feature request: midi CC for toplevel system audio #465
Comments
|
agreed, this is a feature i'd like to add. this is actually possible within the script, but you'd have to manually map the cc. to change the "global" audio params, see the for example, if you'd like to send unity gain of mlr to the reverb:
and then back to -60db
|
|
FYI i'm possibly going to rename to |
|
so it would look something like:
...inside the mlr script, or perhaps manually coding a CC assigned to the aux send, alongside my saved mlr params for CC-mapped track volumes? this could be a way to also specify midi-controlled per-track fx sends, assuming there's a framework in place to do so before everything runs back into mlr's mixer to the global audio output. |
|
@tehn, @nightmorph is this something we need to add in norns? or can we leave it as a script feature? |
|
the feature is to have cc mapping on-the-fly via menu same as script parameters. we're planning to combine the system audio menu into the parameters menu, as discussed with @markwheeler so we can close this. |
it would be great to have midi control over things like aux fx send/return volume, fx parameters, input/output volume, and such. right now, it seems the only things that can have CCs assigned are a few parameters inside individual scripts. there doesn't seem to be a way to map anything at all outside of a script.
example usage:
a live performance with mlr. while mlr exposes a few per-track params such as volume, it would be fantastic if my nanokontrol could not just cover those, but also bring in the system's aux fx as desired.
i also have ideas for the old mlrv-style "press/hold buttons to toggle reverb/delay fx" on the grid itself, and also per-track fx sends (is that even possible, or is each dust script sending all its output to the system aux fx?), but those are probably best placed in a dust/mlr feature request.
The text was updated successfully, but these errors were encountered: