View Issue Details

IDProjectCategoryView StatusLast Update
0000210ardourfeaturespublic2007-01-26 20:03
Reporterobligog Assigned Topaul  
PrioritynormalSeverityfeatureReproducibilityalways
Status closedResolutionfixed 
Platformi686OSLinuxOS VersionMDK 9.2
Summary0000210: Solo/Cut GUI cleanups
DescriptionIn an audio app red always indicates things that are potentially dangerous i.e. recording (Master record button). The Cut buttons on the channel strips should also be red (or maybe an orange colour so as not to confuse them with the track arm button) to indicate the possible danger of having a track cut.

Also the solo should be yellow to differentiate it more from the cut.

When a track is soloed all other tracks should be cut (cut button illuminated) unless it is in solo safe.
TagsNo tags attached.

Activities

paul

2004-02-11 19:44

administrator   ~0000408

chris - by "cut" do you mean "mute" ?

as for solo behaviour, we cannot implement the behaviour you describe, for a good technical reason. unlike most hardware consoles, ardour effectively allows
direct line in patching to the busses and more importantly, does not have a hardwired master out bus. this means that if you silenced all other *strips* when one strip is soloed, you would (1) lose live input on the busses and (2) lose output from the master outs.

ardour mutes all other tracks when one track is soloed, and all other busses when a bus is soloed. this allows us to retain maximal mixer flexibility while behaving in a mostly intuitive fashion.

paul

2004-02-11 19:46

administrator   ~0000409

oh, in addition, there is (nowadays) also a "rude solo" light that blinks red to provide a clear indication of solo status whether or not the relevant solo button is on screen or not. i prefer this to your color suggestions - if you look at most hardware consoles and/or recorders, mute + solo buttons have no color at all, and are certainly not the same color as rec-enable.

paul

2004-05-26 12:51

administrator   ~0000856

no feedback from reporter, and believed to be "not a bug"

Issue History

Date Modified Username Field Change
2004-01-06 10:23 obligog New Issue
2004-02-11 19:44 paul Note Added: 0000408
2004-02-11 19:46 paul Note Added: 0000409
2004-02-11 20:03 paul Status new => feedback
2004-02-11 20:03 paul Description Updated
2004-05-26 12:51 paul Status feedback => resolved
2004-05-26 12:51 paul Resolution open => fixed
2004-05-26 12:51 paul Assigned To => paul
2004-05-26 12:51 paul Note Added: 0000856
2007-01-26 20:03 oofus Status resolved => closed