# Envelope Tool Regression

**URL:** <https://forum.audacityteam.org/t/envelope-tool-regression/151387>\
**Category:** Audacity 3 Help Forum\
**Tags:** design, playback, bug, ui\
**Created:** [February 15, 2026, 2:46am UTC](https://forum.audacityteam.org/t/envelope-tool-regression/151387 "2026-02-15T02:46:14Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![chadfranklin47](https://forum.audacityteam.org/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@chadfranklin47](https://forum.audacityteam.org/u/chadfranklin47)\
**Post date:** [February 15, 2026, 2:46am UTC](https://forum.audacityteam.org/t/envelope-tool-regression/151387/1 "2026-02-15T02:46:14Z")

</div>

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:

---

<div class="post-metadata">

**Author:** ![steve](https://forum.audacityteam.org/letter_avatar_proxy/v4/letter/s/f19dbf/32.png) [@steve](https://forum.audacityteam.org/u/steve)\
**Post date:** [February 15, 2026, 2:58pm UTC](https://forum.audacityteam.org/t/envelope-tool-regression/151387/2 "2026-02-15T14:58:59Z")

</div>

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](https://github.com/audacity/audacity/issues/3305)

---

<div class="post-metadata">

**Author:** ![chadfranklin47](https://forum.audacityteam.org/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@chadfranklin47](https://forum.audacityteam.org/u/chadfranklin47)\
**Post date:** [February 15, 2026, 3:15pm UTC](https://forum.audacityteam.org/t/envelope-tool-regression/151387/3 "2026-02-15T15:15:43Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![steve](https://forum.audacityteam.org/letter_avatar_proxy/v4/letter/s/f19dbf/32.png) [@steve](https://forum.audacityteam.org/u/steve)\
**Post date:** [February 15, 2026, 4:09pm UTC](https://forum.audacityteam.org/t/envelope-tool-regression/151387/4 "2026-02-15T16:09:14Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![chadfranklin47](https://forum.audacityteam.org/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@chadfranklin47](https://forum.audacityteam.org/u/chadfranklin47)\
**Post date:** [February 15, 2026, 4:59pm UTC](https://forum.audacityteam.org/t/envelope-tool-regression/151387/5 "2026-02-15T16:59:56Z")

</div>

Yes, I did exactly that:

 ![image](https://forum.audacityteam.org/uploads/default/original/3X/2/d/2daaec396636acede14428b059687c1174ddf9e7.png)

And for comparison, Audacity 2.4.2:

 ![image](https://forum.audacityteam.org/uploads/default/original/3X/f/e/feceb897d4abcba1bcbaccec31bbc207c9610e7a.png)

---

<div class="post-metadata">

**Author:** ![LeoWattenberg](https://forum.audacityteam.org/user_avatar/forum.audacityteam.org/leowattenberg/32/72853_2.png) [@LeoWattenberg](https://forum.audacityteam.org/u/LeoWattenberg)\
**Post date:** [February 15, 2026, 5:41pm UTC](https://forum.audacityteam.org/t/envelope-tool-regression/151387/6 "2026-02-15T17:41:36Z")

</div>

@dozzzzer @mugen2x

---

<div class="post-metadata">

**Author:** ![steve](https://forum.audacityteam.org/letter_avatar_proxy/v4/letter/s/f19dbf/32.png) [@steve](https://forum.audacityteam.org/u/steve)\
**Post date:** [February 15, 2026, 9:31pm UTC](https://forum.audacityteam.org/t/envelope-tool-regression/151387/7 "2026-02-15T21:31:06Z")

</div>

> [@chadfranklin47](#):
>
> Yes, I did exactly that:

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

---

<div class="post-metadata">

**Author:** ![system](https://forum.audacityteam.org/uploads/default/original/1X/81a69b20bcd548215067cfaceccc8a10bfa2d176.png) [@system](https://forum.audacityteam.org/u/system)\
**Post date:** [March 17, 2026, 2:46am UTC](https://forum.audacityteam.org/t/envelope-tool-regression/151387/8 "2026-03-17T02:46:51Z")

</div>

Closed on March 17, 2026, 2:46am UTC

This topic was automatically closed after 30 days. New replies are no longer allowed.
