Skip to main content

Drones Not Passing All Midi Tracks From MultiTimbral Sessions of Kontakt in Cubase 9.01

Posted

Hi all.

I've been working with Synfire Pro for a couple of weeks now and really love this program. And yes, the learning curve was steep on this app (like an Adobe app) but that just means it's functions and the possibilities go deep which is a good thing.

I set up drones in Cubase 9.01 (iMac with OSX 10.12.2, 4.0 GHz i 7, 32 GB MHz) step by step while watching the newest youtube video on how it's done.

When I moved the midi from the drone to the track - only the first midi instrument's midi moves. (i.e. Kontakt set with a guitar on A1 and a piano on A2 and the tracks run fine in Synfire.)

In the video under what seems to be the same circumstances two midi tracks move and the video host is then required to set up another midi track and move the second track and then route the track to the Multitimbral Kontakt instance.

So that didn't happen for me.

Does anyone have any suggestions as to what I might or might not have done? (even though it seems I followed the steps exactly.)

A second question - Should containers matter when moving the tracks and if yes then how do they matter?

Thank you anyone and everyone and wishing you a good New Year.


Mon, 2017-01-02 - 20:58 Permalink

Thanks for the positive feedback, davidisinla.

If there is more than one instrument rendered by a Drone's plug-in, the drag & drop export will also include an equivalent number of tracks. Maybe in your example one track is empty (muted?) and thus ignored by Cubase?

However you should note that if you drag from the arrange window, only the instrument you grabbed is dropped. Only if you drag a whole container, or drag from the Drone's user interface in the DAW, you will get multiple instruments in one drag.

The Drone will always export the entire song worth of MIDI. All containers flattened.

If you want to export a single container only, you'll need to start you drag in the arrange window in that container. 

Fri, 2017-01-06 - 23:36 Permalink

Thank you both for the answers. I haven't gone back to that project and today on a new project the drones were working fine. It was probably caused by having one unused node in Kontakt between two used nodes - (that's sort of a question/statement)

Andre said:

"Maybe in your example one track is empty (muted?) and thus ignored by Cubase?"

So A1 was an instrument that passed the midi. A2 was an unused instrument. A3 was the instrument that didn't pass the midi. Could that of been the issue?