ardour VS audacity

> I think a lot of people starting with open source kinda expect that dedicated contributors will start to swarm around the project. In reality, a large majority of projects, even many quite prominent ones, are driven by a very small core, often just the project founder.

https://github.com/Ardour/ardour/blob/master/gtk2_ardour/abo...

I'm the lead author of Ardour [0], and I'd very much like to hear more about your frustrations, since over the next 1-2 years, paying attention to non-European musical culture is one of the things I hope to focus on during development. You can reach me via the email address in my profile, or maybe use our forums at discourse.ardour.org. Thanks.

[0] https://ardour.org/ <= a cross-platform open source DAW that has been around for more than 23 years

One extra detail, something I've learned from 20 years of working on dragging all kinds of objects around the GUI of Ardour [0]: handle ALL button press and release events as drag events where there is no movement.

[0] https://ardour.org/

I am aware of the 'Real Tone Cable' however I am curious if this is what I should be buying if I also intend on recording my playing in a software such as 'Ardour'

If you don't care about exotica like async or signal safety, and just need to see the callstack from arbitray points, this can do the job without C++23:

https://github.com/Ardour/ardour/blob/master/libs/pbd/stackt...

(2 different implementations, one for POSIX-y systems with the execinfo.h header, and one for Windows)

The demange() function is elsewhere.

I just loaded an instance of samplv https://samplv1.sourceforge.io/ into the Digital Audio Workstation (DAW), Ardour https://ardour.org/ .

If you produce music using a DAW, my preferred is Linux's Ardour: http://ardour.org

Ardour is a free DAW that recently added a clip launcher. I've never tried it.

#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