News for hackers. Stuff that matters.

LWinterberg

Re:Audacity 3.4 – New Musical Features on Sunday November 05, 2023 @07:04PM (#38157144)
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.
Re:Audacity 3.4 – New Musical Features on Sunday November 05, 2023 @06:52PM (#38157068)
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 half-true: while cutting in the context of cut-and-paste may have been used with shortcuts, a fairly significant number of Audacity users actually used "the scissors" to cut (as in: delete) content and came to the forum to complain because their core workflow was broken.

This sort of situation is bad for everyone: People get their workflow broken, devs need to do work to remove and later reinstate a feature, and privacy-minded people who want to complain need to share name and email to sign up on a forum for an account. In addition, it is hard to gauge what significance the forum posts have: If 100 people are complaining, are they a vocal minority of the millions of users Audacity has, or are they representative of most people?

This is especially true considering Audacity is the sort of casual "useful toolbox USB stick" program for many people - they're not going to closely follow development and updates or participate in polls or surveys, simply because it's not a part of their life they care about that much. This situation is different for something like Blender in which the tool tends to be a major part of your hobby or job if you use it at all. Although, saying that: This is a hypothesis based on my perception which cannot be verified as neither Blender nor Audacity track this data.

With telemetry (which for Audacity would have been a "do you want telemetry yes/no"-type dialog on first launch) the question "does anyone actually use the cut/copy/paste buttons?" would have been answered with "actually, yes", things would have been done differently, nobody's workflows would have been broken, and privacy-minded folks would not have needed to put emails on a forum which may or may not get hacked in the future.

In some sense, even people who disable telemetry benefit from telemetry being an option - assuming that their needs are in aggregate otherwise similar to the average user.

Re:Audacity 3.4 – New Musical Features on Friday November 03, 2023 @03:48PM (#38134059)
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.
Re:Audacity 3.4 – New Musical Features on Friday November 03, 2023 @01:22PM (#38131942)
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.

Re:Audacity 3.4 – New Musical Features on Friday November 03, 2023 @12:58PM (#38131565)
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 (i.e. - VST3, which is compatible with GPLv3).

VST3 is dual licensed with some Steinberg license and GPLv3. The purpose of the CLA was to be able to migrate Audacity binaries to GPLv3 with VST3 support. This has happened as of Audacity 3.2.

Other uses for the CLA are to publish the thing in app stores down the road. It's not stopping Audacity being open source, unless you consider Apache software not open source.

Re:Audacity 3.4 – New Musical Features on Friday November 03, 2023 @12:40PM (#38131235)
Feel free to! View > Toolbars > Share Audio toolbar disables it. Compiling from source has it disabled by default.
Re:Audacity 3.4 – New Musical Features on Friday November 03, 2023 @05:56AM (#38126502)
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.
Re:Audacity 3.4 – New Musical Features on Friday November 03, 2023 @05:55AM (#38126493)
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 relevant features disabled, or you can just download an older version of the software and stick with that to the end of time if you dislike the changes a new version brings.

Even to the suitiest of corporate suits it's clear that the enshittification funnel (first it's awesome for users, then for partners like publishers and advertisers at the cost of users, then it's awesome for making money at the cost of everyone else) simply doesn't work with an open source program.

Re:Audacity 3.4 – New Musical Features on Friday November 03, 2023 @04:18AM (#38125888)
As you can see in https://github.com/audacity/audacity/pull/835, the telemetry was never added.
Re:Audacity 3.4 – New Musical Features on Friday November 03, 2023 @04:17AM (#38125878)
Audacity will switch to Qt/QML for version 4 because wxWidgets just keeps getting in the way.
Re:Audacity 3.4 – New Musical Features on Friday November 03, 2023 @04:12AM (#38125845)
> - 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 samples without anyone ever noticing that it had happened.

> - The documentation at https://manual.audacityteam.org/index.html is still for 3.3 which is a bit frustrating when trying out new features. Also the link labeled Manual that is displayed in the splash screen 404s for me.

the manual job always takes forever to complete, but support.audacityteam.org is updated.

> - It took a bit too long to scan my computer for plugins and at the end I was told some plugins were deemed incompatible but not why.

It tries to load the relevant VSTs in a child process and if the VST crashes the child process it gets flagged as incompatible. Audio plugins are awful and nobody ever follows the spec.

All of the other things you mentioned are in various stages of being planned.

Re:Audacity 3.4 – New Musical Features on Friday November 03, 2023 @04:05AM (#38125807)
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: Musescore (the notation program) is free and open source, musescoreCOM (the website) makes money. If Musescore didn't exist or was hard to access (ie paid), musescoreCOM would have way less content and thus would make way less money.

Now look back at Audacity: There's Audacity (the program) and then there's audioCOM (the website). Audacity, being the thing which has a dedicated upload button to it, is definitely the main source of content for this website.

Now, why would Muse make Audacity paid and completely cripple audioCOM with it? And what money would they make from selling it? Wouldn't people just be able to download Audacity 3.2 from literally anywhere because it's GPL'd anyway?