cparmerlee

Anderton

cparmerlee
This initial launch does include a small number of improvements to the core product.

 
I wouldn't classify Mix Recall and VocalSync as "small improvements,"

I said a small NUMBER of improvements to the core product, not "small improvements."
 
I'm not sure VocalSync will be useful to me as most of what I do is in the instrumental realm.  Mix Recall definitely looks very useful to me.  I would probably buy the upgrade just for that.

Must learn to read slower. BTW I'm researching the ways in which VocalSync can be abused to do functions other than the ones for which it was intended. Don't tell Cakewalk what I'm up to...LOL. For example I've found that with extreme settings, you can unsync vocals that are too tight and where you want more of an ADT effect.

I don't know if it's been finalized, but I think the aim is in time for the NAMM show, which starts on 1/21/15.

Ryan Munnis [Cakewalk]

Beepster
... 
Basically I'm mostly concerned about missing out on plugs or features in the main package. Not extra content which I'm assuming would be advertised beforehand to entice chuckleheads like myself to act.
 
That may not be particularly answerable but just a rough idea would be cool.
...

You're right. I don't think I personally can fully answer that with specifics. The obvious goal is for everything we release to be something you wouldn't want to miss out on, so the pressure is on us to keep you enticed and a member forever :)

Allrighty then, this thread is perfect place to ask the bakers

so what does it take to get 2 of my most wanted things in? Or how may people have to feature request these two things to get you guys to feel "many people would benefit of these so we should implement it" ? 10, 20, 100 people?

Nr 1 : better track highlight on active track instead of like it is now, the track text background is light blue, how about highlighting a little bit of the whole active track? Much easier to see what track is active currently

Nr 2: more visual difference between track and the tracks take lanes, thos was much easier to see difference in the track layers days...

I mean it can't be only me that thinks these enhancements could be useful ?
At least make it optional in the settings.. Fine by me, let the user have option to enable/disable it

I pretty much got used to other stuff now i was disliking before, the very dangerous "click on lower part or a midi/audio clip and the rest is muted/dimmed", i did this so many times accidentally without noticing... But i learned the hard way, now Im very carerull where i click with the mouse... Simply because there is no option to disable that functionality, i know it is a part of comping featur but this is still enabled even if comping mode is not enabled...

Would be nice if cake folks could answer this

Thanks

orhanproject

Ryan Munnis [Cakewalk]

Beepster
... 
Basically I'm mostly concerned about missing out on plugs or features in the main package. Not extra content which I'm assuming would be advertised beforehand to entice chuckleheads like myself to act.
 
That may not be particularly answerable but just a rough idea would be cool.
...

You're right. I don't think I personally can fully answer that with specifics. The obvious goal is for everything we release to be something you wouldn't want to miss out on, so the pressure is on us to keep you enticed and a member forever :)

Allrighty then, this thread is perfect place to ask the bakers

so what does it take to get 2 of my most wanted things in? Or how may people have to feature request these two things to get you guys to feel "many people would benefit of these so we should implement it" ? 10, 20, 100 people?

Nr 1 : better track highlight on active track instead of like it is now, the track text background is light blue, how about highlighting a little bit of the whole active track? Much easier to see what track is active currently

Nr 2: more visual difference between track and the tracks take lanes, thos was much easier to see difference in the track layers days...

I mean it can't be only me that thinks these enhancements could be useful ?
At least make it optional in the settings.. Fine by me, let the user have option to enable/disable it

I pretty much got used to other stuff now i was disliking before, the very dangerous "click on lower part or a midi/audio clip and the rest is muted/dimmed, i did this so many times accidentally without noticing... But i learned the hard way, now Im very carerull where i click with the mouse...

Would be nice if cale folks could answer this

Thanks

Best bet is to post a thread in the Features and Ideas sub forum if you haven't already.
 
http://forum.cakewalk.com/Features-Ideas-f76.aspx
 
Not a gurantee of course but they seem to definitely be keeping an eye on it.

bobgassert
So this Membership means that if you don 't pay every year for the rest of your life your sonar stops working the way its supposed to and all your projects are un usable? I don't like it at all . 

Hey Bob, you should maybe read a few of these 27 pages of thread .
 
Sonar will continue to work in the state it was in when you last paid for it.
 

Beepster

orhanproject

Ryan Munnis [Cakewalk]

Beepster
... 
Basically I'm mostly concerned about missing out on plugs or features in the main package. Not extra content which I'm assuming would be advertised beforehand to entice chuckleheads like myself to act.

That may not be particularly answerable but just a rough idea would be cool.
...

You're right. I don't think I personally can fully answer that with specifics. The obvious goal is for everything we release to be something you wouldn't want to miss out on, so the pressure is on us to keep you enticed and a member forever :)

Allrighty then, this thread is perfect place to ask the bakers

so what does it take to get 2 of my most wanted things in? Or how may people have to feature request these two things to get you guys to feel "many people would benefit of these so we should implement it" ? 10, 20, 100 people?

Nr 1 : better track highlight on active track instead of like it is now, the track text background is light blue, how about highlighting a little bit of the whole active track? Much easier to see what track is active currently

Nr 2: more visual difference between track and the tracks take lanes, thos was much easier to see difference in the track layers days...

I mean it can't be only me that thinks these enhancements could be useful ?
At least make it optional in the settings.. Fine by me, let the user have option to enable/disable it

I pretty much got used to other stuff now i was disliking before, the very dangerous "click on lower part or a midi/audio clip and the rest is muted/dimmed, i did this so many times accidentally without noticing... But i learned the hard way, now Im very carerull where i click with the mouse...

Would be nice if cale folks could answer this

Thanks

Best bet is to post a thread in the Features and Ideas sub forum if you haven't already.
 
http://forum.cakewalk.com/Features-Ideas-f76.aspx
 
Not a gurantee of course but they seem to definitely be keeping an eye on it.

I did it last year if memory doesnt fail me but the thing is even if i do f-request again, i never now whats happening with the feature request, i guess they go for the top most wanted features first, i feel like i have to gather a lot of people so we do a massive request of the feature, like a united thing... So it catches bakers interest...

 

Anderton
 
But remember, the big advantage compared to Adobe is you get to keep stuff. If you want to upgrade, you upgrade. If you don't, you don't but you still get to keep what you paid for.

 
EDIT: Please ignore this Craig, Atsuko just corrected me HERE.
 
 
 
======================================
Craig, with the greatest respect, and with apologies for quoting you slightly out of context, as I detailed in THIS POST, there is also a distinct disadvantage compared to the Adobe model that (obviously) is never being mentioned by you and others in this thread.
 
Taking up an Adobe Subscription Plan doesn't require any initial purchase of a software licence. A new subscriber simply starts paying the same as everyone else, regardless of their previous loyalty or which versions they already own. There is no tiered payment structure for identical products, and there is no requirement to pay a 'fee' to join.
 
I recently subscribed to the Adobe Photography Plan (Photoshop CC + Lightroom 5) as a new user, and I pay the same as everyone else. A new user to the Cakewalk plan being rolled out still has to buy the software licence for $499, which is basically what you keep when you pay a year up front or complete 12 consecutive monthly payments.
 
As I said in the post I linked to, either model can be argued to be better or worse than the other - that's not the point I'm making. What I am saying is that making any comparisons to the Adobe modus operandi, when it's only mentioned that their model doesn't allow you to continue to use the software if you stop subscribing, is slightly disingenuous because it's never mentioned that you don't get to keep the software (i.e. continue to use the licence) because you weren't obliged to purchase it in the first place.
 
I actually subscribed to the Photography Plan precisely because I didn't have to initially shell out five or six hundred dollars in the first place. Yes, I know I have to keep subscribing to be able to use the products, but I did all the calculations and worked out that was a better deal for me long term than upgrading Lightroom 5 (which I do own) or continuing to struggle with Photoshop Elements.
 
 
 

Thanks stevestrummerUK and neirbod

We are 3 people so far then, 97 more needed (maybe more)... :)

Beepster

orhanproject

I did it last year if memory doesnt fail me but the thing is even if i do f-request again, i never now whats happening with the feature request, i guess they go for the top most wanted features first, i feel like i have to gather a lot of people so we do a massive request of the feature, like a united thing... So it catches bakers interest...

Well unfortunately it's not really a democracy and there's no guarantees even if a lot of users are behind a feature (improved notation is good example) so all you can do is make the request thread (and BTW that sub forum was only created in the past couple months so definitely post your request there) and hope the Bakers are able to work it in to their development. Some things just aren't feasible or cost effective.
 
In regards to your one request a lot of people have been asking for more color cusomization options since the X series and in X3 they borught SOME options back but not as many as there were before. Viewing the vids of the new release it looks like they have change the color scheme to be a little lighter/easier to view so maybe they've expanded color options as well.
 
For now the alternative is an add on called Duckbar created and maintained by a foum user (Panu) that many people use, trust and like. I don't have a link but if you google Duckbar and Cakewalk Forums you'll find a ton of threads with info and links to the program.
 
You have to disable it before reporting any problems to Cake tech support though to insure the add on is not somehow mucking things up but my impression is it is not intrusive to Sonar operation for most users. I do not however use it so I can't say one way or the other.
 
Cheers.

Thanks Beepster, ah I see... I'll hope for the best then....
I'll look up duckbar, tnx

rfreeze
Are the 12 month periods set, or do they start/end randomly based on when each user buys in? 
 
I ask, because in my mind random would keep the Baker's marketing guys from dangling carrots on the other side of the line.  This would give me more confidence in the continuous nature of the advertised feature release process.
 
 

The 12 months starts the day you buy in and ends 12 months later so the idea is a perpetually dangling carrot. You can see what's coming up next on one of the Cake pages but I don't currently have the link open to post it. Right now it is showing a drum replacement tool, some FX chain thingies and something else that I'm forgetting right now.

coolbass

Karyn
It is a question that (I think) Andrew touched on briefly when asked about costs in the future.  I've been looking for his post for an hour but can't find it,  but it was along the lines of.. "like the version updates/upgrades in the past", in other words, skip an update and you pay extra (or get less discount) for the next one.

I think you are muddling the waters. As far as I have read,  Cakewalk is saying that if you ever had Sonar/producer or /platinum, the cost of re-entering will be 199$.

Honestly I don't see the value in speculating about the fairly distant future:
 
Cakewalk/Gibson is going to have to produce product/pricing that us users will be willing to pay and will also make it a viable product from a business standpoint.
 
I wouldn't be surprised to see some adjustments in future years to reflect this.
 
 Based on the number I've times I've upgraded over the years, Cakewalk has always tried (and succeeded!) to provide enough stuff to entice me at a price I was willing to pay. I would expect that to continue as they are smart enough to know that if they don't they will lose me as a customer.

I still need to know the bug fix policy.

So, say, for example, just before my subscription ends, there would be a a feature rolled out that was announced long before and I'm eagerly awaiting. Now, a major bug in this new feature slipped through preventing the new feature to work at all. A hot fix will be announced, my subscription ends, the hot fix gets roled.

What about warranty here?
I paid with my subscription for this new feature, but it doesn't work until fixed.
I'm not entitled to the fix, as I'm no member anymore.

How is this handled please?

What about other bugs which get fixed along the way after my subscription has ended?
I'm happy to subscribe in order to get new features, refinements and such.
But afai understand, there have to be a warranty period, for the product as a whole, and for new features and patches in particular that get rolled out?

Please clarify.

Thank you

Beepster

rfreeze
Are the 12 month periods set, or do they start/end randomly based on when each user buys in? 
 
I ask, because in my mind random would keep the Baker's marketing guys from dangling carrots on the other side of the line.  This would give me more confidence in the continuous nature of the advertised feature release process.
 
 

The 12 months starts the day you buy in and ends 12 months later so the idea is a perpetually dangling carrot. You can see what's coming up next on one of the Cake pages but I don't currently have the link open to post it. Right now it is showing a drum replacement tool, some FX chain thingies and something else that I'm forgetting right now.

Rfreeze makes an interesting point.  In the familiar model, Cakewalk (and most other companies) begin working in earnest on a new release after the most recent release is stabilized   (I realize there is some overlap, but the basic model is true.)  And this drives a natural development and marketing cycle that tends to be somewhere in the 1-2 year range between releases.  That does cause revenues to be very "lumpy" which might be a problem for some companies.
 
With the model that Cake is trying to present, there wouldn't be such discretely defined release cycles and they surely hope to make the income less lumpy.  But modern software development still favors major releases, especially for products as complex as SONAR.  For them to make the subscriptions continuous beyond the first 12-month free period, they will have to do at least minor releases to the core product before that 12 months is up.  otherwise, people will correctly conclude that nothing really has changed and the subscription plan is just an opaque way to raise prices.
 
I take the company at their word that they really do want to change the actual pattern of delivery and this is not just a marketing tactic.  They have 12 months to demonstrate that.

Hello
 
In Sonar Platinum is Additive Drums 2 the full version that can be used in other Daws, or is it tied to Sonar only?
 
Thanks.
 
Some great new features BTW........nice job Bakers.
 
 

TabSel
I still need to know the bug fix policy.

So, say, for example, just before my subscription ends, there would be a a feature rolled out that was announced long before and I'm eagerly awaiting. Now, a major bug in this new feature slipped through preventing the new feature to work at all. A hot fix will be announced, my subscription ends, the hot fix gets roled.

What about warranty here?
I paid with my subscription for this new feature, but it doesn't work until fixed.
I'm not entitled to the fix, as I'm no member anymore.

How is this handled please?

What about other bugs which get fixed along the way after my subscription has ended?
I'm happy to subscribe in order to get new features, refinements and such.
But afai understand, there have to be a warranty period, for the product as a whole, and for new features and patches in particular that get rolled out?

Please clarify.

Thank you

This question has been asked several ways now, but not answered yet.  We really do want to know :)