Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#24050 - [audacity] mixer panel problems in multitrack environment
Attached to Project:
Arch Linux
Opened by Nicola Bignami (_thebishop_) - Monday, 02 May 2011, 15:59 GMT
Last edited by Eric Belanger (Snowman) - Wednesday, 21 December 2011, 19:36 GMT
Opened by Nicola Bignami (_thebishop_) - Monday, 02 May 2011, 15:59 GMT
Last edited by Eric Belanger (Snowman) - Wednesday, 21 December 2011, 19:36 GMT
|
DetailsDescription:
In a multitrack environment, after applying an effect on a track (or part of it), its controls in the mixer panel became uneffective (the "Mute" and the "Solo" buttons and the sliders won't produce any effect). The controls of the other tracks works correctly. The only way to get through is to save the project, close Audacity, restart it and load the project again. When the problem occurs, sometimes Audacity freeze while playing (the entire UI freezes while the audio output continue to play) if I use the panel mixer on the "locked" track. Additional info: * package version audacity 1.3.13-1 x86_64 (I didn't try with the 32bit version) Steps to reproduce: open Audacity create a project with more than one track open the panel mixer apply an effect to one of the tracks (or part of it) start playback on the panel mixer press the "Mute" or the "Solo" button or move the slides of the edited track |
This task depends upon
Comment by Eric Belanger (Snowman) -
Tuesday, 13 December 2011, 19:18 GMT
is it fixed in audacity-1.3.14-1 ?
Comment by Nicola Bignami (_thebishop_) -
Wednesday, 21 December 2011, 19:00 GMT
Yes, it is fixed in audacity-1.3.14-1.