Gearslutz.com - View Single Post - Lynx, Cubase 4 WinXP, multiple UAD users: Can anyone confirm or refute this?

drmad69 · 7th May 2008, 06:06 PM

The two LYNX's fighting is common in my experience.

I even had one that was a src; and it didn't matter..

This is the reason for the secfet control screen and the PCI throughput numbers.

One card will was always 50% worse then whatever ended up being

the primary card on the buss...

FWIW, I did mess with the latency settings, and in the UAD control panel there is a

addition separate place to just set it.

There are several apps on the net, things got somewhat randomly better

with the common suggestion audio card on top.. at the highest setting 254 or such..

(The question IS.... WHICH card to you boost, do you make them equal, do you have one slightly about the other and so forth.)

I tried an exhausting amount of combinations for MONTHS.

There was never an official word on the settings to use when two lynx's cards

are on the same buss fighting, and which settings to do what with.

Dawgear, as to your UAD problem...

When you do a ASIO reset, from time to time, do you end up it clearing and

having 1 automatic dropout? For instance at a buffer size of 128, I commonly

would get 1 dropout after the asio reset out of the gate..

Anyway, here is my "theory". When you switch plugs accross the UAD, it is

doing something very close to a ASIO reset, or possible the equivalent of

pushing the Automatic latency button on and off in the daw.

I don't know, try making your UAD's a 250 latency PCI buffer and the lynx

like 32 with everything else... Maybe that will agitate the issue.

In anycase; that situation holds off buffers from the Lynx driver for the time it

takes to irritate it. Rather, the driver should know some sort of a reset is in

process and either reset completely accordingly or honor the timeout.

So, anyway, the thing about either test is; it shouldn't happen, and probably

doesn't with other drivers. But it is the classic case of the lynx driver catching

a dropout where it shouldn't. Again, I think you can do this without a UAD is

all I'm saying... If you launch and app that puts 75% on your machine for 4

seconds lets say. It will probably dropout where most drivers wouldn't...

Also; They have recently had another bug I haven't seen solved that looks

alot like the samplitude issue, where the driver gets locked, tries to "catch up"

on the dropouts and they skyrocket until the machine is reset.. This

was a result from david trying to fix the summing dropout issue and it

backfired, especially in my machine..

But it wasn't until they removed PHASE from the command line tool that

broke the camels back in my case.. I was using the tool to invert the ada8000's

and had been for over a year and they removed support.. Absolutely no reason

to do that. I was happy to see after 2 years in the queue that the screen bug

was fixed. It finally took a user pointing out the memory link for them to believe

there was a issue there, and this is after dozens of people had complained..

I mean, with a client there, having your card's mixer app look like it had crashed

or was buggy as heck, it just didn't look professional.

They are trying; I just didn't pay for 2400$ in cards in 2004 for the ability to be

a alpha tester. It looks like they have increased the buffers again because of

record dropouts, you know, maybe someday they will indeed solve the problem..

I just figured I could sell them now and get what little they were worth out of

them and buy them back cheaper someday if I thought it was fixed...

But an RME card on ebay is already as cheap and I know it works.. I've had

both of them in the machine side by side... In fact, this is how I started using

them.. It's just the elusive issue didn't show up until months later when

I caught it, and by that time I had two lynx interfaces all built out with ls-adat's

and so forth...

I'm not the only one, there are dozens of reports. So if lynx says I'm just

bitter they are full of it. As we can see yet another person is trying to get

the issues solved.

7th May 2008, 06:06 PM	#22
drmad69 Gear maniac Join Date: Oct 2003 Posts: 254	The two LYNX's fighting is common in my experience. I even had one that was a src; and it didn't matter.. This is the reason for the secfet control screen and the PCI throughput numbers. One card will was always 50% worse then whatever ended up being the primary card on the buss... FWIW, I did mess with the latency settings, and in the UAD control panel there is a addition separate place to just set it. There are several apps on the net, things got somewhat randomly better with the common suggestion audio card on top.. at the highest setting 254 or such.. (The question IS.... WHICH card to you boost, do you make them equal, do you have one slightly about the other and so forth.) I tried an exhausting amount of combinations for MONTHS. There was never an official word on the settings to use when two lynx's cards are on the same buss fighting, and which settings to do what with. Dawgear, as to your UAD problem... When you do a ASIO reset, from time to time, do you end up it clearing and having 1 automatic dropout? For instance at a buffer size of 128, I commonly would get 1 dropout after the asio reset out of the gate.. Anyway, here is my "theory". When you switch plugs accross the UAD, it is doing something very close to a ASIO reset, or possible the equivalent of pushing the Automatic latency button on and off in the daw. I don't know, try making your UAD's a 250 latency PCI buffer and the lynx like 32 with everything else... Maybe that will agitate the issue. In anycase; that situation holds off buffers from the Lynx driver for the time it takes to irritate it. Rather, the driver should know some sort of a reset is in process and either reset completely accordingly or honor the timeout. So, anyway, the thing about either test is; it shouldn't happen, and probably doesn't with other drivers. But it is the classic case of the lynx driver catching a dropout where it shouldn't. Again, I think you can do this without a UAD is all I'm saying... If you launch and app that puts 75% on your machine for 4 seconds lets say. It will probably dropout where most drivers wouldn't... Also; They have recently had another bug I haven't seen solved that looks alot like the samplitude issue, where the driver gets locked, tries to "catch up" on the dropouts and they skyrocket until the machine is reset.. This was a result from david trying to fix the summing dropout issue and it backfired, especially in my machine.. But it wasn't until they removed PHASE from the command line tool that broke the camels back in my case.. I was using the tool to invert the ada8000's and had been for over a year and they removed support.. Absolutely no reason to do that. I was happy to see after 2 years in the queue that the screen bug was fixed. It finally took a user pointing out the memory link for them to believe there was a issue there, and this is after dozens of people had complained.. I mean, with a client there, having your card's mixer app look like it had crashed or was buggy as heck, it just didn't look professional. They are trying; I just didn't pay for 2400$ in cards in 2004 for the ability to be a alpha tester. It looks like they have increased the buffers again because of record dropouts, you know, maybe someday they will indeed solve the problem.. I just figured I could sell them now and get what little they were worth out of them and buy them back cheaper someday if I thought it was fixed... But an RME card on ebay is already as cheap and I know it works.. I've had both of them in the machine side by side... In fact, this is how I started using them.. It's just the elusive issue didn't show up until months later when I caught it, and by that time I had two lynx interfaces all built out with ls-adat's and so forth... I'm not the only one, there are dozens of reports. So if lynx says I'm just bitter they are full of it. As we can see yet another person is trying to get the issues solved.