jih64
It would be good to hear from those who's performance went backwards with Lexington (I being one of them) whether or not things have improved with Manchester. Perhaps a separate thread.

I second this. If any of you experienced a decrease in CPU performance with Lexington, please let us know if that seems to have been fixed with Manchester. 

My experience is no it hasn't, but that was just a quick test with a small project I created to check out Lexington after being away from Sonar for 6 months, the difference between Lexington and whatever I was on back in July/August was quite noticeable, even on a relatively small project, getting clicks and pops and farts with just 1 instance of EZDrummer, I of EZKeys and 2 or 3 audio tracks each with Bias FX Pro on them, I made a thread back then, but marked it solved as I found that scrapping the project and starting a new one seemingly fixed it, but it didn't take much for it to return, after adding just a few more tracks and plugs it was back, I could double or triple that in S13 or Reaper with no sign of any issues, I rolled back to Gloucester or Hopkinton and everything was back to normal. Doesn't appear to have changed with Manchester, others seem to have it worse. I was going to start a new thread, but thought it may get over ridden by the overzealous, you know how it is.

jih64
My experience is no

So you're saying that you're getting the same CPU spikes using Manchester as you were in Lexington? That's disappointing. I get off work in a couple of hours. I'll download the update and see if I have any better luck. 

I have edited the above post with more info. But basically yes.

jih64
I have edited the above post with more info. But basically yes.

Thanks for the details. If this update doesn't fix the issue, I'm going to have to contact Cake directly and open up a support ticket for it. I'm crossing my fingers though. Hopefully my PC build is one that will play nicely with Manchester. 

jih64
My experience is no it hasn't, but that was just a quick test with a small project I created to check out Lexington after being away from Sonar for 6 months, the difference between Lexington and whatever I was on back in July/August was quite noticeable, even on a relatively small project, getting clicks and pops and farts with just 1 instance of EZDrummer, I of EZKeys and 2 or 3 audio tracks each with Bias FX Pro on them, I made a thread back then, but marked it solved as I found that scrapping the project and starting a new one seemingly fixed it, but it didn't take much for it to return, after adding just a few more tracks and plugs it was back, I could double or triple that in S13 or Reaper with no sign of any issues, I rolled back to Gloucester or Hopkinton and everything was back to normal. Doesn't appear to have changed with Manchester, others seem to have it worse. I was going to start a new thread, but thought it may get over ridden by the overzealous, you know how it is.

I think this is a serious issue that we need to get fixed. If I can be of any help just let me know. 

John
 
I think this is a serious issue that we need to get fixed. If I can be of any help just let me know. 

I think I recall you also were having performance issues after Lexington, how have you found Manchester ?
 
It's not a big issue for me really, I'm content with Studio One 3, I do everything there now, sometimes export the stems to mix in Mixbus 3 when I think what it adds soundwise with it's particular 'sound' will be of benefit. I just check in every now and then, and keep my membership up to date, waiting to see if Sonar gets some features that I have gotten use to in S13 and aren't really prepared to be without.
 
I have always found Sonar to be a bit heavier than the other DAW's I have, but never to the point where it has been an issue or a problem, just something that I had observed and was aware of. I must say I lost a bit of faith during the Rapture Pro debacle, but am SO glad to have it working fine now.

kitekrazy1
I'm a bit worried. Did they give this update to those of use that had an expired membership this month and didn't renew? I hope it's not going to be in demo mode. Well if so then I can see how well it reverts back.

Yes, they extended your membership by 14 days which should puts its expiry to almost (or past) the end of January.  I was one of the very early adopters (read guinea pig for their new system) which meant my year was up on the 15th.  In the cake store, it shows my membership valid until the 29th now.

skitch_84

jih64
My experience is no

So you're saying that you're getting the same CPU spikes using Manchester as you were in Lexington? That's disappointing. I get off work in a couple of hours. I'll download the update and see if I have any better luck. 

Same here. cpu spikes with Lex and Man.

Mosvalve

skitch_84

jih64
My experience is no

So you're saying that you're getting the same CPU spikes using Manchester as you were in Lexington? That's disappointing. I get off work in a couple of hours. I'll download the update and see if I have any better luck. 

Same here. cpu spikes with Lex and Man.

I wish that someone from Cake would chime in and acknowledge that this is a serious issue for a lot of us. I'm completely understanding that it may not be an easy fix and I'm fine if they are taking their time to get the fix right, but it would be nice to hear from them that they're aware of the issue and are working to correct it. Updating to the latest version (that I'm paying for with the subscription), has felt like a downgrade for the past two months because of this. :(