Problems with midi key mapping!

[banicos]

Hi!

I'm using a M-audio x-session midi controller with resolume.

I'm controlling x-fader, layers opacity and composition effects without problems.The problem is to mapping the clip controlling (pause, play, reverse), for example when i assign a button to "play" resolume assign me to "reverse". Anyone can help me?

Other question, when i assign this buttons, they are only assigned to that clip, right? it is possible to control all the clips with the same shortcut?

Hope guys undertand!
Many Thanks!

[Joris]

when i assign a button to "play" resolume assign me to "reverse"

Not quite sure what you mean there, could you explain it in different wording?

it is possible to control all the clips with the same shortcut?

In the View menu, turn on the Layer Transport Controls. This will allow you to map the controls of the clips currently playing the layers.

Hope that helps.

Joris

[banicos]

Hi!

Thanks for the help! What i mean is that when i assign a button to "play", resolume automatic re-assign to "reverse". (sorry, my english is not very good )

Thanks!

[Joris]

Ah! If I understand correctly, you want to toggle between forward and reverse with one and the same button? If that is the case, unfortunately that is not possible. R2 had this feature, but it was dropped in favour of having greater control of the playback.

[Vjcheshire]

I am having a similar problem with Resolume 3 and midi mapping the play, reverse, and foward buttons on certain controllers. Using touch osc (via Ipad & nanokontrol 2) If you try to midi map these keys to separate notes on a controller, maps all 3 keys to the random button. So when you press the 3 different midi mapped keys it goes to random, then on release it goes usually to reverse.

[Joris]

Hey VjCheshire

Make sure you're sending midi notes (and not cc's). Then it should work correctly. You can tell the NanoKontrol to send notes via the Korg Editor app.

Joris

[Vjcheshire]

OK I'll try that and see what happens. The new nanokonrtol 2 seems a bit flakey so far. I'm guessing it would be the same error with the Ipad/Touch osc sends as well?