Larry Jones
Max Output Level: -74 dBFS
- Total Posts : 834
- Joined: 2007/10/11 02:45:33
- Location: Southern California
- Status: offline
SONAR Slow Start
SONAR is taking a long time to launch on my system these days. This morning it was 3:20 from clicking a .cwt file until ready to play. Only two changes to the computer that I'm aware of: the 1709 Windows update, and the installation of three different DAWs (Samplitude, Studio One and Mixcraft demo). Anyone else have this happen, or know of a possible cause?
SONAR Platinum 2017.10 • CbB • Win10 • i7/2600 • 16GB RAM • Focusrite Scarlett 6i6 • NVIDIA GeForce 8400GS
|
scook
Forum Host
- Total Posts : 24146
- Joined: 2005/07/27 13:43:57
- Location: TX
- Status: offline
Re: SONAR Slow Start
2018/01/03 20:17:01
(permalink)
☄ Helpfulby Zargg 2018/01/03 20:57:20
No where near that extreme but I do believe the MAGIX Low Latency Driver (aka ASIO4ALL) slowed SONAR startup. I removed the driver from the registry. See this post and the one following it.
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: SONAR Slow Start
2018/01/05 20:39:48
(permalink)
It's always been slow here (although I never actually timed it), and it can take absolute -ages- to unload too.
|
Brando
Max Output Level: -47.5 dBFS
- Total Posts : 2776
- Joined: 2003/11/06 11:47:20
- Location: Canada
- Status: offline
Re: SONAR Slow Start
2018/01/05 23:49:22
(permalink)
I switched to S1 here. I always thought Sonar took long too. S1 takes way longer even for fairly modest projects. Anything with Kontakt takes way longer in S1 than in Platinum. As close to identical projects as I could muster. I'm not bashing S1 as it turns out I like it a lot. But over the years I've heard a lot of comments about Sonar that in my brief time window shopping alternatives leads me to conclude that we Sonar users had/(have) it pretty good. I'm still in the process of moving on but it's not as enjoyable as just using Sonar has been. My 2 cents
Brando Cakewalk, Studio One Pro, Reaper Presonus Audiobox 1818VSL ASUS Prime Z370-A LGA1151, 32GB DDR4, Intel 8700K i7, 500 GB SSD, 3 x 1TB HDD, Windows 10 Pro 64
|
.
Max Output Level: -76 dBFS
- Total Posts : 729
- Joined: 2015/05/25 01:53:03
- Location: Good TImes :)
- Status: offline
Re: SONAR Slow Start
2018/01/06 00:32:25
(permalink)
In my experience since jumping ship 2 1/2 years or so ago on the release of Studio One 3, my experience has been the opposite. Regarding startup, load speed, and speed in general, Studio One 3 makes SONAR look like it's crippled.
Intel i7 4790 @3.6Ghz - 32GB Ram - Windows 10 Pro 64bit - RME Fireface UFX+ Studio One 4 Professional, REAPER, CbB-(Couldnb't be Bothered) More Plugs than Plumbers Warehouse.
Happy Studio One User Since August 2015 "It's the entertainment value, the comic relief . . . plus the Software and Deals Forum"
|
Frank Harvey
Max Output Level: -86 dBFS
- Total Posts : 214
- Joined: 2014/12/30 03:55:56
- Location: Geelong Australia
- Status: offline
Re: SONAR Slow Start
2018/01/06 00:35:08
(permalink)
I see there is definitely a trend and conclusion developing here .... NOT
|
Cactus Music
Max Output Level: 0 dBFS
- Total Posts : 8424
- Joined: 2004/02/09 21:34:04
- Status: offline
Re: SONAR Slow Start
2018/01/06 00:38:06
(permalink)
Sonar opens for me in 10 seconds. Every time. I disable the Plug in scan. Why scan plug ins if you haven't installed any?
post edited by Cactus Music - 2018/01/06 04:16:51
|
msmcleod
Max Output Level: -72 dBFS
- Total Posts : 920
- Joined: 2004/01/27 07:15:30
- Location: Scotland
- Status: offline
Re: SONAR Slow Start
2018/01/06 00:48:02
(permalink)
Just some thoughts here: Does this only happen with that template, or does it take ages with a blank template too? Have you blocked internet access, and is there any plugin (or even more than one plugin) in your template that is trying to check for authorisation/updates? It might be that the cumulative time-outs of each plugin giving up is causing the slow startup?
|
msmcleod
Max Output Level: -72 dBFS
- Total Posts : 920
- Joined: 2004/01/27 07:15:30
- Location: Scotland
- Status: offline
Re: SONAR Slow Start
2018/01/06 00:51:32
(permalink)
One more thing - if this has happened since you installed Samplitude, Studio One and Mixcraft, you might want to go to SONAR's plugin manager and exclude any new plugins these DAWs have introduced. Maybe one of them is causing the issue. I've got to say though, I've recently installed the same three DAWS (Samplitude X3 Pro, Studio One 3 Pro & MixCraft 8 Pro) and I'm not seeing any slow down in SONAR's startup time. In fact, SONAR is the quickest out of all of them to start up.
|
Larry Jones
Max Output Level: -74 dBFS
- Total Posts : 834
- Joined: 2007/10/11 02:45:33
- Location: Southern California
- Status: offline
Re: SONAR Slow Start
2018/01/06 05:03:04
(permalink)
UPDATE: I disabled a bunch of nVidia HD audio drivers -- don't remember how many, at least eight -- and SONAR is starting much faster now. I now believe the Windows 1709 update caused a large part of this. Maybe I'll get around to removing the Magix Low Latency driver but so far I have not found an uninstaller for it. SONAR may not be a fast starter, but I'm a patient guy, as long as it's responsive once it's open and I'm using it. And it is. But I am currently devoting all my DAW time to learning Samplitude, which I have found to be kind of a bear. I want to be as facile with it as I was getting to be in SONAR, and it's just going to take time. I have a few old projects in SONAR that probably will need remixing some day, so I'm keeping it. I love it, but it's an Edsel. Thanks scook for your advice.
SONAR Platinum 2017.10 • CbB • Win10 • i7/2600 • 16GB RAM • Focusrite Scarlett 6i6 • NVIDIA GeForce 8400GS
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: SONAR Slow Start
2018/01/06 10:23:38
(permalink)
Cactus Music I disable the Plug in scan. Why scan plug ins if you haven't installed any?
Because it won't do anything if you haven't added/removed plugins. It only takes a second or two if nothing has changed. If sometthing *has* changed - you actually *want* it to sscan...
|
marled
Max Output Level: -85 dBFS
- Total Posts : 251
- Joined: 2015/01/22 04:50:52
- Status: offline
Re: SONAR Slow Start
2018/01/06 15:08:20
(permalink)
Sonar is the fastest starting DAW since I disabled the automatic plugin scan and the START SCREEN! And I have also installed Samplitude with the MAGIX Low Latency Driver (but I do not use this driver). It does not affact Sonar at all!
|
CakeAlexSHere
Max Output Level: -79 dBFS
- Total Posts : 577
- Joined: 2016/05/19 12:03:48
- Status: offline
Re: SONAR Slow Start
2018/01/06 15:13:11
(permalink)
Try temporarily disabling for virus scanner. If you are using standard hard drives (not SSD) make sure it's defragged. Check to see if other heavy processes are running before starting Sonar using task manager or process explorer. Process monitor is also a useful tool to see how bogged down your I/O is.
|
mettelus
Max Output Level: -22 dBFS
- Total Posts : 5321
- Joined: 2005/08/05 03:19:25
- Location: Maryland, USA
- Status: offline
Re: SONAR Slow Start
2018/01/06 23:35:35
(permalink)
Larry Jones UPDATE: I disabled a bunch of nVidia HD audio drivers -- don't remember how many, at least eight -- and SONAR is starting much faster now. I now believe the Windows 1709 update caused a large part of this. Maybe I'll get around to removing the Magix Low Latency driver but so far I have not found an uninstaller for it.
I actually uninstalled (not disabled) all Nvidia software via the add/remove programs except for NVIDIA's Graphics Driver, and NVIDIA's PhysX System Software. Also, if you go into the Device Manager, then click View->Show Hidden Devices, you can uninstall all of the dead linkages (they show up with an icon over them, and will reinstall themselves if ever plugged back in). When that gets messy, software is trying to connect to all of them if Windows lists them even if dead. The MAGIX ASIO driver seems to be a one-off deal... it causes grief on initial load, but once configured in each program seems to behave. I was initially going to trash that, but I have a few standalone VSTis that need an ASIO driver, so it does serve a purpose. The only other thing that comes to mind is there was a similar thread long ago and Noel spoke on how SONAR loads. The only time it was excessive for me was because SONAR links to available ReWire devices, and I had a flaky one. If you have installed any programs with ReWire enabled, that could also be a cause. Win10 updates I cannot speak to, but I have seen folks mention issues with various updates on their machines. Often this seems that disabled settings get re-enabled each time an update occurs, so disabling things that cause issues must be done with each major update.
ASUS ROG Maximus X Hero (Wi-Fi AC), i7-8700k, 16GB RAM, GTX-1070Ti, Win 10 Pro, Saffire PRO 24 DSP, A-300 PRO, plus numerous gadgets and gizmos that make or manipulate sound in some way.
|