Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Paul W]

Getting "static" often with 24/192 and 24/176 multichannel through an AES16e card.  Dropping down to 96k clears it up as does switching to 2 channel.

DPC Latency Checker shows about 100us average with 150us peaks with Aurora running, and reports the system should be GTG (but doubt GTG includes multichannel 24/192). 

An Antelope Orion (over USB) shows average latency of about 1000us with 2000us peaks (USB and Orion drivers are the hogs).  Somewhat amazingly, Orion does play 24/192 multichannel over USB.

On the other hand, Latency Monitor says both units should have issues.  Latency Monitor suggests a power management problem, but I've turned off all the power management I can find in both Control Panel and BIOS.  Other than Orion specific drivers, for both Aurora and Orion, the drivers with the highest execution times are NTOSKRNL.exe, NDIS.sys, ATAPORT.sys, and HECIx64.sys.

The fact that a USB device works and a PCIexpress won't kinda makes me think the PCI bus priority is too low...but I'm not sure about that...and don't know how to change it.

PC:
Win 7/64
Core i3 540 3.1GHz
16GB RAM

What latency figures are you guys seeing with Aurora running?

Any suggestions on what I might try?

[SpeedD408]

What firmware on the card and aurora are you running?  I'm on 12.10 on the card and 28 on the aurora 16 with no issues.  I did have some major latency issues with 12.9 when using loopback.

[Paul W]

Checked FW and both were slightly out of date.  Updated the AES16e and Aurora FW to 12.10 & 28...unfortuntely no improvement.

Other ideas?

[mojave]

The Steinberg guide "Optimizing Windows for DAWS" might have some more helpful ideas.

I'm not having any trouble with my AES16e. Did you make sure the AES16e's clock is set to internal and on the Aurora 8 you set the clock sync source to "AES A"?

[Paul W]

Yes, AES16e clock is internal (and tracks JR), Aurora (16 BTW) is set to AES A and Syncro-Lock does lock at 192.  I've tried most things in the Steinberg guide (thanks!) but will try the rest.

Would you guys mind checking latency with Latency Mon and Latency Checker to see what readings you get?

[SpeedD408]

Here you go.. Attached are 2 charts.  One with Latency Checker and one with LatenyMon.

I was playing "The Rubberband Man" by the Spinners at native 24/192 when taking these screen shots.

enjoy.

[Paul W]

Thanks a lot!  How many JR channels were you running to the Lynx?

[SpeedD408]

The song is native 24/192 2-channel.  I have JRiver JRSS configured to mix to 5.1 and send that to the AES16e.

[SpeedD408]

Did you get your system working??

[Paul W]

It's down to about one "pop" per hour which may be as good as it gets with 15 channels of 24/192 running on a 1st gen i3 processor.  The big improvement was enabling 64 bit HPET (High Precision Event Timer) in BIOS as well as Win 7 and then revisiting latency settings in JR.  (HPET supposedly helps some systems but not others, so it is not a magic bullet cure-all.)  I'm contemplating the Intel roadmap to decide when to go for a new MB and processor.

Thanks for your help!

[Paul W]

This is an update intended to save time for anyone going the Lynx 24/192 multichannel route...

The best performance with the old i3 processor was using the x1 PCI-E slot on the motherboard...the "one pop per hour" reported in the previous post used the slowest MB slot available.

For other reasons, I've since upgraded the MB and processor to an i7-4770k.  With random static quite often, the new i7 system didn't work as well as the old i3!!!  So, I went through the drill of disabling power saving, enabled HPET, tried every setting imaginable, but still no love.  With JR running, latency ran mid teens to peaks just over 50us which, I think, is pretty stout for a PC without overclocking.

Anyhow, the solution was the same as for the i3...move the AES-16e from the "fast" x16 PCI-E slot I had so carefully selected to a vanilla x1 slot!  For Intel systems 3 generations apart, the trick for both was to use the slowest PCI-E slot! 

Since moving to the single lane slot (knock on wood) not one glitch of any kind...it works flawlessly!