• SONAR
  • When can we expect the first Platinum update?
2015/01/26 22:33:59
microapp
When will the first Platinum update be available?
Will updates be on the 21st of the month (the Platinum release date) ?
Is it possible to inform us what is being worked on for the next monthly update?
2015/01/26 22:36:34
cclarry
It's already been issued...

We are currently awaiting the second update.
 
 
2015/01/26 22:44:26
microapp
No, the 254 build was the official release.
254 may have been an update for the lottery winners who got the early release.
How about the next update ?
2015/01/26 22:55:13
Splat
..which still happens to be the second update for what it's worth :) I can tell you this, Cakewalk will be releasing regular updates when they are ready and tested... I'm sure they will let you know when they are ready...
2015/01/26 23:01:08
bitman
They have a bit of digging out to do right now.
 
Dated material -> http://www.foxnews.com/we...other-major-snowstorm/
2015/01/26 23:06:48
cclarry
microapp
No, the 254 build was the official release.
254 may have been an update for the lottery winners who got the early release.
How about the next update ?



252  was the official release that I received on the 21st.

The 254 update came a day or 2 later...
2015/01/26 23:27:09
microapp
I am pretty sure 254  was what I downloaded the PM of the 21st. I suppose it could have been updated w/o me knowing it. It is not important what the next update is called.
This is not the OP questions.
This may seem trivial but consider the case of wanting to keep as current as possible while at the same time minimizing downtime.
If the update is going to be on a strict schedule, then one could maybe not schedule clients for a few hours that day, do the update and test thoroughly. If there were issues with the update, like breaking something unexpected, then you could roll-back.
This would become even more important if we actually were aware of what was going to be in the update.
Maybe the update would contain a fix for something of interest to a particular client which is not working.
You could push that client out until after the update.
A regular schedule would facilitate scheduling of downtime.
2015/01/27 00:22:18
Anderton
microapp
If the update is going to be on a strict schedule, then one could maybe not schedule clients for a few hours that day, do the update and test thoroughly. If there were issues with the update, like breaking something unexpected, then you could roll-back.
This would become even more important if we actually were aware of what was going to be in the update.
Maybe the update would contain a fix for something of interest to a particular client which is not working.
You could push that client out until after the update.
A regular schedule would facilitate scheduling of downtime.



Unfortunately I doubt there will be a clockwork schedule (but I could be wrong), there are lots of variables. For example, there was a separate update recently of my amps to replace incorrect versions with correct versions. I suppose it could have waited, but as it was a mistake at Cakewalk's end, they wanted to solve it as soon as possible. I think "about monthly" will be the way it works. 
 
However, remember that you get to choose when to update. You can see what's in it, and decide to skip it, postpone, or wait until several updates have happened and update all at once. So the bottom line is you control the update calendar more than Cakewalk. 
 
As to what's coming up, I'm submitting a list of what I have planned so far in terms of content. This will be folded in with other features. Some features will not be announced too much in advance to avoid giving competitors a heads-up. Others will be announced well in advance.
 
Others will occur based on feedback. For example, the comments about the amp sims "get" that these are designed to be "plug-and-play" effects where you just drag them into place and start playing, and maybe make a few tweaks or put some other effects afterwards. The reaction could have been "This sucks, I want a rack of stuff so I can create my own amps, your presets suck, and you suck." In that case, there wouldn't have been any more amps.
 
But because the reaction has been favorable, today I proposed doing an "Amp of the Month," which I really hadn't considered before even though I have amps in various stages of development for my own use. If I finish them I'll have enough to last for at least a year. Probably the Acoustic Guitar amp, Hollow Body amp, Keyboard and EDaMp will be next...however even this brings up an issue of why scheduling is variable. The Hollow Body amp depends on when Gibson Memphis ships me several guitars for testing with it, so that might get delayed whereas the amp for EDM might get pushed ahead because I'm close to having it done anyway. 
2015/01/27 00:44:41
microapp
If there were to be a strict schedule, it would make sense to make use of that in planning application of updates.
If not then as you say, you may simply have to delay application until your schedule allows it.
I think a somewhat flexible schedule is better for development otherwise the Bakers would be exchanging one or two updates a year for twelve. I would rather things be right than rushed to make a deadline.

As to what's coming up, I'm submitting a list of what I have planned so far in terms of content. This will be folded in with other features. Some features will not be announced too much in advance to avoid giving competitors a heads-up. Others will be announced well in advance.
.

It is always good for us to know as much as possible about what is baking without giving away any advantage to the competition.
I think it would be a good idea to insure that a bug fix and feature modification list is included with every update to help decide if and when to apply that update and to help with testing the changes. Nothing is worse than finding some unknown change broke something else while in front of a client.
 
2015/01/27 05:45:19
mudgel
21.0.254 was called Allston Update 1.

It was to fix a Melodyne use issue that cropped up during the lottery winners early use which was 21.0.252
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account