I think it has been a misunderstanding (probably due to my weird english ahaha). I was trying to say that I really liked the SONAR PLATINUM UI design as I love the CBB UI since it is the same, but I can't work with only a beautiful UI. I had been experimenting crashes, tons of audio dropouts and some Waves plugins extrangely dissappearing (the vst3 version of Waves Grand Rhapsody Piano for example). Also, as Scott, I think that Audiosnap palette is broken and some editing tools seems outdated compared to things like REAPER. I would like to see substantial changes in that direction instead of tiny "monthly updates" with cosmetic features and non deep bug fixes. In the past, I could understand the existance of monthly updates because there was a monthly subscription model but today there is no need on keep going that way. I am grateful to Bandlab for giving this amazing DAW for free and for removing all the "bloatware" but I don't want to be in an eternal "insiders" program with this monthly updates system. Honestly I hate it.
P.D.: For example, take a look on the latest 2018.08 update. Meng said that it has been delayed because they want to introduce a new feature but it hasn't been ready and the developers must remove it in order to launch this 2018.08 release. A release that basically add the option to remove the insignificant "new feature" of 2017.07 and, in addition, a new one that needed a hotfix few days later because it was completely broken. All of that make me laugh and I just don't understand why not to wait and test the things properly, releasing substantial updates only when they are ready. 

There is a significant new feature coming, but as with any major change it takes time to iron out the wrinkles. It was almost in this build, but Noel & company decided it wasn't quite ready for primetime yet.
 
We should be grateful for such a sensible approach. The traditional method for commercial software is to constantly push out new features just so you can tick off a box in a features matrix, regardless of how polished those features are. 
 

my feelings sure aren't mixed.  i'm down with CbB (yeah you know me)

bitflipper
There is a significant new feature coming, but as with any major change it takes time to iron out the wrinkles. It was almost in this build, but Noel & company decided it wasn't quite ready for primetime yet.
 
We should be grateful for such a sensible approach. The traditional method for commercial software is to constantly push out new features just so you can tick off a box in a features matrix, regardless of how polished those features are. 
 

+1
 
I'm all for stability first (even if it takes longer to release) before the new features.
 
I'm still trying to figure out a fix on CbB crashing on only one of my projects (crashes when loading Overloud's TH3). I have Bandlab Assistant 3.2.1 (which it says is the latest), but not sure if the one in this thread is newer? 
I've already put in a ticket a five days ago and waiting on a reply.

Hey Mesh, did you send the crash report, or reach out to the support staff via email/submit a request page in the help guide? If you've sent the report after seeing the pop up message, go ahead and drop a line to support@cakewalk.com as well. It sounds like you may have figured out the issue was project specific, but its worth a shot to get some additional feedback. 

It seems to me the OP should develop some better  methods. If he has found an earlier version of Splat or CbB to be more bug free and crashing less with no VST problems, then he should be using that version. There's no obligation to install every monthly update.
 
If anyone feels like they have a pretty stable problem free system, then they should make an image file of their C drive to preserve this stability and turn off auto Win updates, until it's time to try a new version.




 
I know some that are using Win 7 and a pretty old version and love the stability and never update anything unless absolutely needed. Predictability is very good. While to me this may be a little too extreme, I do tend to like to stick with a version for 2-3 months before trying a new version, so I'm well aware of any bugs and won't be blindsided if I have an important session.
 
One thing I love about the current system is I can open CbB and Splat at the same time and compare things. Or decide to use Splat instead of CbB. Also I recently found out that with CbB you can make a copy of the Cakewalk Core folder and then install the new version.
 
 If you suspect a bug or want to be safe with an important client, you can double click cakewalk.exe in the old version and immediately roll back to an earlier version. The folder is only 156 megs, so it doesn't take up any real HD space.
 
When I installed CbB in April I found it to be noticeably more stable than Splat. I'm now using 2017.07 and it's just as good if not better. I now have the most stable problem free system I've had since the days of Sonar 8.5. 
 
I'm extremely pleased with CbB and the excellent seasoned team with Noel, et al. It's also refreshing to see Meng here sometimes. The last time that happened was in the days before Roland and Gibson was when Greg Hendershot would pop in the forum sometimes.
 

Customer Support [Cakewalk]
Hey Mesh, did you send the crash report, or reach out to the support staff via email/submit a request page in the help guide? If you've sent the report after seeing the pop up message, go ahead and drop a line to support@cakewalk.com as well. It sounds like you may have figured out the issue was project specific, but its worth a shot to get some additional feedback. 

Yes, but I've only sent the crash report. Regarding that TH3 issue, I had been using TH3 in that project all along and everything was running as it should prior to that. The only thing I did different was (that day) I installed Caliburn from Kuassa (very nice Marshall amps BTW) and used that as well, and saved the project. After that, it always crashed when opening that project.
 
Anyway, I'll also drop a line to support.
Thanks for chiming in on this, it's greatly appreciated to get help over here. :)

Hi Mesh, I had also a crash issue with TH3 and CbB. It happened when I clicked the Interleave button (to mono). Doing the same in Splat did not cause a crash. After some research I found out that it only crashed with the VST2 version of TH3 (which I used in CbB, but not in Splat). Using the VST3 version of TH3 did not crash in either DAW! Maybe this information helps you!
 
Marc

gmp
It seems to me the OP should develop some better  methods. If he has found an earlier version of Splat or CbB to be more bug free and crashing less with no VST problems, then he should be using that version. There's no obligation to install every monthly update.
 

no but there's a natural human inquisitiveness that leads people to install updates - but there's no easy roll-back option as there was for sonar so it's hard to use a specific version unless you jump through the "copy installer before deletion"  hoops, which not every user will feel comfortable with

I'm having fewer problems than ever with Cakewalk, fka Sonar, fka Cakewalk, but I've been with Cakewalk since 1995 and it's always worked well for me. 
 
I love it (and I wear my T-shirt whenever its clean.