• SONAR
  • [SOLVED] new Windows 10 forced update (free version) ruined my Sonar Platinum (p.2)
2016/08/05 22:07:56
Cactus Music
My DAW doesn't have any on board audio, I never installed that when I built it. I also disabled the HD video audio.  I can play U tube videos while Sonar and Wav lab are open and never have had any issues with audio,, it all goes through the 6i6. So I'm a solid believer in only using your audio interface on a DAW. Might be possible this doesn't always work with certain interfaces.  
2016/08/06 08:13:27
wetdentist
i was able to figure out how to solve my problem.  last night, i uninstalled the Quad-Capture completely.  then Windows update automatically downloaded & installed the most up to date driver.  then, and this is what i had originally forgot about, Roland has this additional executable file that connects these generic MIDI files that get downloaded from the Roland website to the device.  then there was another setting in the preferences that needed to be changed: Playback Timing Master was switched to "none" so i had to switch that back to the Quad-Capture.
2016/08/06 17:08:21
tlw
The best way to force Windows (any version) to ignore the on-board soundchip is to disable on-board sound in the BIOS. That way Windows doesn't even get to find out it exists. And, as Anderton discovered a while ago, check in device manager that there are no active HDMI audio drivers.

As an aside, I had my first "install Windows 10" experience yesterday. Put it on a Mac using Bootcamp. Win10 has to be the most promiscuous, data-mining operating system I've ever seen. Even turning stuff off in the setup screens like the peer-to-peer eat-your-bandwidth update sharing function didn't prevent it being turned "on" when Windows proper booted. And the updates it grabbed then over-wrote various other settings. Come back Windows 8, all is forgiven.

Roll on Sonar for Macs.
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account