Cubase MIDI Recording strangeness
-
- KVRist
- 347 posts since 6 Nov, 2004 from Glendale, California
Whenever I record Midi, it always gets shoved somewhere between 4 and 5 16ths bacwards and this makes a synth line that i'm recording in realtime suddenly become out of beat.
this doesn't happen with MIDI CC, only with notes.
Im puzzled. The "Auto Quantitization" is off, and i don't see an option anywhere for midi latency adjustment.
also, the latency from my keyboard (midiman Oxygen8) is very low, as time from the press of a key to delivery of the note on a synth is instantaneous to my ears.
I'm going to consult the manual more thoroughly now.
Thanks.
this doesn't happen with MIDI CC, only with notes.
Im puzzled. The "Auto Quantitization" is off, and i don't see an option anywhere for midi latency adjustment.
also, the latency from my keyboard (midiman Oxygen8) is very low, as time from the press of a key to delivery of the note on a synth is instantaneous to my ears.
I'm going to consult the manual more thoroughly now.
Thanks.
- KVRAF
- 19156 posts since 13 Feb, 2003 from Vancouver, Canada
I have this problem at work too (Nuendo), but that's a rather complex setup involving a MOTU timepiece, an O2R, A/D converter, some ADAT's and a sheep.
I know the old VST32 Cubase had a setting where you could offset the MIDI by ticks (or ms, can't remember), but I don't think it's been put into Nuendo/Cubase yet. Maybe someone else can illuminate us?
I know the old VST32 Cubase had a setting where you could offset the MIDI by ticks (or ms, can't remember), but I don't think it's been put into Nuendo/Cubase yet. Maybe someone else can illuminate us?
- KVRAF
- 2686 posts since 5 Feb, 2004 from Nevada City, California
i'm not sure about the solution - but what audio/midi interface are you guys using?
and in cubase does it say "(emulated)" beside the midi port name..?
and in cubase does it say "(emulated)" beside the midi port name..?
-
- KVRist
- 360 posts since 23 Feb, 2001 from San Rafael, California
Long known problem with SX... one thing that sometimes helps is the reset button in the midi setup page. There is also a setting that affects timing (use system time or something like that), try switching it the other way...
-
- KVRist
- Topic Starter
- 347 posts since 6 Nov, 2004 from Glendale, California
My soundcard is an Audiophile 192 (but that shouldn't have anything to do with midi, right?).
My Oxygen8 is connected with the USB cable and software. The port does say "Emulated".
Where's that "Use system time" setting, cause Reset did nothing.
ERGHH.
I may have to mixdown and record in ext.
Thanks guys.
My Oxygen8 is connected with the USB cable and software. The port does say "Emulated".
Where's that "Use system time" setting, cause Reset did nothing.
ERGHH.
Thanks guys.
- KVRAF
- 2686 posts since 5 Feb, 2004 from Nevada City, California
hmm.. i never had midi timing problems with my audiophile 2496, but the BCA2000 did almost exactly what you describe..
do you have any ports that are not listed as emulated?
you may have to move the ignoreport filter file - i think its in the 'MIDI Port Enabler' folder...
do you have any ports that are not listed as emulated?
you may have to move the ignoreport filter file - i think its in the 'MIDI Port Enabler' folder...
-
- KVRist
- 360 posts since 23 Feb, 2001 from San Rafael, California
In the Device Setup Window, there are 2 subsections under Midi, that say "Direct Music" and "Windows Midi". Both have a checkbox that says "Use System Timestamp" check or uncheck those and try again...pannewb wrote:Where's that "Use system time" setting, cause Reset did nothing.
-
- Fearer of cheese
- 3216 posts since 12 Mar, 2002 from UK
Hi pannewb,
You could try this MROS update, botton of the Midex 8 driver page http://www.steinberg.de/DocSupportDispl ... roduct_ID=
This supposedly helps with midi timing problems in Cubase.
I posted about this@CM forum http://forum.midiaddict.com/viewtopic.p ... g+problems but the link I gave there is no longer valid.
You could try this MROS update, botton of the Midex 8 driver page http://www.steinberg.de/DocSupportDispl ... roduct_ID=
This supposedly helps with midi timing problems in Cubase.
I posted about this@CM forum http://forum.midiaddict.com/viewtopic.p ... g+problems but the link I gave there is no longer valid.
RIP Black Tom and Beckett. They weren't just cats, they were MY cats, the best cats ever.
-
- KVRist
- 274 posts since 30 May, 2005
is it a prob if the port has the word emulated next to it in cubase sx... coz when i use the triton at times thru usb, it always says emulated next to the port name///ford442 wrote:and in cubase does it say "(emulated)" beside the midi port name..?
- KVRAF
- 2686 posts since 5 Feb, 2004 from Nevada City, California
from what i've read - the 'emulated' port can cause problems like what you've described.., but not always - one thing to try is to move the file 'ignoreportfilter' out of the 'MIDI Port Enabler' folder before you launch cubase - that may give you more options in the list of midi ports..
- KVRAF
- 19156 posts since 13 Feb, 2003 from Vancouver, Canada
That's a long known issue? Damn, I wish I'd known that going in...c_huelsbeck wrote:In the Device Setup Window, there are 2 subsections under Midi, that say "Direct Music" and "Windows Midi". Both have a checkbox that says "Use System Timestamp" check or uncheck those and try again...pannewb wrote:Where's that "Use system time" setting, cause Reset did nothing.
I'm going to try that timestamp setting. I've never tried that before, hopefully that'll do it. Sometimes I just think I have the worst luck with soundcards...I'll see how this works, thanks for the tips!
-
- KVRist
- 157 posts since 15 May, 2005
Ther system timestamp was added in Sx2 (I think) for Direct Music drivers, and was added in 3.1 for Windows Midi drivers.
There appear to be a lot of cases where the 3.1 addition of timestamp has cured the problem (see the Cubase forums).
Note: start with the ignoreportfilter file moved into the Midi port enabler directory, so only the Windows Midi and Direct music ports show up, and then try with and without timestamp for the respective drivers.
http://forum.cubase.net/phpbb2/viewtopic.php?t=25976
http://forum.cubase.net/phpbb2/viewtopi ... idi+timing
http://forum.cubase.net/phpbb2/viewtopi ... idi+timing
There appear to be a lot of cases where the 3.1 addition of timestamp has cured the problem (see the Cubase forums).
Note: start with the ignoreportfilter file moved into the Midi port enabler directory, so only the Windows Midi and Direct music ports show up, and then try with and without timestamp for the respective drivers.
http://forum.cubase.net/phpbb2/viewtopic.php?t=25976
http://forum.cubase.net/phpbb2/viewtopi ... idi+timing
http://forum.cubase.net/phpbb2/viewtopi ... idi+timing
-
- KVRist
- Topic Starter
- 347 posts since 6 Nov, 2004 from Glendale, California
Thanks for all your help, guys.
There was a non-emulated version of the port, and i chose that. I also used System Timestamp for DirectMusic ports.
And one of the two (or maybe both) fixed it.
Thanks again, and bduffy, I hope this sorts your prob too.
There was a non-emulated version of the port, and i chose that. I also used System Timestamp for DirectMusic ports.
And one of the two (or maybe both) fixed it.
Thanks again, and bduffy, I hope this sorts your prob too.
-
- KVRist
- 274 posts since 30 May, 2005
OKay now, i'm a bit curious ,,, what exactly is this 'emulated port' and why does it appear as emulated, and what does this signify ....

- KVRAF
- 2686 posts since 5 Feb, 2004 from Nevada City, California
according to this - http://service.steinberg.net/knowledge_ ... midi_ports
"DirectMusic mirrors the Windows MIDI ports as "emulated" DirectMusic ports..."
"DirectMusic mirrors the Windows MIDI ports as "emulated" DirectMusic ports..."