Cubase VST users - recorded MIDI data not in sync with what

hesnotthemessiah · Post by **hesnotthemessiah** » Mon Mar 06, 2006 7:13 am

The midi data need to be dragged back by "X" amount within Cubase VST5 after I have recordered it. The "X" amount differs from session to session but all the recorded midi data needs to be moved by the same amount. I have just tried the "Reset Devices " option (as advised at the Cubase forum) and this seemed to cure the problem - when I recorded midi data after doing this, all seems fine, but this needs to be done evertime I record midi data.

Now I know this problem has been discussed a few times on this forum and also at the Cubase forum, but no specific solutions seem to have been discovered for problems involving Cubase VST5 (or any other version of Cubase VST where the problem arises). I would really like to know if anyone else using a Cubase VST/Creamware card combination has come across this problem and if they have managed to get it working correctly again.

Thanks.

Herr Voigt · Post by **Herr Voigt** » Mon Mar 06, 2006 4:30 pm

As posted several times at problems and tips/tricks forum: If you have xp, run dxdiag and disable direct draw acceleration. It works for vst 5.1, too. Since I did this tweak, I have no more midi timing issues.

Best, Thomas

hesnotthemessiah · Post by **hesnotthemessiah** » Tue Mar 07, 2006 11:15 am

On 2006-03-06 16:30, Herr Voigt wrote:
As posted several times at problems and tips/tricks forum: If you have xp, run dxdiag and disable direct draw acceleration. It works for vst 5.1, too. Since I did this tweak, I have no more midi timing issues.

Best, Thomas

Hi Thomas. Thanks for the response. Have run dxdiag today and have disabled the direct draw acceleraion. I have not tested my audio PC yet to see if there has been any change. Were your midi timing issues the same as I described in my post? I will test Cubase once I am back from work and MIDITime has finished it's diagnostics.

I am currently running the utility MIDITime. I think my problem has something to do with Windows using two clocks and timestamping of incoming midi data using one of these clocks by the sequencer. MIDITime tests the midi interface to see which clock the midi interface uses. Sorry if this is a bit vague as I am having trouble trying to understand it myself.

I think the problem could be something to do with my midi interface and Cubase using different clocks, or it could be something to do with "emulated drivers" which is something else I can't quite understand either.

Perhaps I should look at stamp collecting?

H-Rave · Post by **H-Rave** » Tue Mar 07, 2006 11:57 am

I've had this problem alot when using java programs and when I run the asio sync test I lose alot! of samples.have you set the buffer size to 5292 samples,you didn't say.

Herr Voigt · Post by **Herr Voigt** » Tue Mar 07, 2006 2:57 pm

Well, I'm afraid that this topic will be too much complicated for me. I have no knowledges about timestamps, different clocks etc.
I can only say, my setup works for me. I have a middle MIDI interface (MIDISport 4x4 USB) and make all my MIDI recordings over this way. My scope MIDI i/o I only use for my Doepfer pocket dial, when I drive sound tweaks with my scope synthies. Then the timing is not so important, I always draw my corrections in the cubase parts.
I hope that a (MIDI-)guru from here can continue the help.

Best, Thomas