Audacity predates this convention, it's Cmd+1,2,3,E,F for zoom in/neutral/out/selection/project at the moment. It definitely should be changed though.
In the context of Audacity, telemetry already would have been useful: A previous version removed the cut/copy/paste buttons, thinking that people normally used ctrl+x/c/v. However, in practice this turned out to only be…
We've definitely learned something. And I can forgive you being skeptical, all I ask from you is to also be skeptical of outrageous claims.
Note that it says "closed" at the top. Pull requests which are merged say "merged", like this one: https://github.com/audacity/audacity/pull/5484 You can verify for yourself that there is no telemetry code in Audacity.
Indeed: > Audacity's source code is currently released under the GNU General Public License version 2 (GPLv2). We intend to update the license to GPLv3 to enable support for new technologies not compatible with GPLv2…
Feel free to! View > Toolbars > Share Audio toolbar disables it. Compiling from source has it disabled by default.
This fork exists and it's called Audacity. Audacity doesn't have any telemetry, the PR never got merged. And any online functionality it does have (automatic update checking, crash reporting) can be turned off.
Not really. Enshittification requires high switching costs, so users stick around despite thinking "yeah I should go somewhere else". With Audacity, switching costs are low. You either can compile the thing with the…
As you can see in https://github.com/audacity/audacity/pull/835, the telemetry was never added.
Audacity will switch to Qt/QML for version 4 because wxWidgets just keeps getting in the way.
> - The tempo stretching example in the video was too subtle for me. I listened a few times and had trouble telling the difference. that's the point of it. Being able to make 124 bpm samples cooperate with 110bpm…
It's complete BS. Audacity never stopped being open source and currently has update checking and crash reporting - it does not have any telemetry.
You may want to actually read the privacy policy, particularly point 4: "We do not store or share any personal information." Regarding Audacity becoming a paid product or closed source, look at the rest of Muse Group:…
Audacity predates this convention, it's Cmd+1,2,3,E,F for zoom in/neutral/out/selection/project at the moment. It definitely should be changed though.
In the context of Audacity, telemetry already would have been useful: A previous version removed the cut/copy/paste buttons, thinking that people normally used ctrl+x/c/v. However, in practice this turned out to only be…
We've definitely learned something. And I can forgive you being skeptical, all I ask from you is to also be skeptical of outrageous claims.
Note that it says "closed" at the top. Pull requests which are merged say "merged", like this one: https://github.com/audacity/audacity/pull/5484 You can verify for yourself that there is no telemetry code in Audacity.
Indeed: > Audacity's source code is currently released under the GNU General Public License version 2 (GPLv2). We intend to update the license to GPLv3 to enable support for new technologies not compatible with GPLv2…
Feel free to! View > Toolbars > Share Audio toolbar disables it. Compiling from source has it disabled by default.
This fork exists and it's called Audacity. Audacity doesn't have any telemetry, the PR never got merged. And any online functionality it does have (automatic update checking, crash reporting) can be turned off.
Not really. Enshittification requires high switching costs, so users stick around despite thinking "yeah I should go somewhere else". With Audacity, switching costs are low. You either can compile the thing with the…
As you can see in https://github.com/audacity/audacity/pull/835, the telemetry was never added.
Audacity will switch to Qt/QML for version 4 because wxWidgets just keeps getting in the way.
> - The tempo stretching example in the video was too subtle for me. I listened a few times and had trouble telling the difference. that's the point of it. Being able to make 124 bpm samples cooperate with 110bpm…
It's complete BS. Audacity never stopped being open source and currently has update checking and crash reporting - it does not have any telemetry.
You may want to actually read the privacy policy, particularly point 4: "We do not store or share any personal information." Regarding Audacity becoming a paid product or closed source, look at the rest of Muse Group:…