thanx for your reply gpvillamil
If this is the case, make sure that Resolume *only* has MIDI input enabled on the virtual port coming from Live, otherwise it will be seeing MIDI from both the controller and the virtual port, and will get confused. I think that this is maybe what is happening in your case.
the computer wich runs resolume only gets midi from firefly midi in, all the rest are disabled
Another option is to have MIDI from controller -> Live on one MIDI channel, and from Live to Resolume on another MIDI channel.
i dont know how to do this.. i cant figure out how to have a specific midi channel to be sent from my controller.. coulnd find anything in the manual so fast.. i guess its possible becouse there is a knob with "CH"
And even another option (using MIDI Yoke) is to send MIDI from the controller to a virtual port, and then have both Resolume and Live take input from the same virtual port, like this:
Controller -> virtual MIDI port #1 -> Live
hmm, midiyoke is just a driver, isnt it? hasnt got a config menu somewhere... i dont realy know how to patch midi signals... would be nice to have a reason-like UI for that
i did some experimenting within ableton with 2 midi tracks. 1 having midi in from the controller. and then another one listening to the first track and relaying it to the midi out... no sucses
another thing is that i cant seem to control resolume with recorded cc from ableton.....
i made a list of setups i tried:
bcr controller -> usb -> ableton laptop -> firebox midi out -> phonic firefly midi in -> resolume pc... = lag
bcr controller -> midi out -> firebox midi in -> ableton laptop -> firebox midi out -> phonic firefly midi in -> resolume pc... = lag
bcr controller -> usb -> ableton laptop -> midi yoke via ethernet -> resolume = lag
korg nano -> usb -> ableton laptop -> firebox midi out -> phonic firefly midi in -> resolume pc... = lag
in all cases clip triggering works as it should...
and in all cases resolume was just listening to one midi in
also tried running both ableton and resolume on the same machine... and the problem is the same
to be continued......