• SONAR
  • After rebooting, Sonar starts VERY slowly. Several minutes! (p.2)
2015/03/12 00:51:07
robert_e_bone
How much memory do you have?
 
Bob Bone
 
2015/03/12 06:27:42
TremoJem
I have the same problem.
 
It will also happen when Windows has been idle for awhile...say overnight.
 
I will energize my first MOTU 8Pre...wait for it to finish and then energize my second MOTU 8Pre and then execute X3e.
 
It can take as long as five minutes or I give up and reboot the entire system.
 
Once I get everything running I can shut down X3e and start it again without delay.
 
What gives? I will look in the device manager, although I don't recall ever looking for "hidden devices" before.
 
I am sure I should be able to find this though, thanks.
2015/03/12 12:25:14
Cactus Music
I guess this is were Windows 8.1 and SSD drives shine. 
I'm into Sonar as fast as I can type my password and then at the very most watch the little circle for 4-10 sec.  Sonar opens in 4 sec. 
 
You might want to check your start up processes by opening msconfig. Check "hide all Microsoft" and nuke what is still showing minus your antivirus. 
You can always turn them back on. This is my standard optimizing for my DAW for 10 years now.
You may find stupid useless things like Adobe Reader auto updater.  Nuke em! 
 
Run Latency Mon     http://www.resplendence.com/latencymon
 
And why are you using asio4all? 
Is it because your on board audio didn't work in WDM mode? You might be better off using the original on board cards native drivers. Double check they are up to date. 
asio4all is really just WDM mode and it tricks Sonar into thinking it's ASIO mode. It's good when it works, but it is a well know factor for causing havoc with your proper ASIO drivers. Removing it sometimes requires a trip to regedit.  I think removing it might be worth a try.
Sonar might be confused  about the audio driver when it's loading.  This is a typical asio4all/ ASIO conflict.  
Often on board sound cards work in WDM mode with the native drivers. Still not a great situation with Sonar because of pour performance and latency, but no way would I ever put asio4all on my DAW. 
It is only a desperate move for audio devices that don't have drivers and the audio device is all you have. 
 
Of course the best solution is a proper audio interface with 6 outs. 
 
2015/03/12 15:14:18
Splat
Try Craigs suggestion, then try this in order until you get a solution I suggest.

1) Completely remove ASIO4ALL
2) Update your audio interfaces firmware and drivers.
3) Run windows update several times.
4) Goto Intel driver update website. Install updates.
5) Update your motherboards BIOS
6) Rename AUD.INI in Sonar (google for details).

At any stage you could also defrag your hard drive and run chkdsk. If you have SSD windows should do what is appropriate automatically.

Always backup!

Thanks.
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account