Is your platinum slow to start?

Here on a core 2 duo laptop development machine, X3 shows the splash banner for about 15 seconds before showing the sonar window. Same machine, Plat shows the splash for 50 seconds and only during the last 10 to 15 seconds is there any hard drive activity.
 
After it's up, it runs nice and quick though.
 
Win 7 x64 4 gb ram
 
:Ron

bitman
Here on a core 2 duo laptop development machine, X3 shows the splash banner for about 15 seconds before showing the sonar window. Same machine, Plat shows the splash for 50 seconds and only during the last 10 to 15 seconds is there any hard drive activity.
 
After it's up, it runs nice and quick though.
 
Win 7 x64 4 gb ram
 
:Ron

What Audio card are you using?

I have a Core 2 Duo 6 GB mem with a Tascam FW-1884. I don't really see much difference over X3E for start times.
It takes a while to load a fair sized project though.
Opens 4 GB project in about 60 secs (7 DIm Pros, AD1, 15 audio tracks).
Open task manager and watch the memory size during start. WHen it looks like it is doing nothing you will probably see the memory increasing to a few GB as it loads synths and samples etc, then boom... the Sonar windows open.
 
32-bit will be snappier than 64. Advantage of 64 is > 4GB memory. I could not open project above in 32. It might open but would drop out since the samples could not all be in memory and the disk would be thrashing trying to keep up.

Seth Kellogg [Cakewalk]

bitman
Here on a core 2 duo laptop development machine, X3 shows the splash banner for about 15 seconds before showing the sonar window. Same machine, Plat shows the splash for 50 seconds and only during the last 10 to 15 seconds is there any hard drive activity.
 
After it's up, it runs nice and quick though.
 
Win 7 x64 4 gb ram
 
:Ron

What Audio card are you using?

Realtek HD audio (onboard) with ASIO4All
 
Sorry for the delay in response, I had to go walk the dog.
:Ron

 I think 32-bit may start faster since it cannot load as much into memory as x64 and 32 loads expecting to load samples and stuff from disk later as needed.. With x64 Sonar knows to put as much stuff in memory as possible and this takes more time. Also the actual 32-bit code is somewhat smaller than 64 so this loads a little faster.
If you have I7 x86 then it is fast enough to get stuff from disk so your project still works. If you kept increasing project complexity, eventually 32-bit would choke being limited by on the fly disk access . 64-bit would have stuff in memory all the time and will handle truly massive projects.
Try the task manager memory size thing. Sonar should not be idle for any length of time on start. IT should pretty much be loading stuff into memory all the time until the Sonar windows appear. 

Huh, Ok.
 
Thanks for the replys.
If I disable my sound card it makes no diff
2ond and 3rd launches take just as long from splash to progam as the first.
 
This is a dev machine so I don't play back much with this pc.
Just wondering if it was just me and, yes Ron, just you. :-)

I have it on my main desktop and a laptop both start up quickly. 

They seem the same on my system. It is too fast to do any precise comparison (I have a pretty zippy computer) but certainly not the 5x you are seeing, which I'd notice.
 
Could be an issue with drivers (as alluded to with the soundcard thing). Could possibly be caching, Windows watches what you do and precaches stuff in RAM so maybe it has figured out you like X3 but not yet Platinum. I kinda doubt that is it though, normally wouldn't be that big a difference.
 
At any rate it does look like it is something specific to your system, not just Platinum in general.

Mine starts fairly fast. There was a couple times it took longer than usually to start up and I thought it had frozen. For most part it's snappy tho.

I have crappy comp (see sig.), but X3 and Platinum starts reasonably fast. I am not in the near now, but for sure it takes less then 30sec for moth. And that is only for the first time, next time they start faster.
 
32/64 and memory should not influence that part (as I understand, we are speaking about SONAR start-up, not project loading).
 
Some ideas:
* do you have some real-time scanner (antivirus)? It can help to let it check the whole disk once and/or exclude SONAR directories from checking. Or disable for test.
* do you have some devices which are scanned by sonar? Not only Soundcards (all), but also MIDI. You can try
to disable/disconnect them all.
* how full is your hard disk? Check there is no fragmentation. Also check performance of the whole disk to see there is no problems with some parts of it. That should have no influence in case you really haven absolutely no disk activity (HDD led is not lighting/blinking at all).

Gosh this is an old thread resurrected.
 
Kill it.