Matomo VS audacity

Matomo just released their major v5 upgrade with following key improvements:

There are many good, lightweight, and open-source alternatives to Google Analytics, such as Plausible, Matomo, Fathom, Simple Analytics, and so on. Many of these options are open-source, and can be self-hosted.

You can for example use analytics that aren't spyware, and hence don't even have to try to trick users giving "consent" to things they don't really want.

Seriously: what share of people actually want their behavior to be tracked for ad companies to make more money?

https://matomo.org/

Matomo is a GDPR-compliant and open-source analytics platform. You can either host it yourself or use Matomo’s hosted version. https://matomo.org/

I tried the self-hosted version of Matomo [1][2] a few years back but I remember it was a bit underwhelming for the effort required to set it up.

https://matomo.org

It seems like you just want a self hsoted google analytics. Theres Plausible , Matomo and Umami for that.

#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