Quote:

The old legacy asio code is causing the processor to really ramp and doing anything sends it over the edge.



John, what old legacy asio code? Kent said in another thread that PG had problems with asio until 2009 but not any more. You are one of our resident experts, I'm wondering why you still feel there is this big problem with asio. This goes to what Mac said, there's a lot of moving parts to this starting with the latest versions of Biab/RB and a modern PC running Win 7. If you're running older stuff, all bets are off. I was one of the biggest beaters of that drum when I was using my old P4 2.8. Never could get the asio to really work. After tons of tweaking I could get the latency down to about 40ms, no lower. Now with the latest and greatest I'm running 10ms with no problems at all. The first thing I did with the new box was go to EMU's website and download their latest drivers. Works perfect.

This is yet another example of nobody but us geeks knows anything about this. If a user is not willing to hit the books and become a total computer nerd and understand and apply what Mac just said should give it up now and take up golf or something.

In my probably useless opinion, there is no longer a problem with asio but it requires knowledge such as ASIO4ALL is not asio. It's only to be used if someone's device doesn't have it's own native asio driver. If your soundcard comes with it's own asio driver then update it, learn how to set it up in your DAW and use it.

Bob

Biab/RB latest build, Win 11 Pro, Ryzen 5 5600 G, 512 Gig SSD, 16 Gigs Ram, Steinberg UR22 MkII, Roland Sonic Cell, Kurzweil PC3, Hammond SK1, Korg PA3XPro, Garritan JABB, Hypercanvas, Sampletank 3, more.