Wookiee

Beepster
 
 
http://forum.cakewalk.com/Lexington-crashes-during-recording-in-CompingSound-on-Sound-m3341674.aspx
 
If that IS the case I cannot update to Lexington. It does strike me as system specific.
 
 

I was unable to reproduce this problem using Arturia's Wurlizter V.
First recorded the Synth on its own, then set a loop and turned on Comping mode, loop around three times, stopped recording without a crash.

Yeah I saw your post. Thanks for checking it out, Wookster.

BobF
You're STILL not updated yet?!  

Blapples deep in a project... for another. My mind is in the tune at the moment.
 
Despite my incessant navel gazing around here I am a bit of an artsy frucker and the update process would crush the flow.
 
Once it's written and fired off for approval I'll be updating before tracking the finals.
 
;-)

arlen2133
Hi Beepster,
I did get a chance to take Lexington out for a few runs. 
At first glance, it was indeed snappier then Kingston (whoo hoo) and played nicely.
I haven't had any problems with midi, aux tracks, take lanes or the likes.
 
That's NOT to say I didn't have any crashes...
Had two -the second one was on purpose to see if I could repeat the first one.
It appears that one of my plugins (eventide ultrachannel) doesn't like it anymore if I change the track it's on from stereo to mono.  When I mix, I typically change the Master bus from stereo to mono and pan to the left.  This continues to work fine in Lexington.  Sometimes though I want to check a track out for phase or whatever.  Tried this out with the ultrachannel on it and it immediately crashed SP.  Didn't do that in Kingston. 
 
Didn't file report yet cause during the holiday, I would probe the forum to see if anyone else was having issues.
This post let me know some have (most haven't).  I'll submit it and see if they've got a fix for it.

Thanks, Arlen. I don't have that plug... and actually pretty much stick to the included plugin suite aside from a few specific goodies I've gathered along the way (mostly Cake stuff as well but some seemingly Sonar friendly third party gack).
 
I think I have ONE more little part to write for my current session then a quick mix before I fire it off for approval. Then I'm gonna jump in balls first on Lexington and use Windows restore as my failsafe before doing my final tracks (and all the other wackiness I may do on top of that).
 
It would be a hardcore session so will likely expose any definciencies. I think I'll probably give the Aux track stuff a rudimentary workout too since that seems to be working well for others and would certainly benefit my weird arse workflow.
 
Cheers.
 
PS: You should post a thread about the Eventide thing. I'm not sure but I think Stratman might use that one and I'm sure others do as well so you'd be providing a service by posting the issue. Sadly I cannot test that one for ya.
 
Good luck.

Thanks Steve for checking that for me. I'll have to go get the update and check it out.  Did you check it on a track?

Good to know. I'll update that plug and see what we got.
Thanks again.

scook
Eventide rarely announces updates to their products. I just checked and there was an update last Oct. I just tested UltraChannel v2.0.23 and the Oct 2015 update 2.0.29, by adding the plug-in to the master bus, toggling the track interleave while the transport was running. Lexington did not crash on me.

Thanks again Steve for the advice..
UPDATE: This is v2.1.2 now.  Worked like a charm. 
So, as I said before, I don't have any issues with Lexington.  I'm good for now. 
 
Craig, thanks for checking in and letting me know.  Sometimes i forget to check for updates.  Forum is a good reminder. 

1) Delete/Cut special not pulling all clips to the left if a portion of the selected track does not have a clip in it.
2) When trying to delete multiple clips in a track all at once, only a portion of them are deleted.
 
Bug reports submitted. Not, got to figure out how to roll back to a previous version so I don't have to be Gibson's (unwilling) beta tester.

I've been working with Lex since I first posted this and have had nothing but problems (compared to Foxboro).
 
Lexington is sluggish, glitchy and erratic. I am very disappointed with this update and am going to have to try installing an earlier version.
 
Also the Aux track stuff, which was one of the main reasons I updated, are kind of more hassle than they're worth because of the screwed up Solo stuff (which does not allow you to just solo a track... you have to solo the track and the Aux... and of course UNsolo them again after... bad workflow).
 
So yeah... ya'll know I'm not one to crap on a release for no reason but I am seriously underwhelmed with Lex.
 
The performance improvements (another thing I was updating for) seem to be non existent on my system and actually taken multiple steps backwards on my rig.  Must only be for Win10 users or something (I'm on Win7).
 
Ugh. Seriously I don't like making negative reports like this but it ain't good. Maybe Kingston will be better.

It's odd how people's experience differs.
 
I'm running Lex on 2 systems - 1 Win 7 & 1 Win 10 and Lex, for me, is by far the most consistently stable release ever.
 
Hell, I've even got Pentagon to work on both!

mettelus
Manchester looks like the aux track Solo is resolved.

I am also not seeing any noticeable "speed" improvements on my machine either, so not sure where the common thread lies (also Win7 here).

Yeah... I saw that in the eZine which is great. But if the performance is similar to Lex i'mma gonna be in a conundrum.
 
Do I go forwards for the Aux Solo (and maybe be stuck with crappy performance) or backwards (and be stuck with crummy Aux routing solo functionality... or no Aux tracks at all).
 
Thing is I KNOW some of this performance stuff is because I switched back to using 96khz but still, it should not be THIS bad. I used 96khz on many projects in the past and it was fine. Now I'm having to REAM my i/o and interface buffers and freeze stuff.
 
Methinks us Win7 users have been left in the dust. They said they were gonna drop us at some point but wouldn't say when (after I asked).

tenfoot

Beepster
 
 
Methinks us Win7 users have been left in the dust. They said they were gonna drop us at some point but wouldn't say when (after I asked).

I don't think this is true at all Beepster. Many people, myself included, are running Lexington on windows 7 without issue, Confirmational bias kicks in when we have problems - we seek out any common factor whether it is  the cause of our woes or not. 
 
Just roll back to an earlier version until your DAW performance improves. It takes no time to do. If it doesn't improve, come back to Lexington and let the troubleshooting begin.

No, really. The quote was quite literally "We will stop testing on Win7 soon" (or something very close to that wording but "soon" was definitely used). That was posted a little while after Sonar 2105 was released. I think it was Noel or Ryan. They would not elaborate on when and it's not really the type of thing I think they'd announce.
 
Anyway... my point wasn't that it isn't working. It was that a) they may have indeed stopped testing on Win7 machines now, b) that the performance improvements touted in Lex were possibly acheived by taking advantage of stuff in Win10 that does not exist in Win7 and c) that SOME hardware configurations running on Win7 may start LOSING performance because the program wasn't tested as rigorously as it would have been with X3 or at the start of 2015.
 
Lexington "works" but as I said it is definitely not faster (on MY system) and I've been getting a lot of lags, glitches and dropouts since installing it (while working on a rather modest project compared to previous projects). It's just general stuff that adds up. It kind of reminds me of how X2 used to get weird on me all the time... except not as bad (thankfully).
 
Others had no problems X2 while I found it almost unusable. X3 was perfect on my system (aside from some specific bugs) as has SPlat been up until and including Foxboro (my last version) but now getting wonky with Lex.
 
Just reporting what;s happening and speculating on what has been said in the past about Win7. I know they can't support old OS's in perpetuity and continue to expand the program so if that IS the case I may have to just suck it up and either upgrade to 10 or lock the system down to use the last verison of Sonar that works.
 
Alternatively I may have to resort to the plan I had when X2 was giving me nothing but headaches. Since most of my issues are generally related to tracking and editing I was going to start using Cubase or Reaper to track and edit then import the final takes into Sonar for mixing (which is a far superior environment for mixing IMO).
 
I'll just have to do some tinkering to see if I can avoid that. Maybe JP or Kingston will play nicer on my rig or hopefully the new Manchester update will be better.
 
That does make me wonder whether the included Melodyne 4 will work in older versions or if it's going to be locked to Manchester like other things were in the past.
 
Cheers.

"Sonar 2150."
 
And apparently I keep moving forward in time at an alarming rate.
 
HALP!
 
...
 
and accidentally overwriting my original posts instead of creating new ones so this doesn't makes sense...
 
lol

Responding to finding any problems with Lexington:
An intermittent problem that's come up for me is that the play/pause doesn't work after loading a project.
I'll hit the space bar or click the Play button and nothing happens. Then I have to close the project, open it again and then everything is fine.

I haven't seen anyone else reporting this issue, so maybe it's something unique to my setup. If I find a pattern to it I'll report it to Cakewalk, but so far it's been pretty random.  It does happen pretty often tho.

John
I'm on Windows 10 Beep and I am seeing much the same performance you are. This started problem under Lexington. 

Yeah... that seems to indicate something weird is going on because I don't recall the last time you've ever had issues aside from one off confirmable bugs on your rig.
 
It's like by stomping on the gas pedal to get more speed it's rattled some bolts loose for some of us (but not all).
 
Really hoping Manchester works out but I will check out Kingston if not.
 
I do really need to learn Reaper basics though so maybe this is just fate nudging me in that direction and then Sonar will sort itself out when it's time to wander home.
 
Cheers!

Beepster

John
I'm on Windows 10 Beep and I am seeing much the same performance you are. This started problem under Lexington. 

Yeah... that seems to indicate something weird is going on because I don't recall the last time you've ever had issues aside from one off confirmable bugs on your rig.
 
It's like by stomping on the gas pedal to get more speed it's rattled some bolts loose for some of us (but not all).
 
Really hoping Manchester works out but I will check out Kingston if not.
 
I do really need to learn Reaper basics though so maybe this is just fate nudging me in that direction and then Sonar will sort itself out when it's time to wander home.
 
Cheers!

No need to swear Beep by calling up the grim reaper.   What we need is for CW to help out with this. 
At present most of my projects are touchy to play back due to this problem. The first core on my quad core CPU is being hammered. The others are also running high. Through out the year this was not happening only with the last update did this start to happen. I have even increased my ASIO buffer with no reduction of the CPU usage. There is something going on internally that is causing this and I don't know what it is. I also checked my system latency and it is good. So I don't know what could be the problem.