Jump to content

CC nightmare!!!


  • You cannot reply to this topic
No replies to this topic

#1
pan_down

    Gold Punk

  • Members
  • PipPipPipPip
  • 263 posts
G'day All,
              really struggling to get the cc thing happening correctly at the moment, have tried to lay it out as clearly as possible, hoping someone has come across this before?

Basically I've got a moog voyager connected to logic  [ audio via motu ultralite, midi via edirol usb converter ].

I'm getting issues with MIDI conflicts as certain parameters on the voyager are recognized as completely different ones by logic. E.G. When I tweak Oscillator 2 Frequency on the moog, it sends CC data on CC #10. In the logic MIDI control / automation list however, #10 refers to PAN so when i tweak osc2freq, its changing the Pan on my channel in Logic. A more severe example is that something on the moog seems to transmit on CC#120 which is currently assigned to 'all audio off' in logic - has killed a couple of my projects.

What I need to do is somehow modify / disable the default MIDI control list / set that appears in the automation / piano roll drop downs on the [external midi instr.] channel i've created for the moog to avoid these conflicts.

I've tried creating a new Hyper set, however these controls do not seem to override the default automation control set in case of duplication ie, cc#10 data just controls osc 2 freq AND pan on the channel.


I've also looked at the controller assignment window and learn mode but this seems to relate more to mapping au controls to ext controllers.

If anyone could help me out here it would really be appreciated, I've got a killer synth here that i can't get the most out of until i get this sorted...

thanks :D





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users