Anderton

yevster
Here it is:
https://www.steinberg.net...grace_period_info.html
When a copy of Cubase 7.5 is activated, one automatically gets a license for 8 and a downloadable update. My original Cubase purchase was through a grace period and that's exactly how it went. MF seems to be without a clue :)

I clicked on that link. It's from over a year ago, and about a grace period for those buying Cubase 7 and being able to upgrade to 7.5. It doesn't say anything about Cubase 8, and I still don't see a link where you can buy Cubase 8 Pro now from GC or MF for $400. If you want it now the only option I see is paying $550 from a company like Sweetwater.

My bad. https://www.steinberg.net...grace_period_info.html

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

orhanproject
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...
Thanks

Completely agree on both.  

 

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.
 
 
 

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 stevestrummerUK and neirbod

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

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

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

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.
 
 

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.