Sending Midi Out
Sending Midi Out
So I have been trying to set up my ultimate midi controller for Arena 5. I am using various controllers like the NI Traktor F1, APC 40's, Launchpads and more. I am using Bome midi translator to set midi feedback for pad lights etc. One thing that I realize would be super helpful with getting pad controllers to light up just right, is sending midi information when a clip stops playing. For instance, I have a Traktor F1 pad controller, with Bome midi translator I can make a pad light up when I press it and simultaneously send midi cc/note info to resolume to trigger a clip on layer 1, column 1. With midi mapping I can make the pad trigger the clip. That is great, but I would love the light on the pad to change/turn off when the clip is done. For this to work Resolume would need to send midi data out to my controller once the clip finishes. I can't find any info on assigning midi out for various events. Mapping midi inputs are great, but is it even possible to do the opposite?
Re: Sending Midi Out
Resolume works with a midi feedback system. What you map on the input side, gets sent as output back to the controller.
So when you have a midi note mapped to a clip trigger, a note on will be sent out when that clip gets triggered either via the controller, mouse or automation. How it's triggered doesn't matter, the note on always gets sent. Similarly, when the clip is ejected, a note off is sent.
Now columns are a bit of a special case, because a column is just a collection of clips. It doesn't really have a playing state, and triggering it is just an event. When you trigger a column, an event is sent to trigger all the clips in that column. After this event, there is no guarantee how long that column remains "active". The user is free to trigger individual clips from many different columns, and it would be strange if the original column would still be marked as active after one or more of the clips in it have been ejected.
So in short, you can get midi feedback for playing clip states very easily. Just not for columns.
So when you have a midi note mapped to a clip trigger, a note on will be sent out when that clip gets triggered either via the controller, mouse or automation. How it's triggered doesn't matter, the note on always gets sent. Similarly, when the clip is ejected, a note off is sent.
Now columns are a bit of a special case, because a column is just a collection of clips. It doesn't really have a playing state, and triggering it is just an event. When you trigger a column, an event is sent to trigger all the clips in that column. After this event, there is no guarantee how long that column remains "active". The user is free to trigger individual clips from many different columns, and it would be strange if the original column would still be marked as active after one or more of the clips in it have been ejected.
So in short, you can get midi feedback for playing clip states very easily. Just not for columns.
Re: Sending Midi Out
That is super helpful to know that note off is sent once a clip ejects. So I understand the terminology correctly, "ejection" is any time you select a different clip on a layer (or deselect all clips on a layer) is that correct? If that is the case I should check and see if it sends cc data back out the same way it does note on/off midi is sent.
Thanks!
Thanks!