The Sonar "Cambridge" update introduced what I thought was a fairly significant problem with the "new" Control Bar, and I must admit I expected some sort of a Quick repair to this issue.
 
As we all know, the Control Bar no longer retains the positioning of the different modules, and every time you restart Sonar, the Control Bar reverts to a default module positioning, not at all like n previous Sonar versions, where it would remember your custom positioning. I find this very disruptive to my workflow every time I start Sonar, and have been anticipating a fix for this, which hasn't come as of yet.
Wasn't there some advantage to the new membership model that was going to improve the timely repair of issues such as this ?
It's April, and as far as I've seen, there's only been 1 quick fix, as I recall.
Call me impatient, but is this issue really that hard to fix, since it's a feature that has only recently been added to Sonar ?

There is also the file paths issue.

I would prefer cakewalk not respond to this and get it out as soon as they can.

I don't hold up much hope for a hotfix now as it may be only another 2 weeks to the next major release where the fix will probably be in. It would have been a lot better if we had seen it a lot earlier but we are where we are. Easter and the Z3TA+2 bug may have slowed things.

Btw Without source code in front of you nobody can tell how hard it is to fix.

It's true, I don't know spit about programming, and how hard this would be to fix, but if I downgrade back to the "Braintree" release, there are some new Prochannel plugs that I have used in "Cambridge" projects that probably would not work in "Braintree" release . . . for sure in the future I may be wary of upgrading right away until such buginess has been repaired.
 

If there is a release every month, it's rather good I think.
Not a bad list of fixes in Cambridge.
 
It might be a bigger thing with each release than we realize.
 
I would prefer every two weeks too, but might be difficult, don't know.
More than anything, how CWBRN's are treated is the big deal for me - things reported and confirmed years ago that are still there.
 
Was it a single CWBRN in fix list in Cambridge - among 50 fixes?
 
So collection on reports, sorting them to possible similar categories and on todo-list - that is the major issue. How many new users should experience a particular problem, spend hours narrowing down, trying to find workarounds, are needed before top of todo list?

I believe it's all confirmed, from the many forum posts, that everyone who upgraded to Cambridge experienced this Control Bar issue, and Cakewalk have confirmed they are aware of it, and looking into it . . . great, but it still currently has a great degree of suckage when you use this feature daily, and it lets you down.

Ben Staton (Cakewalk) was saying in a post that they were aware and would have a fix asap. I'm guessing that it is probably more expedient to do all the months fixes in one go.

It's one reason why I'm not personally a fan of upgrades that come so often. While it's true that there are more fixes than new bugs every time (and kudos for that), sometimes a new bug can be more show disruptive than finally getting a fix for that bug that you had already found a work-around for.
 
I would definitely not like to upgrade every two weeks.

Sanderxpander
It's one reason why I'm not personally a fan of upgrades that come so often. While it's true that there are more fixes than new bugs every time (and kudos for that), sometimes a new bug can be more show disruptive than finally getting a fix for that bug that you had already found a work-around for.
 
I would definitely not like to upgrade every two weeks.

That's why the clever people (I'm not one yet) should wait 2 to 4 weeks before installing.

mudgel
Ben Staton (Cakewalk) was saying in a post that they were aware and would have a fix asap. I'm guessing that it is probably more expedient to do all the months fixes in one go.

If Ben said they would have a fix ASAP, you can bet money it will be in the next update.
 
And on the subject of fixes - it seems there's an undocumented fix. It used to be that if you docked an FX Chain, the preset label would be outside the chain and to the right. It no longer seems to do this and the preset label is placed properly. Can anyone confirm?

Doktor Avalanche

Sanderxpander
It's one reason why I'm not personally a fan of upgrades that come so often. While it's true that there are more fixes than new bugs every time (and kudos for that), sometimes a new bug can be more show disruptive than finally getting a fix for that bug that you had already found a work-around for.
 
I would definitely not like to upgrade every two weeks.

That's why the clever people (I'm not one yet) should wait 2 to 4 weeks before installing.

while that's generally true, does it really work with the new monthly rollouts? 4 weeks and the next version's there, so for example, is it possible to install braintree rather than cambridge?
personally i'd expect to see some of the monthly updates to be stability-only, and not introduce new features each drop... though i understand this may be harder for marketing, who are "new feature oriented"
/fwiw