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.

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.

That was posted a little while after Sonar 2105 was released

 
No problem then. I don't plan one being around for an other  90 years 
 
Nah, seriously, I did read that support for Windows 7 "would not continue indefinitely" but I don't recall the word "soon" being mentioned.
 
I bloody well hope not 'cos my main DAW is still on 7 and my interface will not run under Win 10 and I'm not ready to buy a new one (yet).

"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

Give Kingston a try Beepster - I saw a very significant performance increase on both of my systems running win 7 with it (there was actually a post on the forum where one of the bakers stated that the perfrmance enhancements were for all windows versions). I have Lexington on both now and haven't seen any loss of performance, but I haven't really pushed either system at this stage. 
 
I understand that eventually Win 7 will not be supported, but I hope it is not as soon as you think.  I like win 10, but the inability to turn off updates is a terrible Idea and an unacceptable risk in a comercial studio or live performance situation. I shouldn't have to worrry that something may stop working every time I connect to the internet then restart my computer, only to have to wait 10mins whilst updates load. Hopefully someone clever will come up with a permanent solution for that little microsoft gem:)
 
 

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.

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

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!

and now I'm stuck in a time loop... lulz.

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.