ktpsns
12 hours ago
An audacity fork. Reason for forking described at https://tenacityaudio.org/docs/_content/Introduction_and_Mot... . Their own summary:
> 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
forgotpwd16
11 hours ago
So, 4 years since the initial forks and 2 years since the Audacium merge, how Tenacity (basically Tenacity&Saucedacity&Audacium) compares to Audacity?
LeoWattenberg
44 minutes ago
After its inception, Tenacity unfortunately tackled an irrelevant, yet opinionated part of development first: The build system, together with any internal variables saying "audacity" getting replaced with "tenacity". As such, a lot of the work that's gone into it don't manifest to users, and merging any upstream changes takes needlessly long. As a result of this, Tenacity fell behind upstream a lot, being stuck somewhere around Audacity 3.1 while Audacity already was around 3.7. Last month, mercifully, Tenacity got rebased onto Audacity 3.7: https://codeberg.org/tenacityteam/tenacity/pulls/527 (a +261299 -395037 diff!)
As far as user-facing changes go, it's some new themes, a different compressor, keeping features visible which upstream has hidden by default, MKA support without FFmpeg, as well as support for some more niche systems (Haiku, BSD). All of this is in some stages of ongoing; Tenacity 1.4 alpha 1 got released a few weeks ago, and while that does include the rebase, it hasn't ported back all of the changes which were made before the rebase.
Noteworthy: Most of the development is being contributed by one person, Avery King.
As of right now, I'd recommend Audacity 3.7.x over Tenacity, as Audacity 3.x has been in maintenance mode pretty much since 3.6, while Tenacity is currently finding its footing again. Disabling update checking is easy enough anyway.
In the future though, it appears that Tenacity is going to keep alive legacy Audacity for legacy systems while Audacity 4 is on the way of adding more DAW features and dropping support for older systems. Definitely a worthwhile role to inherit.
(disclaimer: I was a designer for Audacity)
cookiengineer
9 hours ago
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.
[1] https://github.com/audacity/audacity/blob/8d6e45a9756e700b7f...
swiftcoder
8 hours ago
Can you point out the specific issue here? At a glance it looks like a fairly normal self-update patching process
Orygin
7 hours ago
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