Bug 1686 – Equalization effects ignore and remove any amplitude envelope

••• Introduction •••
••• Keywords •••

Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla

Bug 1686 - Equalization effects ignore and remove any amplitude envelope


Summary:	Equalization effects ignore and remove any amplitude envelope

Status:	CLOSED MOVED

Product:	Audacity
Classification:	Unclassified
Component:	Built-in FX
Version:	2.2.0
Hardware:	Per OS All

Importance:	P2 RepeatableAll
Assigned To:	Default Assignee for New Bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-07-15 07:28 UTC by James Crook
Modified:	2021-09-01 06:11 UTC (History)
CC List:	7 users (show)

See Also:	208
Steps To Reproduce:	1. Create a mono DTMF. 2. Use envelope tool to reduce it to 1/4 amplitude. 3. Select 5s to 15s. 4. Apply Equalization (or Filter Curve or Graphic EQ) The audio in that section is boosted back to full amplitude.
Release Note:	Group: Effects *Equalization effects ignore and remove any amplitude envelope
First Git SHA:
Group:	Envelope
Workaround:	One possible workaround is to "apply" the envelope (using "Tracks > Mix > Mix and Render") before applying EQ. The downside is that it makes the envelope permanent rather than editable
Closed:	2021-09-01 00:00:00

Flags:	petersampsonaudacity: Regression+ petersampsonaudacity: Test‑OK‑Win+ petersampsonaudacity: Test‑OK‑Win- petersampsonaudacity: Test‑OK‑Mac+ petersampsonaudacity: Test‑OK‑Mac- stevethefiddle: Test‑OK‑Lin+ petersampsonaudacity: Test‑OK‑Lin-

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description James Crook 2017-07-15 07:28:25 UTC

Equalization appears to ignore amplitude envelope.

Comment 1 Peter Sampson 2019-08-22 12:10:26 UTC

Tested on W10 with audacity-2.3.3-alpha-326-c9fbd283b7bfc8702caf86a4672cba7ff6260b7d

This has propagated to the new for 2.3.3 Filter Curve  and Graphic EQ (sliders) effects, similarly afflicting them

Comment 2 Steve Daulton 2020-06-14 21:40:13 UTC

This looks to me more like a real "bug" rather than an "enhancement".
It has also been reported by real users.

Comment 3 Peter Sampson 2020-06-15 05:20:07 UTC

I agree with Steve - and this Forum poster
https://forum.audacityteam.org/viewtopic.php?f=46&t=111560

Comment 4 Peter Sampson 2020-06-15 05:25:24 UTC

Retitling this bug and upgrading to P3 with a Release Note ans Worjaround

Comment 5 Steve Daulton 2020-06-15 05:28:20 UTC

This appears to be a duplicate of the P2 bug 208.

Comment 6 James Crook 2020-06-30 06:49:29 UTC

This is a special case of bug 208.

This bug 1686 gives precise steps to reproduce, and will be easier to clear than 208.  Whoever fixes it may well go on to fix bug 208 too.  I prefer to keep this as a bug in its own right rather than close as duplicate.  No need to break 1686 into many component bugs.  This broken out bug is enough to act as a canary for 'are we making progress?'.

Comment 7 Leland Lucius 2020-08-09 04:08:29 UTC

Fix in:

https://github.com/audacity/audacity/commit/58adb94

Comment 8 Peter Sampson 2020-08-09 05:58:49 UTC

(In reply to Leland Lucius from comment #7)
Tested on W10 with Audacity 3.0.0 58adb94

This now looks to be fixed properly on Windows.

Comment 9 Peter Sampson 2020-08-09 07:12:10 UTC

(In reply to Leland Lucius from comment #7)
Tested on macOS 10.15.6 Catalina with Audacity 3.0.0 58adb94

This now looks to be fixed properly on Windows.

Comment 10 Steve Daulton 2020-08-18 16:04:52 UTC

Works for me on Linux.

Comment 11 Peter Sampson 2021-08-25 09:44:48 UTC

This fix was reverted for 3.0.4

See: https://github.com/audacity/audacity/actions/runs/1163596473

and:  https://github.com/audacity/audacity/pull/1526

Comment 12 Peter Sampson 2021-09-01 05:58:45 UTC

closed in favor of GitHub Issue 1595
https://github.com/audacity/audacity/issues/1595