A little bit disappointed by update now not fixing a CWBRN I reported three weeks ago.
Seemed like a real simple things to fix - really annoying using console view.
 
But installing update there were for some reason a video trailer for some other product - Music Creator.
What does this have to do with installing Sonar update?
 
Just wonder - what is focus for devs - that take time from Sonar?
 
Thanks.

lfm
A little bit disappointed by update now not fixing a CWBRN I reported three weeks ago.

 
Even if they'd fixed it the day you reported it, they'd still be QCing it.
 
Also, I've learned fixes that look simple often aren't, but conversely, fixes that look like they'd be complicated can be simple. I guess a lot depends on how much of the program the issue "touches." For example Cakewalk was able to fix the Melodyne issue that cropped up early on in the new version because it lives in its own self-contained environment.
 

Since we are now listing problems in a forum, along with the CWBRN# it would be nice if the Cake folks went to that forum and ticked off the issues that were fixed on a given release. I tested my problem and updated the status as "no change" in this release.
 
If you want us to do new tricks bakers, you should do the same.

Thanks for input.
 
It's just the on/off-button on the EQ module in console - when you choose to collapse EQ-Plot module from menu.
Eq module disappear - but that annoying buttons hovers and cover over everything you have below(up to a point when FX is hidden).
 
It's been like this since X3 too. All version not having ProChannel.

 
Being a programmer - this is a simple Hide call(or visible false) for that button.
 
 
But they work on so many other things - that are not Sonar related - why?
How determined are they making Sonar the best possible?
 
Maybe I'm expecting too much - so set me straight!
Status of CWBRN was changed to Investigating after a few days.
 
Is it one or two months now till next update, or?
It's just as good to know what to expect.
 
Thanks.

https://www.cakewalk.com/Support/Contact/Problem-Report-Status is the best place to start for status, but as Craig mentioned the cycle for software development is not simply changing code. 3 weeks may be a bit overzealous of an expectation to have. As users we have no visibility to the priority queue that is going on behind the scenes.

Mine was CWBRN-31304 at feb 8th.
 
I understand bugs that takes quite some effort to investigate even, then try to see how to fix etc.
But this one was the simplest possible.
 
Set me straight - what can you expect?
Will there be something monthly with at least something fixed, or?
Even if no new features - an update is welcome.

I think there will be some learning curve all the way around, as we settle into this new development/sales model.
 
I can tell you that prior to this new way of doing things, if a bug was reported early enough following a given release, it maybe stood some level of chance of making it into development and then general release for that product version cycle, but if a bug - even a super simple one, was reported say 4-5 months post release, then it was pretty much a CERTAINTY that it would not get released until the next release cycle came out.  That's just the way it was.
 
Now with the new way of doing things, I believe they have indicated several times that maintenance will be faster, and more importantly ongoing, which should REALLY do nice things for the product from here on out.
 
They JUST released updates a little bit ago this afternoon - did anybody test out reported bugs to see if this one got addressed?  (it takes a bit for them to compile the precise list of what made it into release, so it if often quicker to just test for things in the early hours/days after a release is put out there).
 
Bob Bone
 

lfm
...But installing update there were for some reason a video trailer for some other product - Music Creator.
What does this have to do with installing Sonar update?
 
Just wonder - what is focus for devs - that take time from Sonar?
 
Thanks.

 
Music Creator's compiled from the same code base as SONAR. While we work on one, we also work on the other.

lfm
Being a programmer - this is a simple Hide call(or visible false) for that button.

 
Being a programmer, surely you know that is not true in a big program like this. It's likely that there is a complex system in place that decides which UI elements need to be visible or not at a given time and why it isn't triggering under these circumstances may not be obvious.
 
The other thing to consider is that there are a ton of new bugs in Platinum - I found 3 or 4 within half an hour of starting it up - so it's likely that yours is low on the priority list. I do have some sympathy though; it's very frustrating when a bug gets ignored for months and months but the company finds time for Yet Another Analogue EQ/Compressor/Whatever. Obviously it's unlikely to be the same programmers working on each feature however.
 
 

Kylotan
it's very frustrating when a bug gets ignored for months and months but the company finds time for Yet Another Analogue EQ/Compressor/Whatever. Obviously it's unlikely to be the same programmers working on each feature however.

This is true. The only recent plug-ins I recall being added to the program were not developed by Cakewalk. The effects and sims I create have nothing to do with SONAR's code, and you should be thankful for that. My coding experience is limited to bouncing a pixel around on a Commodore-64 screen in Basic...although I must say I was able to make it bounce reasonably well.