Quote:
- + Parent send: allow arbitrary channel counts for master/parent send
|
I have questions. :-)
Let's say the parent channel has 10 channels and the child has 10 channels. At the moment, you can route 1-10, 2-10, 3-10, etc. to the parent. I'm not sure I understand the use case, nor why not 1-9, 1-8, 2-6, etc. if these kinds of partial ranges are supported.
If the parent has 10 channels and the child has 4 channels, the situation makes a little more sense: 1-4, 2-5, 3-6, etc. but at the end you get 7-10, 8-10, 9-10 which again feels weird.
Much more interesting and IMO useful is creating a manual send from a 10 channel source to a 10-channel destination. There you have a menu for mono, stereo and multichannel sources to mono, stereo and multichannel destinations. That's fantastic.
I did find a bug though. If you have a 4-channel source and a 10-channel destination, you get these options, in which the nonexistent channels 11 and 12 are referenced:
