Currently you can add a nested composer to MuLab's composer to send MIDI data to it.
However when adding an automation sub-track for this nested composer you cannot target the automation parameters of the composer or its input pins.
It would be awesome to be able to target and automate a nested composer's:
- automation parameters (MP1...MP128)
- exposed modulation input pins
- eventually sub modules and values / pins of the structure below the nested composer
Essentially a nested composer can then be used like an instrument with automaton targets.
FR: Allow automation of nested composer's automation parameters / modulation pins
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
That's possible. If composer X contains composer Y then composer X can automate composer Y's meta-parameters as well as all parameters of all modules inside composer Y.
So i'm not sure what you mean. Pls elaborate.
So i'm not sure what you mean. Pls elaborate.
-
- KVRist
- Topic Starter
- 164 posts since 27 Sep, 2004
This issue seems to be a duplicate for another FR I had.
Obviously MuLab already CAN do what I want - you simply can't select all possible targets from the target selection window. Most of the targets are missing there! Via drag+drop you can do it! And interestingly AFTER you have dragged+dropped a param from a module the rest of this module's params automagically appear as selectable targets.
So it's only a matter of adding ALL already possible targets to their fullest into the target selector window
Obviously MuLab already CAN do what I want - you simply can't select all possible targets from the target selection window. Most of the targets are missing there! Via drag+drop you can do it! And interestingly AFTER you have dragged+dropped a param from a module the rest of this module's params automagically appear as selectable targets.
So it's only a matter of adding ALL already possible targets to their fullest into the target selector window
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Please send a screenshot or screenvideo that shows what you mean.masterjoe wrote: Fri Jan 20, 2023 5:56 pm you simply can't select all possible targets from the target selection window. Most of the targets are missing there!
-
- KVRist
- Topic Starter
- 164 posts since 27 Sep, 2004
Sure, will do it on Monday eventually. I am on the road ATM.
But it's simple to reproduce. Add a composer. In that composer add another composer. And add a "Constant Modulator".
In the outer composer add a track with the generic "Add Track". Then select he target with "Choose Target Module". You can't reach:
- the nested composer's MP1...MP128
- the constant modulator's value (you can somehow add it but the mapping is broken)
Doing both via drag+drop works.
There are more cases. And I had one where a full structure was hidden and appeared after dropping in the first value. Not sure how I did that
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
A track can only be connected to a target module, not to a module parameter.
When a track is connected to module X it can contain automation clips to any parameter of module X. The easiest way to create an automation clip is to drag-drop the parameter on a relevant track.
An alternative way is when a track is connected to module X you can also right-click the track and choose "Add Automation Sub-Track". This simply creates a new sub-track for that same module X (or sub-module), with a new automation clip for the chosen parameter of module X (or sub-module). It's still possible to also put other clips for that module X on that track.
Tracks are very flexible. The only thing that defines/restricts/specializes a track is its target module. You can put anything onto any track as long as it is relevant to that track's target module.
Hope this clarifies things.
When a track is connected to module X it can contain automation clips to any parameter of module X. The easiest way to create an automation clip is to drag-drop the parameter on a relevant track.
An alternative way is when a track is connected to module X you can also right-click the track and choose "Add Automation Sub-Track". This simply creates a new sub-track for that same module X (or sub-module), with a new automation clip for the chosen parameter of module X (or sub-module). It's still possible to also put other clips for that module X on that track.
Tracks are very flexible. The only thing that defines/restricts/specializes a track is its target module. You can put anything onto any track as long as it is relevant to that track's target module.
Hope this clarifies things.