Windows 10: Creators Upgrade Gaming Mode not for Audio DAW Applications

The Gaming mode would appear to be something those of us with recording studio's would benefit from. However an in depth look at it by Cakewalk Sonar analysts suggest its not for audio recording.

Here is their "Your DAW is not a game" Conclusion:

:)

 

next windows 10 update AUDIO VIDEO UPDATE

i want to see an audio video update. for example an update to windows movie maker. why not build skype into it. also why not create a microsoft daw software a digital audio workstation. name it windows daw. ied love to see windows media player
get overhalled as well. also add an HTML EDITOR.

 

Problem With the Way Windows 10 Handles Audio Hardware?

Method 1 results: Troubleshooting wizard returned, "High Definition Audio Device has a driver problem." Attempted to fix the issue with the suggested fix (search for and install an updated driver). The recommended fix failed to resolve
the issue.

Method 2 results: Uninstalled and reinstalled the PatchMix DSP application and the DAW software in compatibility mode. The issue persists, unchanged, with the same symptoms and the same level of repeatability.

Additional Information: The pattern I am finding is that once I reinstall the E-MU PatchMix DSP application, system audio is restored (as is webcam functionality). When I open my DAW, system audio stops and remains unavailable until I
reinstall the E-MU PatchMix DSP application. Orion, my DAW, uses the E-MU ASIO driver. It is the ONLY driver available for me to use, as Windows' audio system seems to choke immediately upon opening the DAW. By using the E-MU ASIO driver, Orion bypasses
the Windows DSP audio drivers. I'm not technically savvy enough to understand how (or if) E-MU's ASIO drivers interact with Windows' DSP drivers, but it seems as if the two drivers do not play well, together. I'm not sure if the ASIO drivers are hi-jacking
the DSP drivers' resources, or what is going on (or what is even possible to cause such a failure). But, that is what it appears is happening - the E-MU ASIO drivers and Windows' DSP drivers don't get along. And it isn't just the E-MU ASIO driver that is
doing this. Reports are that other recording interfaces from other manufacturers are experiencing similar issues when they fire up the ASIO drivers that came with their interfaces. Since the issue spans drivers from many different manufacturers, that tells
me that something in Windows' DSP drivers prevents ASIO drivers to play nicely with them. That begs the question, how can we get the two to get along without Windows DSP drivers from seizing up?

Thanks, again, for your reply. If you can think of anything further, I'd be happy to give them a try!

 

Now if Micro$oft would add an "Audio Workstation Mode" option, that would be awesome! *Cool