Dorchester much more unstable than Cambridge.

My observation, as an 8+ hour per day, 7 days a week professional user of Sonar Platinum is this is going backwards fast. Struggling to open projects, plugins crashing, PC channel not recalling presets. No gentlemen, this will not do. You can blame all kinds of things, but the DAW has to be MORE stable with every new release, and it's not.
 
Please fix it.
 
Sincerely, your loyal user.

It's easy to see the need to let off some steam...but did you provide useful info for Cakewalk to narrow down.
 
Like providing the smallest issue project as a bundle file to Cake, or something.
a) is project created in Platinum or other version
b) have mix recall been used
 
I've seen Sonar(starting without any project) just freeze kind of for 20-30s or so before continuing.
I see a correlation having been online last startup - and if it has to do with trying to look for updates or something. I don't know why they bother having this done that way, if that is the issue - waiting to timeout on something. But speculation on my part.

Crisp and snappy it ain't! X3 is, Plt is bloated from my end and I can make a coffee by the time it loads a project...seems even slower now after Dorchester. Plt continues to crash. I wanted to add an audio track to a project yesterday and it crashed twice. Same project okay in X3. Did manage to work on a project all day today though, so it has some redeeming qualities.
 
Agreed: Stability is paramount!

No clients looking over my shoulder, with lightweight projects, BUT
 
Bugz are bugz, but S-PlatD combined with my current hardware is VERY stable.  S-Plat has been crisper & snappier than any previous version I've used, including X3e.

Fabio Rubato
 
Agreed: Stability is paramount!

But that could mean project load is slower - are your throwing each plugin in it's own thread that would be quicker, but may inflict more on stability syncing all threads with one stream of audio.
 
I remember initial bugs in NI Kontakt(if it was v4) that optimized loading by spreading loading of samples over many threads. Later fixed in v4.1.
 
And let's make assumption that you want Mic Recall to be quicker - then there might be more plugins that needs initializing.
 
If looking at CCC, Cakewalk knew they only had limitied time until launch - quickly admitted that more options are needed and it will quickly change with feedback.
 
So it's not that far fetched that also loading of projects, checking out Mix Recalls takes longer right now - and will get some options later on - do we want all mixrecalls to be prepared to load quicker when selected, or do we want initial load of project to be quicker.
 
All remarks may be valid as stated here in this thread - not saying they are not.
Just pointing at some things that might be worth waiting for - stable operation....checking more things initializing every plugin. You have console size to be calculated, due to what is the max number of inserts on every track, new to Platinum....and many more things I can imagine.

After installing Dorchester (a few days ago), I worked on a new project yesterday with multiple midi/audio tracks and didn't notice any issues at all......I even (accidentally) opened up an older project and noticed it loaded up within seconds.
It's odd that these updates tend to work out well for some and not so well for others. I hope all of you get this resolved quickly.

lfm
 
I think I saw a transparent dialog there at the end.
Did you try turn off transparency in Windows theme?
 
Transparency means all windows covering each other needs to repaint from bottom up - every time a repaint is needed.
No idea, if this is significant on your system - but worth trying.
I just hate it and turn it off for that reason.
 
And I come to think of the 20s-30s delay I encounted some time in between, that I feel might be Sonar checking for updates.
 
Once Sonar is loaded - what is load time then of this project?
 
I can't say this any abnormal - if first startup of computer and a number of sample based libraries are loaded. SuperiorDrummer full bleed, 1.5G, of booted computer takes 10-15s to load on my system.

HI Lars, that transparency is just me turning off the onscreen video program, it's not anything I ever see normally.
 
To simply start SONAR from the .exe, as opposed to opening a project as I did in the video, takes about 10 seconds, so the project itself took around a minute (1 MIDI Track into Superior Drummer; 6 Audio Tracks).
 
 

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

No video ... not saying you're not having problems ... just providing a data point for comparison.  I just started S-PlatD by opening a project with acouple of audio tracks, an instance of Guitar Rig 5, EZ Drummer and two Rapture Pro instances.  The first RP is loading a DimPro legacy piano program, the other a Rapture Pro factory cellos program.
 
Total time to load was 25 secs with the same project having been previously loaded.
 
I emptied the Windows standby memory (cache) and timed it again ... same time within 2-3 secs.

I'm finding some of this too...

Outside of bugs such as not saving the control bar state, all the releases have been stable...

But Dorchester continually crashes simply by changing/loading/closing songs...

I have sent a few crash reports, but my web access is so limited I couldn't send too many...

I haven't had this kind of trouble in a very long time...

Keni

Hay MANTRASKY...Need to ask a question, how long are those 100 tracks?...to get 2 second load times?...it takes more than that just to scan my plug ins...never mind draw in the waves on each track which takes , too long in my book...I could cook a full meal, and make coffee, and have desert by the time some of my 26 tracked projects  load up.
 
If you tweaked something...(shhh) they do not like that word around here.....Let us know what is, or your system specs, so we can enjoy that bliss also ....wink.

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.

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.

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???

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...

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.