Extremely High CPU Usage with Lynx LS-TB and PT 12.5

[john1192]

have you guys tried a different Lynx Driver / Mixer

i had some weird issues and called Paul at Lynx .. rolled my system back and weirdness went away .. there are still times where i will Test in ElCap on 12.5 then go back to 10.9.5 Partition and 12.4 and i will have No Audio until i cycle the power on Aurora 16 .. so it messes with it going back and forth .. i have stopped testing for now ..

my system: and yes, i use the AES card not TB .. but am curious as i have a laptop i would like to use with Aurora

Lynx Mixer ver 1.0 build 57 (build date dec 9 2014)
Aurora Firmware ver 28

cheers john

Originally Posted by DontLetMeDrown

Sounds like the problem lies with the Lynx driver. My setup is slightly different, but same problems with high CPU usage in 12.5 with 1 track in the session (constant -9173 errors, but 12.4 works perfect).

My setup:
Aurora16->AES16e
i7 965 with 12 gigs of RAM
Windows 10 64 bit Home

[Jazzbass56]

Originally Posted by don4777

I am having a problem getting Pro Tools 12.5 to work properly with the Aurora 16/LS-TB under Windows 10 Pro.



Configuration: Pro Tools PC Rack-mount PC (ASUS X99a, Intel i7-5930K, 32GB, 4x1TB SSD drives, ASUS Thunderbolt II Dual, Windows 10 Pro), LS-TB Firmware 5.5 and 6.0 both result in the same behavior. Pro Tool settings are at their default.



This is a new computer and the problem is that audio is distorted in Pro Tools due to cpu usage (as measured by the Pro Tools System Usage tool) is maxed out at 95-100%. This is with or without loading a session. Just sitting idle. The Windows Task Manager shows only 9-11% cpu utilization. If I switch from the Aurora to any other audio device Pro Tools works as expected and the PT System Monitor drops down to < 3% when idle with or without a session loaded. When playing the Pro Tools demo session through any audio device other than the Aurora the cpu usage is 9%.



Studio One and Sonar don't have any problem using the Aurora/LS-TB. I gather from various entries I have found in multiple forums that other people have this working. Does anyone have any idea how to resolve the issue?



Thanks.

I have the same problem, I can't use PT 12.5 have to use 12.4
I contacted Lynx and they didn't offer any solution
I guess it's up to Lynx to figure this out
They suggest that Avid's implementation of ASIO is not up to spec or has somehow changed with 12.5
I gave up and just use 12.4
I don't use or need Cloud collaboration
Cubase 8.5 works flawless

[don4777]

Apparently the EPROM on the LT-TB card had become corrupted. Was able to fix it by switching to EPROM 1 and reloading EPROM 2 with the 5.5 firmware.

I tried using Driver Ver 22 with PT 12.5 and it made no difference.

Anything else we can try?

Don

[don4777]

We heard from David Hoatson, Chief Software Engineer at Lynx, that he is reaching out to his contact at Avid who did the ASIO implementation for Windows to see if they can get to the bottom of this.

Thanks to those who have experienced the problem for providing information. Additional info from others who experiencing this may be helpful. The only common factor I can see is that we are all using a Lynx Aurora and PT 12.5. Things that don't see to be common: Windows version can be 7 or 10, interface can be AES or Thunderbolt, WDM driver can be Lynx Version 22 or 23.

The title of this thread should probably be changed to "Extremely High CPU Usage with Lynx Aurora and PT 12.5". I'm not sure how to change it. Any one know?

Don

[Djsnyper]

I have had the same sort of problems with my system. Since going to 12.5, the system usage window within pro tools shows spikes up to the 90% area immediately after loading. Even without a session open. The weirder thing is that my task manager says my CPU usage is 9% when this happens. I have switched to ASIO4ALL through the Aurora 16 and the spikes go away. Avid has no solution to the problem and point to Lynx for some solution.

PS: I have Intel i7 4790k, 32GB of RAM and 512GB SSD

[Jazzbass56]

Originally Posted by Djsnyper

I have had the same sort of problems with my system. Since going to 12.5, the system usage window within pro tools shows spikes up to the 90% area immediately after loading. Even without a session open. The weirder thing is that my task manager says my CPU usage is 9% when this happens. I have switched to ASIO4ALL through the Aurora 16 and the spikes go away. Avid has no solution to the problem and point to Lynx for some solution.



PS: I have Intel i7 4790k, 32GB of RAM and 512GB SSD

This is a rather frustrating situation , I like Lynx I feel they generally have very good tech support, but this problem appears to be one that they don't even acknowledge as being a problem, I've called them and they just respond they have 12.5 working on their system.
I even gave them the link to this thread.
I use a Lynx Aurora 16 TB with Win 10 pro, Asus X99 pro Board with thunderbolt and as stated earlier 12.5 on Windows is not a option for me because of this problem.
And like others on this thread other DAWs work fine
So perhaps it is a Avid problem with ASIO, but I Wounder why it doesn't effect other I/O s from other manufactures

[amarqu1]

Hey folks, has anyone come across a solution to this issue? I've been using 12.4 over the past few months. I tried moving up to 12.6, and this problem still persist with my Lynx setup. When I switch to a Digi 003R, everything works as expected with about 15% total CPU usage on my current project.

I noticed another thing that's interesting- all the CPU consumption is almost entirely on the 1st core (CPU 0).

[sandberg]

Hi,

Just reporting that I´m having the same issues on my Mac Pro 6.1 (trashcan) running El Capitan with PTHD 12.6 and Lynx LT-TB. My workaround has been to change to a higher buffer size whenever the problem occurs, just to get rid of the noise, and the change back to a lower bs, typically 128 or 64. For some reason it seems that 256 causes the issue more often than both lower or higher bs settings.
This is not an ideal solution, but it beats re-booting the entire system (or worse) when you´re in the middle of a session. Hopefully it can work for some of you while we´re waiting for Avid and/or Lynx to sort this little bugger out.

[Jazzbass56]

This is a problem with Lynx I have a Aurora 16 TB and it won't work with 12.5 or 12.6
I talked to tech support last week at Lynx and they say it's a Avid problem with ASIO and they just pass the blame to them
My focusrite solo USB works fine
Now this only happens on Windows 10
The Lynx works fine with MacOSX
So it is very frustrating and Lynx does not seem to think it their problem



Sent from my iPhone using Tapatalk

[amarqu1]

I've been dealing with this issue a lot over the past few weeks. As of now, I'm over 50% into an upgrade subscription that I haven't been able to use since version 12.4 (May), so a solution would be nice before my subscription is up in December. I did request Avid to extend my subscription based on the problem, but they denied it.

The problem affects both Lynx Thunderbolt and AES 16e drivers, which I believe are almost the same driver. On my Windows 10 machine, I see 80% - 90% use of the 1st CPU thread, and no use of the other 11 threads. This occurs prior to loading a project in Pro Tools, and at all buffer settings. Like others with this issue, it appeared starting with 12.5 and doesn't appear on other DAWs.

I've contacted Lynx who is willing to work with Avid, but last I've heard is that they haven't received any response on the developers' forum where they posted the issue. I put in a ticket with Avid and the service guy verified my install and changed a bunch of computer settings to no avail. Finally, just yesterday I installed a new system drive and Installed Windows 10 cleanly. With no other software installed except drivers, I installed latest Lynx drivers and PT 12.6. The issue remained identical.

So I'm in for one new hard drive, many hours and over half a subscription and there's no fix in sight. I did get a note that Avid was looking into it, but nothing too reassuring. And now I'm faced with a subscription decision in December. This may finally spell the end of my use of Pro Tools.