Re: [Audacity-devel] Track solo - exclusive vs. non-exclusive

[Vaughan J. <va...@au...>]

I never change that setting, but in 2.0.5 it seems it already sets it 
for new projects, so you only need to set it to Simple once. Right?

- V


On 12/12/2013 3:56 PM, Vaughan Johnson wrote:
> On 12/11/2013 9:28 PM, Norm C wrote:
>> Thought I'd toss this out there (and if it belongs on a different list
>> please
>> let me know). Currently the "standard solo" is non-exclusive (soloing a
>> track does not de-select any currently soloed tracks) unless you hold
>> down
>> Shift while clicking Solo. I realize that's sorta how a HW mixer
>> typically
>> works, and maybe that's why it's done this way, but the HW analogy
>> doesn't
>> hold up so well when you realize that on a mixer you can easily solo one
>> track then another exclusively by simply hitting both tracks' Solo
>> buttons
>> simultaneously, something you can't do on a GUI. There's a couple other
>> reasons I think the default should be exclusive:
>> - that's how Audacity operates when selecting tracks (clicking on a track
>> operates exclusively unless you hold down Shift)
>> - that's how CoolEditPro/Audition works
>>
>> Of course, different people have different preferences, and so maybe the
>> best option is to do it like ProTools does: give the user the option of
>> defaulting to exclusive or non-exclusive.
>>
>> My local copy of Audacity does that - in Preferences - Tracks, the Solo
>> dropdown has, instead of one line for Standard, two:
>> - Standard (exclusive unless SHIFTed)
>
> Isn't that the current 'Simple' mode?
>
>
>> - Standard (non-exclusive unless SHIFTed)
>
> Two 'standards' isn't really meaningful, especially because you're
> talking about setting the default -- I wouldn't understand from that
> wording that it's about the default for other projects. Per
> http://manual.audacityteam.org/man/Tracks_Preferences, the Standard
> choice is named that because it's standard to mixing desks and pro audio
> s/w. Setting the default is orthogonal to choosing among the 3 options,
> so imo, the clearer interface is to not change the menu, but add a
> checkbox "Use as default for all projects" or something like that.
>
>
>>
>> Default is the non-exclusive, for compatibility.
>>
>> Total changed lines of code is about 10. Any interest in getting this
>> into
>> the mainline, or would it be viewed as unnecessary confusion to the user?
>
> Personally, I'm -1 on the feature, but as far as adding stuff to Prefs,
> I think that horse long ago left the barn. ;-)
>
> Thanks for the suggestion, though. I won't oppose it if there's demand
> from others.
>
> - V
>
>
>>
>> Norm
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://audacity.238276.n2.nabble.com/Track-solo-exclusive-vs-non-exclusive-tp7560889.html
>>
>> Sent from the audacity-devel mailing list archive at Nabble.com.
>>
>> ------------------------------------------------------------------------------
>>
>> Rapidly troubleshoot problems before they affect your business. Most IT
>> organizations don't have a clear picture of how application performance
>> affects their revenue. With AppDynamics, you get 100% visibility into
>> your
>> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of
>> AppDynamics Pro!
>> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
>>
>> _______________________________________________
>> audacity-devel mailing list
>> aud...@li...
>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>
>