I kinda like CCC. yeah its time consuming , but what I do like is that they put the videos in the command center for easy viewing, what would be nice is ,  more variety of videos perhaps a new video containing whats going on in your new update. I find it the perfect time to view while waiting.. A fantastic Idea , just hope the bakers update them ..

Then post a thread in the enhancements forum (if there isn't one already) and get voting!

Splat
However to say Cakewalk staffers aren't aware of the issues or enhancements needed for the CCC, you've got to be joking!

 
You must have misread my post. I was saying that they must be aware of these issues by now.
 

I have absolutely no doubt Willy is sincere when he says Cakewalk pays attention to the features request forum. The real frustration is that you want the enhancements now.... unfortunately Rome wasn't built in a day and making software and then testing it can often take longer... So give 'em a chance.

 
Nobody is expecting CW to fix these issues overnight, but for some reason CW completely ignores requests to acknowledge these issues (some severe, like no way to specify install locations), and to provide some indication that they plan to fix these issues. The few times CW does give some reply, it seems it was the 1st time they ever heard of it (see Willy's reply above), which from all indications appears to be the most complained about new feature in the Platinum release.
 

And too right if you aren't posting enhancements in the enhancements forum don't expect Cakewalk to ever implement it any time soon.

I think you should re-read my entire post carefully. There I mentioned that these issues have been posted about in the FR forum. Where did you get the idea from that they weren't already posted in the FR forum?

Splat
Then post a thread in the enhancements forum (if there isn't one already) and get voting!

It has been done a long time ago already. See here, here and here. Those are not the only threads about C3 in the FR forum.
 
Please stop making it sound as if we aren't doing our part in trying to make CW aware of this. After all of those threads in the FR forum, apparently it is still news to CW that there are issues with C3 when someone posts about it somewhere else. Does my original post in this thread make more sense now?
 
EDIT: To clarify...
 
Willy said:

Any chance I can entice you guys to make a thread in the feature request forum?

 
Then I said:

There are already threads about the multiple C3 issues in the feature request forum. I really don't think it makes a difference whether issues are posted there or here, since it seems they will be equally ignored.

 
...which you took offense with. But then I mentioned just 3 of the multiple threads in the FR forum:

It has been done a long time ago already. See here, here and here. Those are not the only threads about C3 in the FR forum.

 
So does that clarify my point, and that no matter where these things are posted, they will get equally ignored?

Yeah sorry I misread "And I'm sorry Willy but I don't buy for a second that CW isn't already intimately aware of these issues," I totally agree of course they are..
 
Still if there are three threads in the enhancement forums somebody should merge them (assuming they are exactly the same???) and people should get voting....
 
I wouldn't be surprised it if will take several months before we see CCC enhancements it won't be quick to do and esp to test. Hard to speculate anyway as I have no idea what stage they are at of course.

Ah ok

So we agree (my point still remains, however I was wrong to disagree with you, we mostly seem to agree), my point is that at the next triage meeting they might/will probably be looking at stats down the enhancements forum. Also a lot of people don't realise they can vote on the problem reports forum as well for bugs. It's probably all about metrics that they can show in meetings... 

I've been in situations myself where I've been a QA guy active in another software forums (as a mod and employee of another company), attended triage meetings with developers, and all they looked at is stats rather than what the community is saying (often the stats did not reflect the same thing). It was extremely frustrating for me as I believed I had a good idea what the community wanted and needed (it was pretty obvious). What forums posters might not understand is that developers and managers may not have time or resources to read every forum post so they turn to stats instead to convince others inside the company.

I would then turn to the community to get voting - and ... well... they mostly posted comments rather than vote - so they didn't get listened to....
 
(Edited several times sorry)...

I think we should give them a break its not been out long judge them in a year not in a month for what it's worth I think ur doing a great job & it will only get better 

Hi Steven,
 

There are already threads about the multiple C3 issues in the feature request forum. I really don't think it makes a difference whether issues are posted there or here, since it seems they will be equally ignored.

 
It makes a huge difference, we can run down the feature request forum and get focused, actionable, constructive feedback and add it to our backlog in minutes. That cannot be said for the SONAR forum. 
 
If my intention was to simply ignore it - why would I bother posting in here at all? I'm pretty sure a staffer participation in a thread draws more, not less attention to the topic.
 
Because we do not reply to every single thread does not mean it's ignored. In many cases just because a user requests something doesn't mean its actionable or works for everybody. The whole point of a feature request forum is a venue where folks can discuss and develop a consensus on the best solution together. If you don't want to contribute to that conversation you're more than welcome to just drop a note to our support team directly with your request.
 

And I'm sorry Willy but I don't buy for a second that CW isn't already intimately aware of these issues, since IFAICT C3 seems to be the most complained about feature by far in the Platinum release. 

 
I never said that we were not aware of C3 issues. I asked for feedback to be consolidated into a single place. A place where we don't have to weed through pages of unrelated issues to get to the requests & ideas or problems. 
 

Also strange is how CW employees will comment on all sorts of things in threads until C3 is mentioned, at which point they all disappear. It's very weird really.

 
Your version of history is very interesting, I think you'll find that I participated in lots of C3 threads. Yes things get busy and I'll go dark on the forum at times, the forums are not my primary responsibility.
 
Anyway - I'm truly sorry I offended you so much by my request to put the feedback in a single place, in the future I won't do that and we can just cross our our fingers that someone finds it.
 
Back on topic to your specific requests, I'll illustrate exactly why discussion around these by users is valuable for us in designing C3.
 
Allow per-product install locations.
While I don't know exactly what you mean by per-product, I'm assuming you mean the ability to specify the install path. Can you elaborate how you'd like this to work, do you want a new button a context menu? How often do you think you'd use this option vs the default? There are about 30 design questions in this one - hearing what others think would be extremely helpful.
 
Detect already installed products, whether they were manually installed in default or non-default locations. All this info is in the registry, why can't it pick it up?
This is on our radar - but allow me to correct you. Not everything is in the registry - there is some work we need to do to a lot of our existing products to make everything actually be in the registry. 
 
Allow uninstalling of products. I used C3 to install D-Pro and Rapture, but wanted to uninstall them and install them manually somewhere not on my limited space C drive. To date, after asking multiple times in the forum, nobody can tell me how to uninstall Rapture and D-Pro. It can't be done from either C3 or Add/Remove Programs.
Most products can be uninstalled by right-clicking on the product name in the tree on the left. If it can't be uninstalled then our installer failed to drop the uninstall.exe. 
 
Show changes between updates.
When an update is available orange text appears and includes a clickable link. We haven't been using that heavily but again - these 4 words you have provided don't really tell us how you'd like it to work or what would help illustrate changes. Feedback and discussion around this would be great - how would you like to see changes presented? Do you read them all the time or just every now and again (IOW - should it be super prevalent or just available somewhere)?
 
Allow un-hiding of previously hidden products.
Yeah we can get on that one, would just a button in the settings page to unhide all products be enough or do you see a need to un-hide specific ones?
 
Allow the ability to select multiple products and have them all downloaded/installed in one go.
This is an area where use-case and better understanding can help us design something that makes the most sense. If you're going to use this once in a blue moon then maybe something like CTRL + clicking products in the tree and clicking install is enough. If you're going to use this every single time then we should find something that is more obvious/intuitive. 
 
 

Good post Willy.
 
I also hope you can get some attention to the with problem reports forum before it gets in too much of a mess..  I'm around, but I'm around less and I don't have the permissions like I used to have, so I rely on pestering forum hosts, and it's hard to tell what's fixed without CWBRN numbers. I'm worried that forum will become a mess (especially with the "problem" title that everybody is being misleaded by). There are certainly loads of frozen move notifications that can at least be deleted now and a load of threads that could be commented upon. When Cakewalk staffers say "reproducible" they often don't leave CWBRN numbers leaving the forum handbook process out in a limb. A load of threads in there are probably better off being troubleshooted in Sonar forums first (simply because of more eyeballs). Also implemented issues after left laying around making Sonar look more buggy than it is. If staff could be briefed and they could go through the threads that would be really cool...
 
Thanks..