2
points
Aldipower
Joined 1,853 karma
- AldipowerGoodbye MS!
- Just in time I received my brand new Commodore 64 Ultimate directly before Christmas. What a lovely made piece of retro hardware.
- 2 points
- I am providing my own music on Spotify via a distributor I a pay 50 Euros once. What do I get from Spotify? Basically nothing! It is not the rightholders as I am the rightholder! Spotify is a scam for artist.
- Oh, just noticed my provider "Vodafone Germany" is blocking the domain annas-archive.li on DNS level.
- Used it heavily as my AS3 dev times from 2008 to 2011. Crazy that is still around.
- The cookie storage and the local storage by all means is not the same! Cookies are not stored in the local storage and could be httpOnly, so they are not directly accessible by JavaScript. Nevertheless, as described above, with this XSS attack it is easy to bypass the token and just steal the user credentials by pretending a fresh login mask keeping the origin domain intact. That's why XSS attacks are dangerous since existence. Nothing new actually.
- I have fond memories of Turbo Pascal.
- Thanks for this advice. I will never ever try HTMX now. I hate waiting. This makes me sick.
- This guy lives in extremes! His option 1 is pure HTML the only other option 2 is React! But it seems he never heard about VanillaJS to drive a button click.
- Thank you. Tbh I cannot tell too many difference to intervals.icu, last time I had a look was 2 years ago or so. I remember it lacked some things, but this could have changed. I think Tredict is a little bit more on the straight forward site, just looks cleaner, visually and also from the workflow, also more performant. But this is of course opinionated as I am the inventor of Tredict. I have deep respect for Intervals too. You just could use both for a certain amount of time to see which one fits better for you. :-)
- Because I was frustrated of the pricing and feature list of TrainingPeaks, I've built my own training planning and analytics platform for endurance athletes (and coaches too!). It is called Tredict (https://www.tredict.com.) and it covers almost everything for runners, cyclists and swimmers over training effort forecasting and prediction, a comprehensive training log, training plans, workout planning, Vo2Max calculation, FTP assessments and collaboration with other athletes and coaches, equipment tracking and so on and so on. Quite a lot of things TrainingPeaks offers too. It has integrations for sending and execution of planned workouts to your watch with Garmin, Wahoo, Suunto, Coros, icTrainer and it receives executed trainings or health data from Polar, Dropbox, Oura, Withings and others! I think I did more then 15 oAuth integrations in total over Tredict's existens? And the platform offers an oAuth2 API for 3-party integrations on its own.
The payment model is a pre-paid model for 12 months of write access to your calendar. It brings ~500-600 Euros (before taxes) a month since 6 years.
- Actually I am using PipeWire with rtkit on Debian. But somehow it does not solve my midi problems. "Audio pipeline" is not "midi". Nevertheless I am doing all my _audio_ (not midi) work on Debian and I am very happy with it.
- Bandwidth never was the problem with MIDI, that is actually enough, but your right with _some_ devices in the 80s/90s, that the processor was under-powered for the bandwidth. For example my Roland Alpha Juno 2 from 1986 is somewhat under-powered and not the tightest, but my Casio CZ-5000 also from 1986 is just doing fine! I mean this is almost 40 years ago and there were device that could handle it without problems. The problem with USB though is, that is does buffer in a "non real time safe" way, which leads to unpredictable jitter and interrupts. That means, for MIDI, USB is worse then the original DIN connection.
I am not talking of MIDI in a DAW, without any physical connections, this works just fine.
- Yes, they have timestamps. But if you do buffer (or better to say, delay it), you introduce latency, which is even more worse then jitter. The ideal is 0 latency. And another downside with buffering, you would need to manifest the buffer time at all device you trigger to be the same time otherwise you do not stay in sync.
Edit: Actually midi note on events that are being sent to devices do _not_ have a timestamp! Only events that are persisted in a file may have timstamps.
- I have maybe 20 hardware synths and I do a lot of sequencing. And yes it wasn't a problem 25 years ago, that is exactly why I still use an Atari STe! :-) But today it is a problem. It is just not possible to do complex and tight sequencing today with a normal Win, Mac or Linux computer. Even with my RME PCIe card. Your argument, "it wasn't a problem decades ago, so it cannot today either" is simply not correct.
- This does not solve the underlying problem at all, which makes today's MIDI, coming from a normal computer, almost unusable for serious sequencing. This is timing and jitter issues! So, may I asked, what is the actual use-case for this sequencer? I would like to see/hear some music you made with it. Or is this just for the sake of using AI?
- Google search also favors large, well-known sites over newcomers. For sites that have a lot of competition, this is a real problem and leads to asymmetry and a chicken-and-egg problem. You are small/new, but you can't really be found, which means you can't grow enough to be found. At the same time, you are also disadvantaged because Google displays your already large competitors without any problems!