UPDATE: The Problem also persists when I switch to my RME driver and RME USB Interface.
Restarting the computer ‘sometimes’ temporarily fixes the issues….meaning…as long I don’t open any Menus.
I, originally, thought the problem lied with opening just the AudioSetup window; but, the problem starts as soon as I choose ANY submenu and then X-out from the OPTIONS menu.
Background: I have (2) matching Windows 10 computers: One is my primary and the other is a backup: mirror image of primary computer. Before upgrading the Primary computer, both computer were running GP 5.0.2 with no issues. But, since GP 5.1.6 was available, I updated the primary computer to GP 5.1.6 and that’s when I noticed the problems. Luckily, my backup computer is running flawlessly.
You’ll have a good reason for using asio4all, but personally I would steer clear from it. In essence it’s just a wrapper around Windows multi media. I’ve used it on and off over the years, but I found it to be rather problematic and prone to failure.
If you’re audio device brings it’s own ASIO driver, I would suggest using that.
The only other reason I can think of for using asio4all, is to make an aggregate device (of separate audio devices).
Of course this is my personal experience and n==1.
To Clarify: If I have big GP project with 30-40 rackspaces, and I want to change anything in AudioSetup for that project, I just first open a new GP project (with no rackspaces) and make changes in the Audio Setup, save that blank project as, say, “BLANK”. Then, close it. And reopen the big project? I assume this AudioSetup change will be saved for other GP projects.