Bug 1734 – ENH: Scale in Waveform dB view does not change when changing meter dB range in prefs until after restart

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

Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla

Bug 1734 - ENH: Scale in Waveform dB view does not change when changing meter dB range in prefs until after restart


Summary:	ENH: Scale in Waveform dB view does not change when changing meter dB range i...

Status:	CLOSED WONTFIX

Product:	Audacity
Classification:	Unclassified
Component:	User Interface
Version:	2.2.0
Hardware:	Per OS Other

Importance:	P4 Enhancement
Assigned To:	Default Assignee for New Bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-09-03 21:22 UTC by Bill Wharrie
Modified:	2019-11-19 10:06 UTC (History)
CC List:	4 users (show)

See Also:
Steps To Reproduce:	1) Reset preferences (delete audacity.cfg) 2) Launch Audacity 3) Import or generate audio and switch track to Waveform dB view 4) Observe the dB scale 5) Open Preferences > Interface and set meter range to -96 dB and OK 6) Observe the Waveform dB view scale does not change 7) Quit Audacity 8) Launch Audacity 9) Import or generate an audio track and switch to Waveform dB view 10) Observe the Waveform dB scale now corresponds to the interface preference.
Release Note:
First Git SHA:
Group:	---
Workaround:
Closed:	2019-11-19 00:00:00

Flags:	billwh: Regression+

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 Bill Wharrie 2017-09-03 21:22:27 UTC

Assuming repeatable-all. Martyn found this on Windows and I confirmed it on Mac.

Comment 1 Bill Wharrie 2017-09-03 21:24:26 UTC

Regression on 2.1.3

Comment 2 Paul L 2017-09-07 19:37:23 UTC

I believe this is NOT a regression on 2.1.3.

I think this bug was introduced in 2.1.2 when I worked on per-track spectrogram settings, an incidentally attempted per-track waveform settings too, which proved an unpopular idea.

Comment 3 Peter Sampson 2019-11-17 06:06:19 UTC

Testing on W10 with RC03 2.2.3 and 2.1.1

I confirm that Paul is correct and that this is certainly a regression on 2.1.1, introduced in 2.1.2.

And as a regression I believe this should be fixed

Comment 4 Steve Daulton 2019-11-18 13:05:32 UTC

I am not currently convinced that this should be treated as a regression bug. The current behaviour appears to me to be more useful and more expected.
This is currently being discussed on the QA mailing list.

Comment 5 Peter Sampson 2019-11-19 10:06:55 UTC

Marking this as an enhancement not a bug per se.  This behavior has been extant since 2.1.2 and no users have complained since then,

Discussions on the Quality email list show that most of us prefer the current behavior - so I'm marking this as WONTFIX 


Note that negates this recent pull-request:
https://github.com/audacity/audacity/pull/388