Hi there, > From: Hendrik Jan Veenstra <h@...> > > Thoughts from the mind of Lachlan Deck, 26-03-2002: > > [muting individual tracks/sub-tracks] >>> Uh.. yes, sounds like a simple way out indeed :-). So Italic could >>> either mean "entire track muted' or "section of the track muted". >> >> Or maybe it is easier to make the mute button look like an itemized >> check list. > > So: you suggest some kind of popup list with subtracks mute-status? As I don't have the new version - I can only guess by what has been talked about for this kind of stuff. How is it viewed currently? > Pressing the mute button pops up this list or so? Doesn't seem very > practical... although in itself such a popup would have its merits > indeed. No - not suggesting a popup list - but simply a way of (un)muting all items, which may or may not be in view, by the control of a master item, which in this case is the parent like in an itemised list >> i.e., when an item that has sub-items is ticked, for example, it means >> that all enclosed items are also ticked. If one of them in the group is >> not ticked then the group item has a dash or hyphen to show that all >> items are not ticked. > > OK, that's standard behaviour and makes sense. > >> So, normal operations on this would be: >> If one or more, but not all, items in the group are muted, then >> clicking >> once on the main item - to mute all - and then again will unmute all >> and >> therefore allow an easy reset. Or maybe this is better as an >> Opt/mac+click or Ctl/win+click to do a reset... > > But where does the mutalble-items-list appear then? The above sounds > as if you're talking about the plain old mute button. If I remember correctly the original thread was about being able to quickly turn off all or certain embedded automation for a track - or was it for all tracks? Conceptually, this is akin to muting a folder - which mutes all enclosed tracks. When you unmute the folder, however, any enclosed track that was itself muted is still muted. But if the parent (i.e., folder) mute button allowed you to work as you do with an itemised check list then you could (un)mute all enclosed items. Naturally if for a folder it had the list triangles that allowed quick access to enclosed tracks then this would be great as well. So back to the automation thing using the above concepts - if there is a mute button for the parent object that implemented this kind of behaviour for all automation associated with a track, then this would do the trick of what the original question was (if I remember right) about (un)muting automation quickly without having to bring to view each automation thing into view. Or is my memory off the beaten track? >> Screen sets should effect the status of a track being armed or not. >> Only >> whether or not you see that track on the screen-set. > > I suppose you meant "should NOT effect..." :-) Ye - I ha typi to qukly ;-) > -- > Hendrik Jan Veenstra <h@...> > Omega Art: http://www.ision.nl/users/h/index.html with regards, -- Lachlan Deck ldeck@...

Thoughts from the mind of Lachlan Deck, 02-04-2002: > >> Or maybe it is easier to make the mute button look like an itemized >>> check list. >> >> So: you suggest some kind of popup list with subtracks mute-status? > >As I don't have the new version - I can only guess by what has been >talked about for this kind of stuff. >How is it viewed currently? Each track can be expanded to show several tracks, each carrying automation data for the "parent track". Only the parent track has a mute button. That's it -- very bare-bones, really (muting-wise, I mean -- not talking abaout the awesome automation :). > > Pressing the mute button pops up this list or so? Doesn't seem very >> practical... although in itself such a popup would have its merits >> indeed. > >No - not suggesting a popup list - but simply a way of (un)muting all >items, which may or may not be in view, by the control of a master item, >which in this case is the parent like in an itemised list As I said before: the idea of a list has merit in itself, but I just wonder where such a list should appear then... > > But where does the mutalble-items-list appear then? The above sounds > > as if you're talking about the plain old mute button. > >If I remember correctly the original thread was about being able to >quickly turn off all or certain embedded automation for a track - or was >it for all tracks? For specific tracks indeed, not for all at once. >Conceptually, this is akin to muting a folder - which mutes all enclosed >tracks. When you unmute the folder, however, any enclosed track that was >itself muted is still muted. But if the parent (i.e., folder) mute >button allowed you to work as you do with an itemised check list then >you could (un)mute all enclosed items. Naturally if for a folder it had >the list triangles that allowed quick access to enclosed tracks then >this would be great as well. OK... but in the current implementation this would mean something like: muting the parent track mutes all automation, and muting individual subtracks mutes individual parameter-automation. Problem no.1 is that the parent track -also_ shows automation data, and is, in that sense, not a higher-level thing than an automation track (as a flder is higher-level relative to its contents). Besides, I think that one of the early suggestions in this thread was indeed to have mute buttons on individual automation subtracks -- which would implement the above. However, that left us with the problem of what to do when the automation tracks are hideen (collapsed). Hwo do you make it clear to the user that some parameters are muted. That's where your item-list comes in of course, but then again you get the question of where this should appear... >So back to the automation thing using the above concepts - if there is a >mute button for the parent object that implemented this kind of >behaviour for all automation associated with a track, then this would do >the trick of what the original question was (if I remember right) about >(un)muting automation quickly without having to bring to view each >automation thing into view. Or is my memory off the beaten track? But that would mean giving the parent a seperate "automation mute" button, unrelated to the regular mute button, right? And you remember the problem correctly, except that you forget that a user should also have a simple way to find out which parameters are muted and which are not -- or which parameters have sections that are muted, etc. So it's also a matter of feedback, user interface and the like. cheers, HJ -- Hendrik Jan Veenstra <h@...> Omega Art: http://www.ision.nl/users/h/index.html