Envelope Tool Regression

Audacity 3 Help Forum
, , ,
1

Hello, I am using Audacity 3.7.7 on Windows 10, and I noticed the Envelope tool is broken. The audio impact of the envelope control points is disconnected from what the visuals show. This makes it impossible to predict what a track will sound like based on the visuals. This is extremely frustrating.

I reverted to Audacity 2.3.3 (the previous version I used to use), and the envelope tool works as expected. For example, in Audacity 2.3.3, if I set some control points and then render to a new track, the waveform of the new track looks exactly the same. However, in Audacity 3.7.7, when rendering to a new track, the waveform is completely different.

It seems the audio impact of the envelope control points is the same across these versions, just the visualization in Audacity 3.7.7 is exaggerated. I also confirmed Audacity 2.4.2 has the same desired behavior as Audacity 2.3.3.

Is this a bug? Is this some sort of intentional change to make the envelope tool seem more responsive? Maybe there is a setting I’m missing? Are others having this issue, or is this just me? Please help.

Audacity 2.3.3:


Audacity 3.7.7:

2

I’ve not been able to reproduce this with Audacity 3.7.7 (AppImage) on Linux. It’s possible that it’s platform dependent, or perhaps there is something else about that project that is causing the problem. I did find this bug (possibly related): Envelopes treated inconsistently by destructive and non-destructive effects · Issue #3305 · audacity/audacity · GitHub

3

Thanks for testing. I can confirm that the issue occurs for me even with a brand-new project.

4

Have you tried testing with a minimal (reproducible) project, such as:

  1. Launch Audacity (new empty project)
  2. Generate 30 s Tone
  3. Set envelope points at: <list of times and approx levels>
  4. Render to new track
  5. Screenshot.
5

Yes, I did exactly that:

image
image603×501 13.3 KB

And for comparison, Audacity 2.4.2:

image
image500×484 13.3 KB

6

@dozzzzer @mugen2x

7

It looks like you’ve found a bug. I see that Leo has alerted the devs, so hopefully it’ll be fixed.

1 Like