Hi Tim, Thank you. That was very good,clear explanation!
10.11.2015 00:34, Tim E. Real пишет: > On November 9, 2015 05:59:38 PM Andrew Deryabin wrote: >> Hi All, Tim, >> >> Here is my little question (sorry if I missed something from previous >> explanations about advanced routing): > Not at all, it was never properly explained -;) > >> When 'Omni' column's checkbox is checked in routing popup what channels >> are routed to selected output in case of multi-channel instrument? >> Only 1+2 or all mixed pairs? > It attempts to assign the first N common channels while ignoring the rest. > > Pan and volume are applied only to the first one or two channels. > > Best explained with examples: > > >From a 1-channel track to a 1-channel track: > The source channel has volume applied and then is sent to > the destination channel. > > >From a 1-channel track to a 2-channel track: > The source channel has volume applied and then is sent to > the two destination channels with pan applied. > > >From a 2-channel track to a 1-channel track: > The two source channels are mixed with pan and volume applied and > then sent to the destination channel. > > >From a 2-channel track to a 2-channel track: > The two source channels have pan and volume applied and are then > sent to the two destination channels. > > (Those first four scenarios are exactly like before, as expected.) > > >From a 1-channel track to a 5-channel track: > The source channel has volume applied and then is sent to > the FIRST TWO destination channels with pan applied. > Other destination channels are ignored. > > >From a 2-channel track to a 5-channel track: > The two source channels have volume and pan applied and then are sent to > the FIRST TWO destination channels. Other destination channels are ignored. > > >From a 5-channel track to a 10-channel track: > The five source channels are sent to the FIRST FIVE destination channels. > The FIRST TWO source channels have volume and pan applied, while > the remaining three are sent without modification. > Other destination channels are ignored. > > >From a 5-channel track to a 1-channel track: > The FIRST TWO source channels have pan and volume applied and then > are sent to the destination channel. Other source channels are ignored. > > >From a 10-channel track to a 5-channel track: > The FIRST FIVE source channels are sent to the five destination channels. > The FIRST TWO source channels have volume and pan applied, while > the remaining three are sent without modification. > Other source channels are ignored. > > --- > Note that when using Channel routing instead of Omni routing, > pan and volume are applied only to the first one or two channels. > Pan cannot be applied as broadly as with Omni mode. For example > there is no pan when say, routing one channel to two, EVEN if those > two channels are the FIRST two destination channels. > > --- > Summarizing, a mixer strip's controls are applied only to the first > N channels that the STRIP ITSELF supports. > > So you can see why I spoke of future TRUE multi-channel strips. > There would be meters for ALL channels, and volume and pan > would apply to ALL channels. > It would be tricky since a new kind of panner is needed. > Have you seen Ardour's multi-channel mixer strip panners? > Also there needs to be a way to select how many channels the > STRIP ITSELF has. Again, possibly it will be similar to Ardour where > you tell it how many input AND output channels a strip has. > That's the kind of thing you may expect with multi-channel strips. > We'll see how it works out... The problem will be in real testing of multi-channel panning. Thought I would like to have 12 or more speakers and place them around my room, now I only have 9 (very different from each other :) ) and only 2 2-channel amplifiers. If you are planning to make multi-channel strips with environmental panning, I'll start to make another 4 2-channel amplifiers (or one 12-channel ?) :) :). > --- > And so on... > Hope I got that explanation right, and indeed the logic of it all too. > I need to make some kind of table or chart for users. > > Thanks. > Tim. > > ------------------------------------------------------------------------------ > Presto, an open source distributed SQL query engine for big data, initially > developed by Facebook, enables you to easily query your data on Hadoop in a > more interactive manner. Teradata is also now providing full enterprise > support for Presto. Download a free open source copy now. > http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140 > _______________________________________________ > Lmuse-developer mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/lmuse-developer -- Regards, Andrew -- Regards, Andrew -- Regards, Andrew ------------------------------------------------------------------------------ _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
