Sonar Platinum Lexington Issues (SOLVED - GREMLINS)

Hi all, Merry Xmas and Happy New Year and all that.
 
Background
I haven't used Platinum in a few months, after trying out Presonus's Studio One 3 back in September I think and just really clicking with it and loving many of it's features, I took advantage of the cross grade price and have been using it as my main DAW ever since. I have been downloading all the Platinum updates from my account, but not installing as I wasn't using it. I had all but decided I wasn't going to renew my Platinum Membership, but I heard about the latest update to Rapture Pro and Z3TA+2 and came to check that out. Had stopped using Rapture Pro because of it's issues. Glad to say Rapture Pro is now back on my list and am more than happy with the latest update (Well done). At that time I also noticed the Turkey Gobbler sale and took advantage of the cheap 12 months Platinum extension.
 
After reading the latest couple of Platinum Updates notes, K and L, I noticed a lot of talk about performance improvements, optimizations and fixes and stuff, so I thought I would update to the latest and have a look, not that I had had any issues previously with Platinum, it was S13's features and well it just clicked that drew me away. So to the issue -
 
Issue
On updating Platinum to Lexington, I had a bit of a look around and started a little project just to check things out and get reacquainted. It's just a small test thing, EZDrummer 2 (separate tracks) 5 guitar tracks each with an instance of Bias Fx Pro and Waves IR1, one bass track with Bias Fx Pro and one instance of EZKeys, and other than a few effects on the Master buss nothing else, so as you can see it's not a huge thing. On playback, or trying to record a Lead guitar track I get serious pops and crackles, it's just not usable, so I change the buffer settings for my audio interface to 1024, still a few pops and crackles, change to 2048, it's ok, but of course it's not optimal for playing/recording a guitar track at that setting. Never had an issue before.
 
So I fire up Reaper 5.1, used Reaper for years and I must say it's always been noticeably lighter on resources than Sonar Platinum or X3E, X2 whatever,  and basically create exactly the same thing, same tracks, although I re recorded the guitar and bass parts, exact same FX, exact same settings, a mirror image you might say. Reaper, my computer doesn't even break a sweat, no problems leaving the audio interface at 128. I then do the exactly the same with S13, and again no issues whatsoever. So in both Reaper and S13 I just double everything, basically duplicating every track, effects the whole shebang, and again no issues to be had with either, all is fine. So I then swap out EZDrummer 2 for BFD 3 in both S13 and Reaper, now BFD 3 is quite noticeably heavier than EZD2, again no issues.
 
None of the FX are look ahead type things or anything, sample rates and all that jazz are all the same across the board, I have the onboard sound disabled, wifi isn't an issue, audio driver within Nvidia display driver is disabled, I had done the change to the cakewalk Audio .ini (forget what it is, but I think I recall something to do with multiple processors, threads or whatever, you changes it from 1 to 2 or 0 to 1 or something)
I have noticed that within Platinum the load seems to be more evenly spread in the performance graph, but the first still receives the brunt. I have always noticed that Sonar all the way through has been noticeably heavier on recourses than Reaper, and now the same with S13, but has never been an issue. I thought that with the new improvements, optimizations things would be better, but it doesn't appear that way. I am going to roll back to whatever it was I was on before and try the test project there and see what happens.
 
Any ideas ? 

I am having very similar issues myself. I submitted a failure report through the normal reporting procedure. The current status of my report is "not yet reviewed". At first I thought my issue was a Windows problem. However, the problem does not happen with Reaper or with Cubase.
 
You should submit a report though. The more data they have the better.

Bassmanx
I am having very similar issues myself. I submitted a failure report through the normal reporting procedure. The current status of my report is "not yet reviewed". At first I thought my issue was a Windows problem. However, the problem does not happen with Reaper or with Cubase.
 
You should submit a report though. The more data they have the better.

Hi, I must have been typing while you replied. My issue has gone, everything working fine, see my post above yours, I'm putting my issue down to Gremlins.
 
You might want to try what I did and start from a fresh slate and see what happens. I have read this as a suggestion for various project issues over the years, never had to do it before myself, and have been a little dubious about it as a solution, but there you go, live and learn.
 
Best of luck with it. 

Yeah, that wouldn't be a feeling I would like to have hanging over me. Over the years I haven't really had an issue with Sonar, the one this thread is about would be the worst, and in the end that was nothing. Never had stability issues to speak of, the only thing is I have always found it to be a bit heavier than others I use, Reaper and now S13, but it's never really been a problem, but the less taxing things are the better.
 
Anyway, hope you get it sorted, and things get better for you.