Ammonite-Ops VS audacity

The indent based syntax is only available in Scala 3, you have to download a matching ammonite version from https://github.com/com-lihaoyi/Ammonite/releases

That's funny, because this is what I really like about Scala; how quick and easy it is to get a project started.

> sbt new scala/scala3.g8

will just create an empty project. If you don't even want to bother with a project, use use scala-cli or ammonite (http://ammonite.io/) to just start banging out code.

Even the upgrading of a project from Scala2 to Scala3 is a breeze, thanks to very good backwards compatibility of new library releases.

Ammonite is a very good REPL for Scala. You can invoke it with amm and type expressions into it, or load a Scala “script file” whose name ends with .sc into it, or many other things. It’s documented at https://ammonite.io. 2. sbt is the dominant build tool for Scala projects. As others have commented, when you open a folder in Visual Studio Code and try to make Metals “aware of it,” it expects to find a “Scala project” in the folder. A “Scala project” isn’t just Scala source code. See https://www.scala-sbt.org for details. 3. Also be aware that Metals supports worksheets, so you can easily experiment with code in your project interactively, too.

Scripting API is quite limited, so the third option. - reuse the ammonite scripts https://github.com/com-lihaoyi/Ammonite or look how this is implemented (using internal compiler API),

Your exposure to Functional Programming with Haskell and Clojure suggest you will certainly pick up Scala quickly. With ZIO and cats, you can write robust software quickly. Consider the excellent Coursera Scala course. Get "the Red Book" https://www.manning.com/books/functional-programming-in-scala, and most important, play. Experiment to see how things work. Get https://ammonite.io/

Here's an example of a smaller project that added telemetry without suffering a fork:

https://github.com/com-lihaoyi/Ammonite/issues/607

Or ammonite - I've ran Gatling performance test from a simple script based on this gist it fetches all the dependencies, compiles and runs the test, producing nice html report..

Scala with the Typelevel ecosystem. Stay on the jVM, but have a much more pleasant and robust experience, including a great REPL.

#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