KVR Audio

dollanaire · Post by **dollanaire** » Sat Jul 23, 2005 1:44 am

I don't know why but for some reason when I am recording a midi track, the notes show up about a half a measure before ... for instance, if im recording a hi hat and I hit it exactly on beat 2-1 then it shows up on the screen at 1-4. My input and output latency for my m audio 10-10 soundcard is around 9ms. PLEASE HELP GUYS.

P.S. no auto quantize or anything is on, I just actually see the notes show a half measure before the play status line when Im recording

NoLimits3D · Post by **NoLimits3D** » Sat Jul 23, 2005 2:05 am

Well, is there any delay between hitting a note and hearing it play through your speakers?

Scotrick · Post by **Scotrick** » Sat Jul 23, 2005 5:40 am

you've got to do research on the ignore port filter... I think it'll proabably show up here if you do a search for those terms, but if you for sure do a search at either the neundo or the cubase forums... to make a long story short, Cubase and Nuendo, with some MIDI interfaces, have a mismatch between the system timem, at a clock level... due to some weird Windows stuff... I've read it all a couple of times and still barely understand... but the but the upshot is you move the ignore port filter up a directory level, and then you can see 'all,' of the MIDI ports for your device... and with a process of elimination try each MIDI port until you find the one that works... you're looking mainly for the difference between the emulated and the hardware ports...
good luck

Bas · Post by **Bas** » Sat Jul 23, 2005 8:42 am

In my free SX2 guides there is an explanation of this problem, and (for most) an explanation of the fix. See page 22 of the SX2Project pdf

Note that another option had been added for DirectMusic drivers since I produced the book, use system timestamp. That allows the timestamp from the driver to be used to place the notes correctly.

As an overview the problem lies with the fact that different cards provide different software Interfaces. The preferred model is the diredctmusic interface, but some USB devices provide only WIndows Midi, and directmusic creates emulated ports for software that requires DM ports. These generally do not work well, but in some cases, they are the only that do work.

So some trial and error is required to find the correct ports. WIth the addition of timestamp for the Windows Midi ports (due in SX/Nuendo 3.1) the setup (in theory) should allow all devices to be used successfully.

Teksonik · Post by **Teksonik** » Sat Jul 23, 2005 9:18 am

Why would a $599.00 sequencer have this problem?
(Nuendo $1999.00)

Bas · Post by **Bas** » Sat Jul 23, 2005 11:41 am

I am not a programmer, but I do know that certain hardware has problems in this respect, but using the ASIO4ALL driver on the same hardware cures the problem.
How can any manufacturer hook up to drivers and hardware if they don't all present the expected software hooks to ensure that the system works?

In an ideal world every hardware device would present exactly the same features to all hosts (via the driver), but they obviously don't, as the driver change on certain cards proves.

BTW with 3.1 the fix is supposed to be in place for drivers that present timestamp via the Windows Midi interface. So (assuminbg that drivers have at least one fully specced driver interface) then the setup may still be required, but once done, it should be solid on all systems.

VISIBLE MIDI LATENCY ON NUENDO 3