Speaking of which, how did that "audacity isn't FOSS" fuss end up? A quick search shows tenacity is still active ( https://codeberg.org/tenacityteam/tenacity ) but I have no idea how much the projects kept interacting after the initial debate
Audacity 3.4
11–20 of 122 posts
Re: Audacity 3.4
#12Speaking of which, how did that "audacity isn't FOSS" fuss end up? A quick search shows tenacity is still active ( https://codeberg.org/tenacityteam/tenacity ) but I have no idea how much the projects kept interacting after the initial debate
seems like its because they tried to add basic telemetry?
That’s kinda the blessing and the curse of FOSS. You absolutely can fork the repo, remove the telemetry, and republish it as a new app.
But fragmentation is confusing, requires a lot of maintenance, and really I’m not sure it was worth it. Those who are particularly conscious about the telemetry can block it with a single line in /etc/hosts.
Re: Audacity 3.4
#13These are some really nice quality of life updates. I've never used time stretching, but combined with the beats and measure markers, it could be really nice.
Every now and again there'll be a hard to otherwise source episode of something that turns up two poor vesions, one with good video but damaged | lower quality sound another with good sound | bad video .. and they each have differing frame rates and edit cuts.
To make a better version involves a bit of time stretching on the audio between marks.
I still have an eye out for the best OS tool for merging and aligning video + audio + subtitles tracks .. the smoothly integrated intersection of MKVToolNix + SubtitleEdit + Audacity.
Re: Audacity 3.4
#14These are some really nice quality of life updates. I've never used time stretching, but combined with the beats and measure markers, it could be really nice.
There's a particular occasional need for easy to use time stretching of audio against video. Every now and again there'll be a hard to otherwise source episode of something that turns up two poor vesions, one with good video but damaged | lower quality sound another with good sound | bad video .. and they each have differing frame rates and edit cuts. To make a better version involves a bit of time stretching on the…
Re: Audacity 3.4
#15Speaking of which, how did that "audacity isn't FOSS" fuss end up? A quick search shows tenacity is still active ( https://codeberg.org/tenacityteam/tenacity ) but I have no idea how much the projects kept interacting after the initial debate
Tenacity is distinct in more fundamental ways that just not being copyright infringement (for one, it uses a different GUI toolkit and is way slower and buggier), so its appeal at this point isn't closely related to whether people like Muse or not.
Re: Audacity 3.4
#16Speaking of which, how did that "audacity isn't FOSS" fuss end up? A quick search shows tenacity is still active ( https://codeberg.org/tenacityteam/tenacity ) but I have no idea how much the projects kept interacting after the initial debate
seems like its because they tried to add basic telemetry?
Re: Audacity 3.4
#17Way to bury the lede! What's this magic algorithm being spoken of, how does it work so well?
> A more detailed overview of these changes can be found in our changelog.
The changelog is even more terse, saying only which key combo activates it :(
A way bigger deal to me is mentioned at the bottom of the "other changes" in said changelog: Opus support!
Edit: wait, under "libraries" it says
> lib-time-and-pitch implements a time stretching algorithm originating in Staffpad. It currently is one of the highest-quality time stretching algorithms for music on the market.
Staffpad links to https://staffpad.net and seems to be some music app. The library name links to a Microsoft repository (https://github.com/audacity/audacity/tree/e4bc052201eb0e6e22...) with no readme. The source code is documentation enough :)
Re: Audacity 3.4
#18this is made in wxWidgets by the way, a cross platform c++ GUI framework like Qt but 100% free on the other hand inkscape is made with gtkmm(gtk), which also runs cross platform.
How does wxw and gtk roughly compare? I have liked the UI of Audacity moderately more than Inkscape, but I don't know where framework versus implementation is at play.
Re: Audacity 3.4
#19this is made in wxWidgets by the way, a cross platform c++ GUI framework like Qt but 100% free on the other hand inkscape is made with gtkmm(gtk), which also runs cross platform.
For some values of "works". Inkscape is close to unusable on MacOS because it goes through the X server and every interaction is really slow.
Re: Audacity 3.4
#20Earlier quoted context omitted.
Tenacity is distinct in more fundamental ways that just not being copyright infringement (for one, it uses a different GUI toolkit and is way slower and buggier), so its appeal at this point isn't closely related to whether people like Muse or not.
Would be nice with a fork which followed Audacity closely but without the telemetry. (Like VS Codium I suppose.)