Midi finished, Going to Audio--trouble city (by JD)

An area for people to discuss Scope related problems, issues, etc.

Moderators: valis, garyb

Post Reply
Guest

Post by Guest »

This has probably been discussed but my searches did not reveal the answers I was looking for, so here are my problems. My midi track is finished (Cubase 5.01) and I now working on going to audio. This process has revealed two problems to me upfront.

1. First thing i did was convert my midi kick track to an audio track. however, when i looked at the timing position of my audio kick it was not at 1.01.0 but had been pushed forward to 1.01.12. (working with 384ppq) my thought is that since the audio has to be run through the synth, bigmixer, out the bus and then to Cubase some latency will result. However, is there a way in cubase to adjust my midi tracks timing (globally) before recording so that it lines up to 1.01.00 when it comes into cubase. I'm not just talking about individual track delay but some global offset. This would prevent me from having to go back to each track and slide it back to 1.01.0. Simply put would make my midi to audio process more effecient.

2. This problem is a bit more troublesome. I have a bass line played through the Uknow07 which i now want to make an audio track. i record it to audio and the same thing happens 1.01.12. so i pull it back to 1.01.0. in the audio editor. But as i continue to look at the audio i see that in the next measure the audio has moved ahead to 2.01.06. Thing is, it is all one single wave. Everything should have moved back when i moved the wave the first tme. I check my midi track to make sure that the midi event was actually landing on 2.01.0 and it is. more troublesome is that as i look at each note in the audio editor it seems there is no pattern to the delays. some notes land on the beat others drift. i thought at first it was because i had only 1 voice for the patch and that the note wasn't finishing before another note was triggered thus creating the delay, but when i increased the voices same thing happened. Either i'm missing something or the midi handling inside of the pulsar synths (Or Cubase) is crappy. since i'm doing dance music i need tight timing, but if i can't remedy the situation then i will have to chop up each phrase and move the events to the midi reference positions.

3. Final question. Since i haven't converted my external gear tracks to audio yet i don't know if i will experience that same drifting. but if someone has exstenise experience in this area they can comment on midi timing as a whole. perhaps there will always been some midi drifting. i've read and heard that time pieces by motu and emagic produce rock solid midi timing. (currently using midiman usb 4x4 for external gear). does mac perform better than pc for internal midi timiing? eg sequencer to the pulsar synths. basically i want the solid timing to increase the effeciency of my projects.

Cheers and thanks to all who respond.
JD

PIII 800
ASUS CUSL-2C
Pular I and Pulsar II
SB Live through S/PDIF
256 Ram
Maxtor DiamondMax 30G
MidiMan 4x4 USB
Cubase 5.01
Post Reply