Posted
There seem to be two problems when using the Cubase Export -> Audio Mixdown function to bounce multple audio tracks from VST tracks.
1. If I'm storing the midi in the drones and exporting like that I get what seems to be sync problems with the midi being exported, some notes appear a bit out of sync. The stereo bounce seems fine its only the multi-track VST bounce that has this problem.
2. If I've imported the MIDI file from Synfire into Cubase, set the drones to local, the stereo export works fine but if I had previously exported midi to DAW and the midi is still in the drones it will also play during the multi track bounce. I tested this by offsetting the midi tracks in Cubase one bar back and then I can clearly hear the midi in the drones being played out in the bounce. To work around this I have an open empty project in Synfire and do Export midi to DAW to clear the midi from the drones.
Sun, 2012-02-12 - 17:52 Permalink
Interesting questions. Although I have no answer yet.
I suspect that, during the bounce, Cubase can not anticipate MIDI data because it is hidden in the drones rather than being stored on a Cubase track. This may break its delay compensation or something.
You should perhaps capture the audio output per each instrument and Cubase track, then eliminate the MIDI and do a pure audio-based bounce after that.
Sun, 2012-02-12 - 22:20 Permalink
I found a workaround that works fine for nr 2. and it does make sense to really add the midi to Cubase at the end of the process but maybe it would make sense to somehow show in the drone UI that the drone has internal midi hidden inside and maybe even a way to clear it from the drone UI? But it is strange that the midi is leaking out from the drone only (even if set to Local) when bouncing VST tracks but not in the Stereo bounce or in playback.