Glitches and dropouts in Lexington

 
Cakewalk is certainly aware that some are experiencing poorer performance with Lexington.  I don't believe anything official has been said about what might be the cause or what might be done about it.
 

I updated from Foxboro to Lexington and was getting problems as well. Haven't done a bounce but my exports seem okay however... yes, some people seem to be having issues.
 
Good to know Kingston is working though. I may give that a go if Manchester doesn't right things.
 
Cheers.

Afrodrum
Happens to me too. They sound strange, like the completely new kind of glitch I never heard before in Sonar, loud, scratchy and nasty. Though it does not happen everyday, perhaps every other day.

Yes, that's exactly what I was getting.

PJH

Afrodrum
Happens to me too. They sound strange, like the completely new kind of glitch I never heard before in Sonar, loud, scratchy and nasty. Though it does not happen everyday, perhaps every other day.

Yes, that's exactly what I was getting.

Yes, me too at first. I found increasing my interface's buffers up a bit got rid of the crackling though. However as my project pressed on I also had to increase my read/write i/o buffers (hard disk) as well to avoid dropouts (not crackling... just engine dropouts).
 
Please read my following reply to JonD as it may be of use to you (I've been poking at alternate plans to fix my own issues).
 

JonD
Well, the Manchester update should be dropping any day.  We'll know soon enough if they've found and corrected those issues.  The great thing is, we can always roll back or stay put at a solid release. 
 
I've been on Jamaica for awhile and it's been solid for me.  No more experiencing weird behavior or the odd change here and there after updating every month (I'm on the prepaid annual plan). 
 
It's been quite liberating, and has taught me an invaluable lesson on the virtue of being patient.  I now plan to only update maybe twice a year, depending on where I'm at in my projects -- and, of course, which updates are most solid on my system. 
 
And yes, I still enjoy the monthly release of new features, knowing I'll have them eventually. 

Yup... I am currently waiting for Manchester to be released to see if it fixes things on my system. I am an offline installer so I would prefer not to move backwards (it's a manual installation which overwrites the previous one which supposedly works but I am hesitant to do so because it MIGHT cause some oddities based on SOME reports).
 
Otherwise I will be trying Kingston and if that doesn't work maybe Jamaican Plains. I'm thinking Kingston would be the better choice because it seemed like a refinement of JP and there weren't any complaints (aside from the instrument updates which are separate and unrelated to the main Sonar APP).
 
Also... and I mentioned this in my other thread, what is happening on my system is my Performance Module is showing much higher than normal CPU usage across all cores and recently (because my project track count had grown as well as my "Comping" splits/edits) the HDD icon was redlining (which cause engine dropouts). That is why I increased my interface buffers (which reduces CPU) and read/write buffers (which reduces HDD dropouts).
 
I also started freezing tracks I wasn't screwing with anymore or recording into which Ive never had to do in the past.
 
I mention all this because perhaps it will help folks having these issues with Lexington muddle through until Manchester is released. As I said I think I'm going to wait for Manchester, test it and then if it doesn't correct these issues install Kingston.
 
 
Cheeeeeers!

Paul P

JonD
I now plan to only update maybe twice a year, depending on where I'm at in my projects -- and, of course, which updates are most solid on my system. 

 
It would be nice if we could have more than one Platinum update installed at the same time, as we could with previous Sonar versions.  It would make deciding which one to rely on for a while easier, and in the case of different bugs in different versions, choose the update that doesn't screw up what we need to do right now.  We already have sort of this capability, we can roll back and forward at will, but it's a lot more trouble than just firing up, for example,
X3e which is already lying around.
 

I don't think I'd want EVERY monthly version as a standalone install but would definitely like the option to say "Okay... I like THIS version so don't allow it to be overwritten by follow up versions... but still install the followups as their own standalones".
 
OT (kind of) but I recently realized from the suggestion of another user (might have even been you) that with these rolling updates we lose the option of two audio engines open at once. So you cannot have transport going in two open Sonar windows... which requires two different versions of Sonar. So anyone new who does NOT have X3 or earlier versions will never be able to do that unless Cakewalk allows multiple open projects to play/record/etc at the same time.
 
Sorry if that doesn't make sense... but it's totes a thingie.