ASIO timing problems

muzza23 · Mar 4, 2003, 10:42 PM

im using kx v3530 on an audigy platinum ex, running logic platinum 5.5

whenever i use the asio driver in logic, the timing is slightly off, for example, drum sounds and synths often trigger slightly behind the beat... this happens with both audio tracks and softsynths (i run no outboard gear, everything is either audio or softsynths so it's not midi timing that's out)... when i switch to EASI Directsound in logic everything is perfectly in time, but things get slightly off when i use ASIO... just to be clear, im not talking about audio dropouts or clicks, just that the sounds in the tracks im working on are slightly off the beat.....

anyone else with the same problem? any idea what the problem might be, or how to fix it? i highly value asio's fantastic latency and i would prefer not to have to switch to another card to overcome this timing problem... thanks!!

kiawasch · Mar 5, 2003, 04:23 AM

hi

which audio configuration do you use in logic?

muzza23 · Mar 6, 2003, 05:39 AM

i only select one driver at a time in the audio driver window, so that when i use PCAV, all my objects are set to the PCAV port, and when im using ASIO, all my objects are set to the ASIO port... so basically, when all my objects are PCAV, the timing is fine, but when all my objects are set to ASIO then things get slightly off the beat

Leff · Apr 7, 2003, 11:30 AM

I've got absolutely identic problem. This one can be solved by setting as low latensy as 5 ms, but not every softsynth and not every PC could play without buffer underruns with such low latency... The reason why this mistiming occurs is that kX driver provides very inaccurate current sample position during playback. Accuracy depends on buffer size (latency). So this question goes to developers of kX Project.

TheKezmiester · Apr 7, 2003, 06:14 PM

Don't forget that the newer Logic versions have on-the-fly sample rate conversion. This may be good for some people with old songs recorded at 44.1K but it's a pain in the ass for the rest of us.
It eats up your CPU resourses and can mess with timing.

Remeber to change to 48000 before you start recording, it's better quality anyway.

**Eugene Gavrilov** · Apr 7, 2003, 06:18 PM

I'll have a look if it is possible to improve the timings...

/Eugene