ASIO Delay Compensation in SONAR 4

  • Thread starter Thread starter mark4man
  • Start date Start date
mark4man

mark4man

MoonMix Studios
Was the delay compensation issue for ASIO drivers resolved with the release of SONAR 4?

In my case, audio recorded w/ ASIO was 20.815ms ahead of audio recorded w/ WDM (at 44.1); & I was hoping the issue was resolved (before I go ahead & upgrade.)

Thanks,

mark4man
 
I don't recall there being an issue with delay compensation. My recollection was that there was a problem with envelopes which was caused by VST delay compensation in the VST adapter. This issue was resolved, to my knowledge, with the release of the VST adapter patch.

Also, to my knowledge, this had nothing whatsoever to do with the ASIO driver. The issue is with VST plug-ins and is independant of the driver mode being used.

Have you opened the adapter to insure that you have delay compensation enabled for the plug-in you are having the problem with?
 
dachay,

No...this was a different issue, where users of SONAR running ASIO drivers had recorded audio positioned either early or late by a certain # of samples (which was usually specific to buffer size...usually.) I. e., it was a sample accuracy issue.

My AI mfg. (Echo Audio) told me it was DAW ASIO related; & some folks were hoping it would be resolved with the release of v4.

mark4man
 
I remember the issue when it was raised over on the Cakewalk forum.

My takeaway from the eleventy-thousand pages of discussion was that there was no clear consensus between any of the users concerning whether WDM or ASIO drivers exhibited one consistent behaviour.

Consequently, their investigations seemed to show that software driver version seemed to have more of an impact on the "reverse latency" issue than the Sonar engine itself. For example, there were people posting saying that they had tried different versions of WDM and ASIO driver, not changed any settings in Sonar and were getting wildly different results.

From this, the only conclusion I could come to was that the whole issue related to how the ASIO or WDM driver was passing information to Sonar's audio engine. My understanding of Sonar's engine is that is uses its precache buffers to read the streamed audio, tag it with a timestamp, pass it to whatever FX buss and then return it to the master output. To do this, it must be getting a reliable feed of information from the driver, if not, well -- that's when we see this type of issue.

FWIW - I use an Aardvark Direct Pro 24/96 with ASIO drivers set to a 4.5msec latency in Sonar. Using the 7.13 drivers, I cannot replicate the "reverse latency" issue at all. With the older 7.04 drivers, I can replicate that behaviour.

So said, ignore it, record, zoom in and drag stuff around when you need to. Don't get hung up on the small stuff and keep having fun!

Ciao,

Q.
 
Q,

Consequently, their investigations seemed to show that software driver version seemed to have more of an impact on the "reverse latency" issue than the Sonar engine itself. From this, the only conclusion I could come to was that the whole issue related to how the ASIO or WDM driver was passing information to Sonar's audio engine.
Click to expand...
Well...then I'll just have to live with it, becuase Echo Audio has released their very last drivers for the old Layla 24/96 (I got 'em...& they're beta's...not even certified.). Now they're on to the Layla 3G.

I think what I'll do (in keeping with your "make the best with what you have" advice) is simply record in WDM & bounce in ASIO.

Thanks all,

mark4man
 
You must log in or register to reply here.
Back
Top