Originally Posted By: Dave R
I couldn't get the WAS driver to work properly on the desktop after loading Build 512 (tremendous latency problems....I reported this to PG).


To me this is the major clue. You write like you understand this stuff but someway, somehow you're missing something simple. WAS works absolutely perfect with the vast majority of users. It's a huge improvement in Windows sound. What did Support have to say about using WAS?

On your laptop, I would switch to WAS and if that doesn't work then I would say it's with the laptop itself. FWIW, another user spent weeks (seriously, weeks) messing around with stuff like this and wound up reinstalling Windows and voila everything's perfect. That tells me that somehow he messed up his system with something.

On a clean system, Biab runs perfectly, simple as that. Sure, it's possible now that a recent Win10 update may require a tweak but I haven't seen that yet and I'm on automatic updates.

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.