Hi,
On a track assigned to cv/gate, how can I assgn that specific track’s automations (CC) to a specific MIDI channel ?
1 Like
Could you specify what you want to send from where to where?
On a track that is mapped to CV/GATE, I would like to send automation informatin to a specific midi channel.
I’m afraid you can’t. Currently the only options for midi automation output on a track is the midi output port+channel of the current track, or cv on any of the cv outputs.
I really hope they will allow a track to output midi to another track or another midi port+channel. For example: the envelope effect on a kick drum should actually duck the volume of the bass track. Currently you can only do this if your bass synth allows cv to volume (like Minitaur).
2 Likes
1 Like
Thanks for your answer, hoping for that feature too 
if you could route a track to a specific midi input port and channel that definitely would open up possibilities! internally i mean. but you can already do that with a cable or loop back utility running on a computer module lol
Hi. Has this been implemented? I also have several use cases where the cc of a track needs to be set to a other channel than the track channel. I need for instance a CC number go to to 1 channel and at the same time have a different curve with same cc number go to a different channel. Both in same lane:
Use cases
A) hardware effect using different channel than the synth, but must be controlled from the same lane.
B) drum kit on 1 hapax lane controlling drums in different midi channels on eurorack assimilator in multimode. Each drum has separate midi channel, and each of the drums needs a same cc number on different Channel to select the Assimilator zones. Assimilator multi vz mode is not an option because I still need to be able to change the velocity of the drums.
2 Likes
please dont forget to make a request via the contact page
Feature Request created on contact page 
1 Like
This would be incredible! FX automation being a part of a instrument track.
Ideally, if it was possible to load 2-3 “FX definitions” per track, which would than extend the list of automation lanes.
Nevertheless, I believe separate MIDI channel is severely limiting proposition - it would most often work for the suggested case B , but for the case A, many of us will have our FXs not only on a different channel, but also on a different MIDI output!
Therefore I think even the most simple implementation must allow to specify both output port and MIDI channel if we want to fulfill the outlined use cases.