Sending ghost control messages...

Having a problem with Kontakt 4. Everytime I press playstart it pushes the volume of the first piano instrument. If I press Play...the volume will stay where I set it. When I try to fix it via CC...it will continue to do it. Anyone else having this problem?

I havent tried it in Kontact, but I have in Omnisphere. And the midi CC learn function was not on par at all.

I was wanting to put my scroll functions on the cursor. And it was a no go, but it would assign to the q links. with real bad response to were if you turn the knob all the way around it would barley scroll.

Also have been trying to midi cc learn pads to abelton with little luck. I can do the transport controls. And thats it.....

When a plugin is inserted on a Track, it's volume is controlled from the Ren's Track Mixer which is maxed by default. Upon Play Start, the Ren's Track Mixer is sending MIDI volume to your plugin.

As far as mapping Qlinks to plugin instruments, it will very depending on your plugin instrument. If you are having issues with using the MIDI learn function of your plugin, trying using the automation functions in your plugin.

Clarification......

From my understanding....when you have a Plugin Track in the Ren, its Qlinks can be mapped directly to available plugins parameters. This doesn't appear to be via MIDI CC messages. Within your plugin instrument, look for its automation assignments. You can assigned the plugins knobs so that can be automated by the host. Once this is done, these params will show up in the Ren. And you map Qlinks directly to these params. Your plugins MIDI learn will most likely not work. If it has Automation learn, that it will. This is the case with using Battery 4 inside the Ren.

When you have a MIDI Track in the Ren, its Qlinks can be assigned to MIDI CC#s. These Qlinks can be mapped to params in your external sound module. They can also be mapped to other plugins with your DAW.