I just deleted 30GB of files from the Cakewalk/Downloads folder. I've been getting Corrupted download errors more and more lately. Deleting all these files helped. It probably means I can't revert installed versions, but it stopped the errors for me.

brconflict
I just deleted 30GB of files from the Cakewalk/Downloads folder. I've been getting Corrupted download errors more and more lately. Deleting all these files helped. It probably means I can't revert installed versions, but it stopped the errors for me.

Not from those files, but I'm pretty sure they'll be in your account...just download the one you need to revert to it.

The Command Center will fetch the installers when needed, if they are not found in the download files cache.

I'm good now. D-Pro isn't installing, but I don't need it.

Is nobody here who using and External Insert plug-in function?
This is very useful function and my favorite.
 
But when External Insert loaded on bus channel, it shows some problems (such as bus solo function issue, lost some midi note when playing issue...etc)
 
As I know, Cakewalk Tech Team already knows about this issue.
I would like to request fixing it on future update.
 

Quick question.  As I look at the new update it appears that 1/2 the content files for Rapture PRO files are now RED.  I know they were green last month.  Does this mean that I need to reinstall them or are they included elsewhere (in Rapture PRO)?  These are the ones labeled D-Pro Part 1, D-Pro Part 2, etc.....all the way to the end. Want to make sure I have all the content I should (even if I don't use it often). 

(SOLVED)
My transport is recording and playing back twice as fast in Lexington.  The counter in the control bar is counting seconds at a 2:1 ratio. Is there something I should check?
 
I should add that I changed nothing by way of settings in Kingston prior to upgrading, and X3e is still working fine.
 
Update: It seems the Lexington update reverted my sampling rate to 44.1khz. In previous versions, such as X3, if I tried playback or recording in mismatched sampling rates, I'd get an error saying the DAW couldn't open the record device. I no longer see that error in this latest version, and the recording will commence at the wrong sampling rate (like faster ips), skewing the time-stamp in the Control bar. I believe people should be aware of this potential frustration of tracking at the wrong "speed". Had I not seen this, I would have been upset. 
 
Feature Request: If the sampling rate or bit rate is mismatched from the expected or source clock/bit rate, turn the Control Bar time display orange.

Sorry, but I`m disappointed. Since updated to Lexingston Sonar crashes every time after a while on playback.
 
BTW, the startup  windows now appears earlier, but loading a project needs too much time (no difference between Ipswich, Kingston or Lexington).
 
Update:
After rolling back to Kingston all works fine. No more crashes. Another problem with Lexington was, that my Brainworx plugin bx_meter always told me of peak clippings and was hung up. Now it works fine again. I think Lexington is a little bit buggy.

I seem to be having one issue with the "Added support for VST2 to VST3 plug-in migration for instruments" feature.  I have a few projects that are using Sampletank3 VST2, since early on the VST3 version was causing crashes in Sonar Platinum so I removed it and just used the VST2 version.  But that was nine months ago and the current Sonar and Sampletank3 VST3 seem to get along, so now I have both versions enabled. 
 
If I have the option "Replace VST2 Plug-ins When Option Projects" checked and I open one of those old projects everything loads and the Sampletank3 instances are now the VST3 version, but it doesn't play any sounds.  To "fix" it I had to open it's gui and fiddle with it (I think I just pressed some keys on it's virtual keyboard).  If I turn the Replace option off and load the project, Sampletank3 loads as a VST2 and everything works just fine.
 
I also had to increase the ASIO buffer size on my (old) Focusrite Saffire from 4.5ms to 6.0ms in order to fix some new glitching on playback, which kind of surprised me since the same projects played back just fine in Kingston at the more aggressive setting.  That's the third release in a row where I've had to increase my latency to fix playback problems.  I really wish there was some sort of way for Sonar to test a buffer size setting and tell me if it will playback without glitches at that setting.  This trial and error approach is not fun.

At my place, update was fast and bug free as is the program...
 
It really does work. Gotta be something about the OS, divers, or the hardware. Maybe do an OS/driver update and check it again?
 
And as for the post above, I thought you are supposed to change the buffer size on playback of bigger more complicated projects. I know it needs to be at least 1024 for Melodyne to work... Or, in my noobness, maybe I am misunderstanding....