Bug 2086 – Incorrect Mixer Board behaviour

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

Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla

Bug 2086 - Incorrect Mixer Board behaviour


Summary:	Incorrect Mixer Board behaviour

Status:	RESOLVED FIXED

Product:	Audacity
Classification:	Unclassified
Component:	User Interface
Version:	2.3.1
Hardware:	Per OS All

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2019-03-28 16:31 UTC by Steve Daulton
Modified:	2019-03-29 15:11 UTC (History)
CC List:	6 users (show)

See Also:
Steps To Reproduce:	See Description.
Release Note:	Group: TBD Controls and meters on Mixer Board do move correctly, not corresponding with what is occurring in main Audacity window.
First Git SHA:
Group:	---
Workaround:	None
Closed:

Flags:	stevethefiddle: Regression+ petersampsonaudacity: Test‑OK‑Win+ stevethefiddle: 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 Steve Daulton 2019-03-28 16:31:25 UTC

Issue reported on macOS (Mojave) with Audacity 2.3.1.
Confirmed on Linux with Audacity 2.3.2 alpha.
Assumed to be "all", but not tested on Windows.

Controls and meters on Mixer Board do move correctly:

Example 1:

1) Create a project with 2 mono tracks.
2) Open Mixer Board.
3) Move first track fader of the Mixer Board.
Note that the second channel (incorrectly) moves as well.


Example 2:

1) Create a project with 2 mono tracks.
2) Mute track 2.
3) Open Mixer Board.
4) Start playback (or loop play)
5) Move the Track 1 pan slider to the left.
Note that although the pan slider on the mixer board moves to the left, and the main playback meter shows the right channel level drop close to zero, the meters on the Mixer Board show the same level in both channels.

Comment 1 Peter Sampson 2019-03-29 06:46:11 UTC

I confirm this happens on W10 with audacity-2.3.2-alpha-203-d71a54b4e9682223802f70d2af90854d393b8789

Comment 2 Peter Sampson 2019-03-29 06:56:02 UTC

This is a regression on 2.3.0 - so upgrading this to P2

Comment 3 Paul L 2019-03-29 07:42:05 UTC

Examples 1 and 2 might need different bug numbers.

I'm bisecting and there are commits with example 2 but not 1.

Comment 4 Paul L 2019-03-29 10:45:33 UTC

Part of the problem bisects to 4aa990e8359adf365c2e7340a77a4ba4d3a3829d, specifically changes in MixerBoard.cpp

Comment 5 Paul L 2019-03-29 11:47:56 UTC

Fixed at https://github.com/audacity/audacity/commit/2de696b46135b82f4fc56a3d5cef8a88b6db155d

Comment 6 Paul L 2019-03-29 11:48:38 UTC

... which does fix both parts of the description

Comment 7 Peter Sampson 2019-03-29 14:00:52 UTC

(In reply to Paul L from comment #5)
Testing on W10 with audacity-2.3.2-alpha-204-2de696b46135b82f4fc56a3d5cef8a88b6db155d
And yes this does fix both parts of the problem om W10

Comment 8 Steve Daulton 2019-03-29 14:43:55 UTC

Thanks Paul. Works here on Linux.

Comment 9 Cliff Scott 2019-03-29 15:07:33 UTC

Testing on MacOS 10.13.6 looks good for both examples with build 2de696.