I hope we'll get an update soon. But I understand that it's a difficult challenge for CW developers to release a monthly update. Maybe it would be a good solution for CW to advertise the subscription offer like this: "at least 10 major updates a year". That would give them one or two "jokers" per year.

ebibault51
I hope we'll get an update soon. But I understand that it's a difficult challenge for CW developers to release a monthly update. Maybe it would be a good solution for CW to advertise the subscription offer like this: "at least 10 major updates a year". That would give them one or two "jokers" per year.

They've never missed a boat yet. There's been an update every month, usually right at the end of the month.
 
If that's difficult, and I'm sure it is, then hats off to them for being such badasses.

Yes, you're right. I think that this subscription program is really a new, innovative service. And this program encourages me to test new features, new techniques... and finally makes me work more on music... Isn't it the best compliment that we can give to Cakewalk?
 
That's fine... but [I must admit that when I first read the announcement of this subscription model, I was ANGRY] :-)

I figured this would be a problem of their periodic update model: Despite the whining about it people would come to expect and then demand them.
 
Personally I wouldn't mind seeing the pace of updates slowed. Rather than try to maintain a monthly schedule, release when there's something that merits a release, which can sometimes take longer.

"which can sometimes take longer." insert at end of quote, "(or less)." Like the ability to ARA the tempo map from Melodyne into SPLAT per the master baker.
 
Jim

 
I choose to believe that when it takes longer, there should be special things baking... so bring it on when done well bakers 

Sycraft
I figured this would be a problem of their periodic update model: Despite the whining about it people would come to expect and then demand them.
 
Personally I wouldn't mind seeing the pace of updates slowed. Rather than try to maintain a monthly schedule, release when there's something that merits a release, which can sometimes take longer.

Remember, development of functionality occurs in parallel. Another way to look at it is to release the simple things on the monthly schedule while a more complex function bakes in the background for a future release. Regardless, Cakewalk can't win either way: if they release something simple, then people complain there wasn't anything substantial in the release. If they miss a release, people will complain about that. People who like to complain can always find something to complain about.

Anderton
People who like to complain can always find something to complain about.

Big Yes

Anderton

Sycraft
I figured this would be a problem of their periodic update model: Despite the whining about it people would come to expect and then demand them.
 
Personally I wouldn't mind seeing the pace of updates slowed. Rather than try to maintain a monthly schedule, release when there's something that merits a release, which can sometimes take longer.

Remember, development of functionality occurs in parallel. Another way to look at it is to release the simple things on the monthly schedule while a more complex function bakes in the background for a future release. Regardless, Cakewalk can't win either way: if they release something simple, then people complain there wasn't anything substantial in the release. If they miss a release, people will complain about that. People who like to complain can always find something to complain about.

Craig , this reply is qualified as a complaint . You used the word complain four times .
"No soup for You " :-)
All the best
Jan

Anderton

Sycraft
I figured this would be a problem of their periodic update model: Despite the whining about it people would come to expect and then demand them.
 
Personally I wouldn't mind seeing the pace of updates slowed. Rather than try to maintain a monthly schedule, release when there's something that merits a release, which can sometimes take longer.

Remember, development of functionality occurs in parallel. Another way to look at it is to release the simple things on the monthly schedule while a more complex function bakes in the background for a future release. Regardless, Cakewalk can't win either way: if they release something simple, then people complain there wasn't anything substantial in the release. If they miss a release, people will complain about that. People who like to complain can always find something to complain about.

 
Well stated Craig. I am personally all for monthly updates as they invariably include fixes and enhancements which is part of making the DAW more stable. As far as features go, releases based on required time and complexity makes sense. What matters is the overall development of the DAW over, say, an year or for better justification, 6 monthly periods.
 
In this regard, annual subscription renewal option makes better sense to me than monthly. I say this because monthly subscribers could tend to be more impatient about getting timely updates and having "valued" features every month. But then, that's a personal choice...