Reverse Latency...What the *!#%$~?

[mark4man]

Well...here's an interesting phenomenon.

Ever since I've been recording @24-Bit/96Khz (&...I'm not certain that's related, but...), whenever I record an FX loop track with my effects processor (Lexicon MPX-500)...

...the timeline location of the wet track appears ahead of the source track...by about 4 ppq's ! (on a 120 Ticks per Quarter Note scale.)

What in tarnation ?

The routing is: SONAR (source track) Layla24 3/4 Analog Out > MPX-500 Analog In > Lexicon FX applied > MPX-500 Analog Out > SONAR (recorded track) Layla24 3/4 Analog In.

Check out the .jpg screen shot of the two tracks in question, from the SONAR project:

http://members.bellatlantic.net/~vze3yjbu/TrackFX.jpg

I realize it is impossible (within the realm of the physical sciences) to actually record the secondary track prior to the primary track playback...

which means that SONAR must be writing the track ahead of it's markers?

Anyone experience this before? Any ideas?

Thanks,

mark4man

 

[mixsit]

Over on Cakewalk's Sonar forum there were some threads regarding folkes wanting external tracks to be time compensated. Part of it extended to measureing and charting different drivers, settings, ect. Some combinations did that as I recall -as if the internal tracks ended up slid back.
Might want to check those out.
Wayne

 

[moskus]

I have that problem too.

Move the track is the only sollution, I think.

 

[mark4man]

mixsit,

Responded at Cakewalk site...thanks.



moskus,

Have any idea as to why?

Thanks,

mark4man

 

[moskus]

I'm suspecting a driver error...
The problem was alot bigger before the latest version of my soundcarddrivers.