Currently I can only see sort of a selector / switch for audio - for the other types of data or instrument plugins there currently is no simple device to switch input / output.
For switching simple index-parameters should be enough and most understandable.
These extra devices come to my mind:
(1) 1:n selector [support for ALL types of data: events, audio, modulation]
Have 1 input and 1..n outputs on the device and switch the output using an automatable modulation parameter "output" (=index of the selected output) in that device.
(2) m:n selector [support for ALL types of data: events, audio, modulation]
Have 1..m inputs and 1..n outputs on the device and switch the input and output using an automatable modulation parameter "input" (=index of the selected input) and another "output" (=index of the selected output) in that device.
(3) 1 event input for n instruments selector
Have 1 input and 1..n instruments loaded on the device and switch the instrument using an automatable modulation parameter "instrument" (=index of the selected instrument) in that device. This device should also map audio in / out and instrument event out on the device when changing the instrument index.
All continuous data variants of these devices (for audio / modulation data) should sport a crossfade time parameter when switching. By default this would be set to 0 ms = switch immediately. But when set to > 0 ms then data blending takes place with a definable blend curve between the two switched data streams.
Would be cool! What do you think?
FR: Modular View: Simple audio / midi / modulation selectors / switches
-
- KVRist
- 434 posts since 17 Nov, 2020
I don't get it 
What is that switch you are talking about? Maybe I'll be able to understand it in terms of events and modulation.
-
- KVRist
- Topic Starter
- 164 posts since 27 Sep, 2004
These requested elements are elements of the modular view. They would offer advanced routing of audio / events and modulation data. All my suggested devices shall exists in three variants (expect the instrument selector): audio, events, modulation.
So a 1:n selector uses one input and n outputs. For audio it is one audio stream in and multiple streams out. A selector chooses which one to take from the outputs. For modulation it's similar but the input is a modulation connector and the outputs are multiple modulation connectors.
One additional index value (which can be modulated!) controls WHICH output to use:
input
|
|
--------------------
|
| -> output 0
| -> output 1
| -> output 2
| -> ...
| -> output n
So there must be one index value that can be modulated in order to switch the output through which the data will flow.
A value of 0 would use "output 0" and a value of 1 would use "output 1" etc.
For m:n selectors there is an additional input index value that controls which input to use.
When changing the output then a xfade time value shall control how long it takes to go from one output to the other. By default it would be a value of 0 ms = instant changing. But having values > 0 ms would xfade the data from one output to the other in the given time. For audio this would fade out one output signal and fade in the other with the given xfade time.
Even the xfade time could be a modulatable parameter of each selector device!
Such selector devices would be useful for all data types:
- events
- audio
- modulation
Currently there are no easy selector devices to integrate such elements in MuLab.
Hope that helps
So a 1:n selector uses one input and n outputs. For audio it is one audio stream in and multiple streams out. A selector chooses which one to take from the outputs. For modulation it's similar but the input is a modulation connector and the outputs are multiple modulation connectors.
One additional index value (which can be modulated!) controls WHICH output to use:
input
|
|
--------------------
|
| -> output 0
| -> output 1
| -> output 2
| -> ...
| -> output n
So there must be one index value that can be modulated in order to switch the output through which the data will flow.
A value of 0 would use "output 0" and a value of 1 would use "output 1" etc.
For m:n selectors there is an additional input index value that controls which input to use.
When changing the output then a xfade time value shall control how long it takes to go from one output to the other. By default it would be a value of 0 ms = instant changing. But having values > 0 ms would xfade the data from one output to the other in the given time. For audio this would fade out one output signal and fade in the other with the given xfade time.
Even the xfade time could be a modulatable parameter of each selector device!
Such selector devices would be useful for all data types:
- events
- audio
- modulation
Currently there are no easy selector devices to integrate such elements in MuLab.
Hope that helps
-
- KVRist
- Topic Starter
- 164 posts since 27 Sep, 2004
The element that already exists is "Audio Processors" -> "Audio Dispatcher".humanboeing wrote: Tue Jun 07, 2022 2:15 pm I don't get it
What is that switch you are talking about? Maybe I'll be able to understand it in terms of events and modulation.
It is controlled by MIDI however. I would suggest having an index value for switching instead. And then - if required - use another device to map keys to these indices. That would achieve the same effect but would be more flexible.
So all requested devices have index values which can be modulated.
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
For note events there also already is the Note Dispatcher.
The Audio Dispatcher already features crossfading by means of the Attack & Release properties.
A similar Modulation Dispatcher indeed is on the wishlist.
The Audio Dispatcher already features crossfading by means of the Attack & Release properties.
A similar Modulation Dispatcher indeed is on the wishlist.