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

And Music Creator is quite popular, so it pays the bills that keeps all the dev happening...

The improvement of the contrast between enabled and disabled effects would be done in 1 hour. This would be very easy.
Here I was hoping for improvement.
 

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?

That's actually something I screwed up thanks for letting us know. No SONAR developers time was wasted because I accidentally tagged a video incorrectly. 

I don't see any mistake.  Anyone could select from the list of videos, not watch just the first one.

Willy Jones [Cakewalk]
That's actually something I screwed up thanks for letting us know. No SONAR developers time was wasted because I accidentally tagged a video incorrectly. 

Thanks for letting us know. I scratched my head a bit there.

robert_e_bone
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
 

Solid way of thinking, thank you.
 
I hope this new policy will mean Cake don't feel obliged to make an announced new feature ready before putting the bug fixes out there.
 
More like - every two or four weeks - what is fixed is fixed, put it out there to have as few people as possible experience the same problem.

lfm
I hope this new policy will mean Cake don't feel obliged to make an announced new feature ready before putting the bug fixes out there.

As far as I know the bug fixes are considered part of a release package - very much like the one what was released today, a mix of features, content, and fixes.
 
I must admit it must have taken some cojones to release on a Friday, what with tech support off for the weekend...guess they felt confident nothing would blow up.

Kylotan
 
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.
 

Thanks.
But check out the code from version handler - 10 minutes later it's fixed - check code in again. And it will be there in the next release. Unless someone locked it already working on the same class.
 
The 16 years I ran my own business - it was hours before a bug like this was fixed and out to those reported it. 200 000 lines of code or so, at that time. But basically one product, so in all honesty much simpler to do - and compiles in minutes.
 
Working as employe in a team of 6 - it was a couple of weeks tops(ip camera system). I guess that is where my estimate came from. Guessing Cake team is about that size working on Sonar code.
 
On the other hand, compliments to staff, I had some confusion over Navigator, the floating one was the one I found first - and help file had no references to the other built in. Scook seems to have updated staff on this and now has clarifications in help. Good job.
 
Total - I'm all exited about new Sonar. Running really smooth here.
Just trying to set my expectations right....but maybe Cake are learning too...

Anderton

lfm
I hope this new policy will mean Cake don't feel obliged to make an announced new feature ready before putting the bug fixes out there.

As far as I know the bug fixes are considered part of a release package - very much like the one what was released today, a mix of features, content, and fixes.

Thanks.
I hope you are wrong - but you probably know the drill better than most.
 
Let's say a major new feature - like VCA fader groups are to be implemented.
That's quite a makeover and probably take 6-12 months or something.
 
My hope is they let go of that principle - if they fixed 5 things in two weeks - release that.
That would be 5 things that thousands of people are waiting for to be fixed, and thousands more that never had to be exposed to them, having an all good experience with Sonar.
 
The downside of pre-annoucing features may be that they feel obliged to have at least one thing ready for one of the versions before every release.
 
So hold back on pre-announcing until max two months away, maybe....we will see...

riojazz
I don't see any mistake.  Anyone could select from the list of videos, not watch just the first one.

All videos were about Music Creator 7.
A bit odd when updating Sonar - that's what I thought anyway.
But it's clarified what it happend....