Running Sonar X2a (32-bit) on my laptop and recently have noticed that the first start of the application following a reboot is deathly slow - taking around a minute usually. However, if I close Sonar and restart it, it is back up and running in 5 seconds. This is the case until the machine is rebooted, as which point the first load takes ages again.
 
I don't have any settings in place to scan VSTs when starting Sonar, but the issue seems to be when Sonar is loading the sound card driver, and the issue occurs irrespective of what interface or driver model is being used.
 
This doesn't stop me from using Sonar, as once started everything is fine and projects load fairly swiftly - I just wondered if anyone could explain the application startup speed after a machine reboot.

Some background process kicking in, maybe a virus scanner.

Disabled both WiFi and Anti-Virus. Still the same problem. I think it's the onboard sound driver screwing things up, so am going to re-install the driver.
 

Nope. That didn't fix it either. This is with the onboard sound (I'm currently at work), so I'll give it a go with my proper interface (Quad Capture) when I get home.

What do you expect from a 32-bit OS and a laptop?
Modern programs are getting larger by the day and needs lots of memory. 
The second time you load, things are probably in swap memory, not disk.

Yeah - that's a pretty weird one.  I would think it would be some local oddity, as there are no general reports out there with similar complaints.
 
Have you tried deleting aud.ini?
 
C:\Users\your user\AppData\Roaming\Cakewalk\SONAR X2 Producer
 
Sonar will recreate it on restart.  (It is a hidden file, by the way)
 
Maybe something within it got goofed up.
 
Bob Bone
 

This happens to me also. It has nothing to with whether you're running 32-bit or 64-bit Windows, and everything to do with how your operating system is caching disk reads in memory.
 
 

arachnaut
What do you expect from a 32-bit OS and a laptop?
Modern programs are getting larger by the day and needs lots of memory. 
The second time you load, things are probably in swap memory, not disk.

 
My O/S is 64 bit. I'm using the 32 bit version of Sonar because Proteus VX is 32-bit and doesn't work with Bitbridge.
As for my current setup - I recorded an EBM/Industrial album using it last year using Sonar, so to say that what I have isn't good enough is a bit disingenious IMO.
 
My issue is not with the operability of Sonar (I have no problems there) - I was just hoping that other users may have seen this slow start issue and could offer advice other than "your rig isn't good enough", but hey ho. I'll come back when I upgrade my vastly inferior computer.

When you use Sonar in 32-bit mode you are using a virtualized 32-bit OS.
 

This reminds me of the minimum requirements for running Windows 8.1
 
From:
 
http://windows.microsoft.com/en-us/windows-8/system-requirements
 
Windows 8.1
If you want to run Windows 8.1 on your PC, here's what it takes:
Processor: 1 gigahertz (GHz) or faster with support for PAE, NX, and SSE2 (more info)
RAM: 1 gigabyte (GB) (32-bit) or 2 GB (64-bit)
Hard disk space: 16 GB (32-bit) or 20 GB (64-bit)
Graphics card: Microsoft DirectX 9 graphics device with WDDM driver
 
Sure you can do it, but...