I've noticed with Dorchester that Splat sometimes doesn't successfully start at all. I either launch from CCC or launch it directly and nothing happens. I have to go to task manager and kill the sonarplt process and try again to get it started.
 
No consistency in this occurring.
 
So sig file yet, but it's on a Win7Pro machine with 6 cores and 16 gb of ram.

@ artturner - maybe it's the Echo plug messing up 

Hi LJB,
 
I recommend that you get on the phone with our Tech Support department, if possible. We're not able reproduce the issue here, running basic benchmark comparisons. Perhaps our tech specialists can fix it up, or at least isolate it to a particular component or area that needs our attention.
 
FWIW: We're very committed to making each release of SONAR better than the previous. If we detect a regression, we'll make you wait while we iron it out ;).
 
Thanks.

In Dorchester I have had numerous crashes seemingly out of nowhere. With a heavy client schedule I reverted back to Cambridge and the crashes stopped. (Cambridge is way cooler in real life than Dorchester anyway ).
 
Not sure what may be causing the issue. It's happened when loading Melda MDynamic EQ and one or two others. Mostly it has happened during the start and stop of playback. Hit play and crash, stop playback and crash.
 
Interestingly, even though I reverted back to Cambridge via the CCC the bug with the control bar got fixed anyway, which is cool.

Hello Sir Les, what's funny is that I've thought that my system, or to say the Processor Intel Q6600 Quad Core, is kind of old by today's standards. I can't say enough about SSD, since I've installed mine, Samsung 830 Pro 512gb
my computer is like a high-performance machine! I do have the primary Sonar Platinum program on the main SSD and the plug-ins, loops etc. on the secondary HDD (1tb). I have an external drive (Glyph) 8tb which I keep the music projects, other than that I haven't modified the Register, Bio's etc. I don't over-clock, the only time I noticed a lag in load up time is when I had forgotten that I was running my "Window's Defender & Anti-Virus" which I minimized, wasn't looking at the tray. Opened Sonar and I four minute project, and it took about 35 seconds? (approx.), I have this thing where I need things to respond at an instant, so I'm very aware of my computers condition most of the time, I'm sorry that I can't be more help! I also use 8gb of DDR2 which is old standards by today???

On a side note......I was reaching over my keyboard (while having my guitar on my lap) to adjust something on my Focusrite  2i4, and heard a machine gun like drum sound stuttering continuously (which actually shocked & surprised me). To see, the head of my guitar was hitting the spacebar on the keyboard and it gave a repeating rewind/play function (instead of just playing the tracks) when depressed. Not an issue, just an observation. 

Mesh
On a side note......I was reaching over my keyboard (while having my guitar on my lap) to adjust something on my Focusrite  2i4, and heard a machine gun like drum sound stuttering continuously (which actually shocked & surprised me). To see, the head of my guitar was hitting the spacebar on the keyboard and it gave a repeating rewind/play function (instead of just playing the tracks) when depressed. Not an issue, just an observation. 

 yeah, damned Dorchester what it can do...

Whew!

Nice to have projects of that sort on a machine well setup...

Are they mostly audio recordings or do they contain many soft synths and the like...

I notice that projects using all audio load fast (especially if the waveforms are current in the folder) no matter how many 64bit vst's I use (eq/comp/etc), but as soon as I start adding softsynths (even frozen), the load times increase dramatically...

Keni

brundlefly

SteveStrummerUK
 Here's my load time for Dorchester in real time:
 

 
Mayebe it's of no consequence in this case, but it would be best not to demo a SONAR performance problem with a potentially resource-hogging app like Photoshop running.
 

Good point Dave, I tried it again without Photoshop running and it brought it down to just over 50 seconds.
 
Edit to add: If I reopen the same project immediately after closing it, it takes less than 15 seconds to open.
 
I haven't had Dorchester crash on me yet though.

Mesh
It's odd that these updates tend to work out well for some and not so well for others.

I'm in the camp of things working just fine. My theory is that more frequent releases expose system-specific issues or conflicts on a regular basis instead of having them all pile on once a year, where it just seems there are lots of bugs.
 
But I wouldn't be afraid of installing updates. I've used the rollback option several times, mostly to verify whether something is a new feature/fix or whether it existed previously, and the rollbacks have been predictable and painless. So far I've seen no reason not to trust the rollback process.