ASIO Buffer damaged... stuck at 32!

Obermayer · 03-04-2019, 06:09 AM

After installing another Lynx AES card the buffer size in Reaper is STUCK at 32 and wont budge!

Reaper also goes into lockdown when selecting all available channels from the two Lynx cards, but when selecting only the first 16 inn/outs it will play, but the buffer IS STILL STUCK!

Obviously tried reinnstalling everything, messing with the Windows Inn/outs, removing old ASIO from HKeyreg, resetting Reaper settings etc. Nothing works!

To reiterate: The Lynx mixer and software is fine, until I start Reaper...
Please advise.

akademie · 03-04-2019, 06:20 AM

Is master/slave clock sync of the two cards set correctly?

Some info here:
https://support.lynxstudio.com/hc/en...s-to-a-system-

Obermayer · 03-04-2019, 07:09 AM

Quote:

Originally Posted by akademie

Is master/slave clock sync of the two cards set correctly?

Some info here:
https://support.lynxstudio.com/hc/en...s-to-a-system-

Yes, I'm a mastering engineer with 10+ years of experience so I usually dont have problems like this.. But thanks for the input

azslow3 · 03-04-2019, 09:49 AM

Quote:

Originally Posted by Obermayer

Yes, I'm a mastering engineer with 10+ years of experience so I usually dont have problems like this.. But thanks for the input

Then probably you can better describe what exactly is "stuck"...
Are you using ASIO? Then REAPER does not define the buffer size, it can "request" some but it is up to the driver to set or ignore that request. In other words, REAPER (or other app) is not able to set any ASIO settings on its own. That is up to the driver.
Note that any "request" (sample rate and block size) can confuse (badly written) drivers. Try to uncheck both and (pre)set parameters in the original (Lynx) software. Finally, check that Windows is not using Lynx or at least the sample rate is the same as you want to use in REAPER (fancy things can happened otherwise, and Windows is known for silent changing audio settings after changes in hardware).

Cableaddict · 03-05-2019, 12:19 AM

Obermayer, did you ever find a solution?

This just happened to me, after installing the newest Lynx drivers & FW.

I have a gig tomorrow morning, so not even time to call Paul!

I'm losing my mind.

Cableaddict · 03-05-2019, 03:39 PM

Bump.

Dos anyone know of a cure for this?

WyattRice · 03-05-2019, 05:18 PM

Wow.
Looks like Lynx took down there support forum, and they a have a new support ticket thing you fill out.
It's been awhile since I had been on there site.

@Cableaddict. Did the previous drivers work ok with Reaper?

Hope you guys find a solution.

I've used a Lynx AES16 PCI card for years now.
I had a driver problem one time a long time ago when I upgraded to a new driver, and I contacted David Hoatson, and he had me install the previous driver until they fixed the issue.
I've been updating the drivers every time since, and have had no issues.
I haven't updated the latest one yet that's listed on there site for January 17th 2019, as it says it's for PCIe, but the download is listed for legacy PCI cards too, when I click on the download link. Kinda confusing.
I'm using a Windows 7 64 computer that I built two years ago. Asus board Z170 chipset, Intel I6700K CPU.

Anyway, Hope you guys find out the problem, and post back with the results.
Regards,
Wyatt

Cableaddict · 03-05-2019, 08:02 PM

Thx, Wyatt.

I'm back home now and about to look into this further. Man, did I have a bad day! (gig)

I talked to Paul @ Lynx today, and he's never heard of this before. - And I've known him a long time, a very smart and a very honest guy.

I suspect it might be a Reaper bug, that only pops up once in a long while due to other system peccadillos. The problem is, I just new a full new OS / software install.

Gonna try an older version of Reaper first, then after that I have no idea ....

Cableaddict · 03-05-2019, 08:09 PM

BTW - Paul @ Lynx said the 2017 driver was designed specifically to allow stripped systems to run a 32 HW buffer, though at the cost of less stability as it no longer an extra cache. (i.e., more like how RME does things.)

That probably saves 1 ms or so, which would actually matter to me.

More interesting is that my system, running @ 44.1K and that 32 buffer, actually "just barely, sorta" works! I normally run at 88.2K, but have needed between a buffer between 256 and 512 for the last year or so. (and that's with the new, streamlined driver.) Fingers crossed that if I can get the ASIO setting stable, I might be able to do 88.2K / 128 buffer. That would be Heaven for live performance.

What have you been getting lately, with a decently-loaded session (maybe 5% total cpu) & going for the smallest buffer?

Obermayer · 03-08-2019, 06:57 AM

I never found a solution either, Paul could'nt help...
However, since the buffer seems to be controlled directly from the Lynx mixer, Reaper still reads the correct buffer size and the latency compensation seems to be correct...

Cableaddict · 03-25-2019, 10:19 PM

Yes, that's what I found as well.

It's just a reporting error!

- thanks.