Anderton
The reason Cakewalk structured updates the way they did is you can update quarterly if you like. Or if you want to be on the bleeding edge, you can update every month...or update one month if there's a feature you really like, then not do anything for another six months. Or jump off for a year and come back in again later.
Windows 10 update comes with a slow ring and an insider programme. You decide if you want to be fast and bleeding edge or slow and stable. You have a choice. With Sonar seems every month we are on a bleeding edge updates, and sure we don't have to update.
I think it's fairly safe to assume that this month the start screen was rushed out the door half baked, worse still it is the first thing that happens when you start Sonar. It's a first impression thing. Sure you can switch it off, but here is the thing:
a) This gives a first impression for people running demo's who might buy Sonar.
b) I would suggest that the customer expectation in general is that each monthly release should be stable, esp in a DAW environment.
c) The start screen was more of less the only thing this month.
d) The perception is features will be rushed out the door every month come what may.
e) Every month we are left wondering when and if Cakewalk will fix regression issues quickly or not.
Now if there was a fast ring and a slow ring much like windows 10 update, maybe customer expectations could be managed. Of course a customer can hold back, but if beta code is introduced upon each release they are left with a choice of evils every month.
So far Cakewalk have done a brilliant job management our expectations in the forums, but this month there's has not been much communication (e.g. little acknowledgement with start screen issues). And this is understandable as it's clear they are extremely busy working on those audio enhancements, but I would not say it is ideal.