Well, technically the reason for the fork was the implanted backdoor that was executing a binary coming from Muse groups server, hidden as telemetry and an update check. It's not a well built backdoor and the code is easy to spot, as there's not a lot of other http related code in audacity itself.
edit: Check the au3/src/update/UpdateManager.cpp, they're still not hiding this better after all that happened, lol.
I mean, you already are "executing a binary coming from Muse groups server" if you downloaded Audacity from their website. How is an auto update mechanism a backdoor? You have to accept a modal for it to run the downloaded binary.
I guess it could be improved by using and verifying signatures, but it seems pretty on point for a standard windows software auto update feature
that's a beautiful and very educational video. Basically how to listen user and how to implement feedback around user feedback.
I mean tantacrul's videos are generally super educational to begin with but I really liked this one tbh. Wish he could do this full time and had more frequent videos.
the only thing that I didn't liked the logo. I mean bleh. i hope they'll do something more nice to look at. that's my only complaint lol.
I didn't know it was still maintained. Just gave it a try on this laptop with Manjaro Linux + XFCE and noticed it both messes with the desktop panel toolbar making it rearrange and flash repeatedly for some seconds while loading and also when changing preferences, then doesn't correctly fit fonts into the dropdown lists in all toolbars. It appears to me it doesn't take into account that the list elements add a bigger empty space around fonts compared for example to buttons, so it considers them shorter and they're partially cut out. I don't have a GH account to properly report this.
From the Development section
> The upstream development repository is found on Codeberg. We maintain a GitHub mirror for accessibility and CI purposes, but pull requests are ignored.
Does anyone see multitrack recording happening well in-browser?
Has anyone tried BandLab? Aside from the social slop and recent aggressive advertising, their recording app is super impressive, glitch free, low latency, easy to use and sounds great.
Or will this always be the domain of installable software?
I've never recorded with BandLab, but used it a lot for playback, and for a beginner, it's really good and very easy to use.
With regards to recording - I'm curious how this would work on a scale like 16 ins at a time. Dumping bits from the interface to disk as uncompressed .wav is trivial, on the browser I'm not sure how storage works. Would it have to upload to the cloud immediately?
Serious question: Why would it be preferable to have something like this in the browser? The thought of having to keep track of a browser tab that you might accidentally close and lose all your work doesn't sound great.
This is easy to fix with local storage. You reopen the tab and you're right where you left it. Unfortunately the companies see it as an opportunity to lock users in with cloud saving.
The allure is that the web is the most open, most stable and the most cross-device platform we have. Almost anything that was made for web still works today, with Flash and Java applets being the two big exceptions. Following the Lindy effect the self-contained web apps of today will still be operational far into the future.
Contrast this with Android's pathetic record of constantly breaking backward compatibility and restricting what software the users can even run on their devices.
How is the web stable? Any server can change the app you're working on without you being able to do anything. Tons of the old web is broken or gone.
Compare that to a win32 desktop app that will almost certainly keep working indefinitely without any changes. Plus you can use proper files for storage.
> at the primary reasons were attempts at adding telemetry and a new desktop privacy policy [by the new audacity maintainers]
Previously discussed at https://news.ycombinator.com/item?id=34835200
edit: Check the au3/src/update/UpdateManager.cpp, they're still not hiding this better after all that happened, lol.
[1] https://github.com/audacity/audacity/blob/8d6e45a9756e700b7f...
I guess it could be improved by using and verifying signatures, but it seems pretty on point for a standard windows software auto update feature
Will this be merged into Tenacity or are they going further apart?
I mean tantacrul's videos are generally super educational to begin with but I really liked this one tbh. Wish he could do this full time and had more frequent videos.
the only thing that I didn't liked the logo. I mean bleh. i hope they'll do something more nice to look at. that's my only complaint lol.
(found sniffing around https://codeberg.org/tenacityteam/tenacityaudio.org , this 404 was reported on IRC)
Has anyone tried BandLab? Aside from the social slop and recent aggressive advertising, their recording app is super impressive, glitch free, low latency, easy to use and sounds great.
Or will this always be the domain of installable software?
With regards to recording - I'm curious how this would work on a scale like 16 ins at a time. Dumping bits from the interface to disk as uncompressed .wav is trivial, on the browser I'm not sure how storage works. Would it have to upload to the cloud immediately?
The allure is that the web is the most open, most stable and the most cross-device platform we have. Almost anything that was made for web still works today, with Flash and Java applets being the two big exceptions. Following the Lindy effect the self-contained web apps of today will still be operational far into the future.
Contrast this with Android's pathetic record of constantly breaking backward compatibility and restricting what software the users can even run on their devices.
Compare that to a win32 desktop app that will almost certainly keep working indefinitely without any changes. Plus you can use proper files for storage.