On Fri, May 9, 2008 at 5:22 PM, Christian Schoenebeck
<[EMAIL PROTECTED]> wrote:
> As soon as you're going to implement that group feature, I'm sure there will
> be other voices demanding to extend it for other channel strip specific
> parameters as well, e.g. to be able to load the same instrument for multiple
> channel strips at once, simultaneously changing the volume, ... you name
> it ...

I'm thinking about the group volume behavior.
One approach would be to have an option to "bind" the volume of some
or all of the channels in the group to the group volume, which will
mean that when the group volume is changed the volume of those
channels will be changed and will be the same as the group volume. And
option to "lock" the volume of some or all of the channels in the
group to the group volume, which will mean that when the group volume
is changed the volume of those channels will be changed relatively to
the group volume change.
Another approach would be to implement the group volume to be like
global/master volume for the channels in the group. But in that case
maybe we should consider whether this should be done on frontend or on
backend side.

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel

Reply via email to