audacity VS audacity

#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

They're looking into a new name as well, https://github.com/temporary-audacity/audacity/issues/5

Here's a forked version with telemetry code removed (not mine, and I haven't read the diffs to verify, but it's all visible). But this is the beauty of open source, stuffs available you aren't required to follow new owners if they pull stuff like this: https://github.com/temporary-audacity/audacity/

Audacity will be fine and will continue to be at the top but I think we will see some new popular Forks/Competitors out there, such as this one8, that may or may not rise to the challenge of maintaining a complex application and be able to keep it up to date, work on bugs and issues and also continue to upgrade its feature set an UI. Its something I plan on paying attention to for the foreseeable future and hope this serves as a reminder, Much like OpenJDK, OpenOffice and XFree86 before them, to any other open source projects or Corporate Companies that buy up the Open Source Community Projects that they need to stay true to the community and the Open Source ethos.

It looks like everyone is using this fork: https://github.com/temporary-audacity/audacity

for more context please see this exact comment: https://github.com/temporary-audacity/audacity/issues/48#iss...

TLDR: he’s taking a day off the internet after him and his closed ones getting thousands personal threats over phone, e-mail, etc. for not choosing “Sneedacity” name for the fork

It's a shame the fork doesn't use better commit messages than they do.

For example, "Fixes" is the entire commit message for https://github.com/temporary-audacity/audacity/commit/d9f30b...

Commit messages like these do not inspire a lot of confidence. It would be a lot better (and easier to compare the original and the fork) if the commit message was something like "[Remove-Tracking] Remove SentryHelper.h and sentry ADD_EXCEPTION_CONTEXT usage"