audacium VS audacity

In May 2021, after the project was acquired by Muse Group,[62] there was a draft proposal to add opt-in telemetry using Google Analytics and Yandex.Metrica to the code. Users responded negatively, with accusations of turning Audacity into spyware.[63] This spawned several forks, most prominently among them Tenacity[64] and Audacium.[65][66] The company reversed course, falling back to error/crash reporting and optional update checking instead.[67][68] Another controversy in July 2021[69] resulted from a change to the privacy policy which said that although personal data was stored on servers in the European Economic Area, the program would "occasionally [be] required to share your personal data with our main office in Russia and our external counsel in the USA".[70][71][72] That July, the Audacity team apologized for the changes to the privacy policy and removed mention of the data storage provision which was added "out of an abundance of caution."[69]

#5467 Fix 24-bit recording.

The time stretch algorithm is implemented in https://github.com/audacity/audacity/blob/master/libraries/l... particularly functions _time_stretch and _process_hop. It looks to me like a classic phase vocoder with vertical phase coherence (c.f. https://en.wikipedia.org/wiki/Phase_vocoder).

The basic idea is this. For a time-stretch factor of, say, 2x, the frequency spectrum of the stretched output at 2 sec should be the same as the frequency spectrum of the unstretched input at 1 sec. The naive algorithm therefore takes a short section of signal at 1s, translates it to 2s and adds it to the result. Unfortunately, this method generates all sorts of unwanted artifacts.

Imagine a pure sine wave. Now take 2 short sections of the wave from 2 random times, overlap them, and add them together. What happens? Well, it depends on the phase of each section. If the sections are out of phase, they cancel on the overlap; if in phase, they constructively interfere.

The phase vocoder is all about overlapping and adding sections together so that the phases of all the different sine waves in the sections line up. Thus, in any phase vocoder algorithm, you will see code that searches for peaks in the spectrum (see _time_stretch code). Each peak is an assumed sine wave, and corresponding peaks in adjacent frames should have their phases match.

https://github.com/audacity/audacity/releases

If you are able to build from source, you could download the latest source code, or the latest release version source code, and manually apply the patch.

FWIW: We'll be ditching the atlases for 3.4 most likely, in favor of having themes work like they do in source anyway: With individual PNGs for the icons and a Colors.txt containing all the color definitions. With that, custom themes would be much easier to author and also would stop breaking every time we introduce a new icon.

https://github.com/audacity/audacity/issues/4639 this bug mentions everything, I guess it's Audacity after all. To be fixed in 3.3.2

No there isn't. I searched in vain for a workaround, and then checked the Audacity issues and found this: https://github.com/audacity/audacity/issues/3385