Audacity Bug Summary
••• Introduction •••
••• Keywords •••
    Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla



Bug 2213 - When Solo button is "Multi-track" Export is not accurate - can lead to data loss
When Solo button is "Multi-track" Export is not accurate - can lead to data loss
Status: RESOLVED FIXED
Product: Audacity
Classification: Unclassified
Component: User Interface
2.3.3
Per OS All
: P2 RepeatableAll
Assigned To: Default Assignee for New Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-09-08 10:27 UTC by Peter Sampson
Modified: 2019-09-08 10:32 UTC (History)
7 users (show)

See Also:
Steps To Reproduce:
1) In Tracks Behaviors preferences set the Solo button mode to be Multi track. 2) Generate 4 tracks: a) Chirp b) Click Track c) Noise d) 30 second Risset Drum 3) make the following settings: Track a MUTE (greyed out) Track b SOLO (not greyed) Track c neither (greyed out) Track d MUTE and SOLO (not greyed out) 4) File > Export as WAV 6) Either listen to the WAV file or import it 7) Observe: you get tracks b and d - what you rightly expect is tracks b and C
Release Note:
First Git SHA:
Group: ---
Workaround:
Closed: 2019-09-08 00:00:00
petersampsonaudacity: Must‑Test‑All‑OS-
petersampsonaudacity: Test‑OK‑Win+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Sampson 2019-09-08 10:27:15 UTC
When the Solo button is set to "Multi-track" in Tracks Behaviors preferences Export is not accurate, users do not get the exported audio they expect from
a) looking at the non-grayed-out waveforms
b) previewing the audio by using Play

So Export in this mode is neither WYSIWYG nor WYHIWYG

This can lead to irretrievable data loss if the user
1) makes solo/mute settings
2) previews the audio with play
3) exports the audio
4) fails to check the export
5) Deletes the project

This issue arises as Audacity is basing it's Export upon the setting status of the un-obvious Mute buttons - rather than the much more obvious visible state of the displayed waveforms.

It also leads to a gross inconsistency between Playback and Export where
a) Playback works off the visibly active waveforms and ignores the Mute buttons
b) Export works off the Mute button and ignores the visibly acrive waveforms
Comment 1 Peter Sampson 2019-09-08 10:28:00 UTC
James has submitted a fix for this issue:
https://github.com/audacity/audacity/commit/cabe925ab72eceaae46fc8b26db3d0e111ca1b35
Comment 2 Peter Sampson 2019-09-08 10:32:56 UTC
Testing on W10 with audacity-2.3.3-alpha-345-cabe925ab72eceaae46fc8b26db3d0e111ca1b35

This now tests OK on Windows

I tested with
a) Simple
b) Multi-track
c) None
d) Export Multiple

and all look good

James advised me that this "Only needs testing on one platform..." - accordingly I shall close this as fixed.


This is not a regression - we have had this issue for a very long time.