SPLAT update with command center is too cumbersome

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

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.

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

Willy Jones [Cakewalk]
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. 

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.

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?

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.

sven450
It is pretty clear that Cakewalk is aware and is attempting to resolve these issues.  How long they will take or how many they can fix at once is something users don't know and on which speculation is futile and counter-productive.
 
Sarcastic comments like "What is so complicated about that?" and "I fail to see what is so complicated about this" very clearly shows the truth:  we are not Cakewalk programmers, and we do not understand how difficult or time consuming it is to do these things.  To assume they are a simple matter to fix over lunch is ludicrous.  Unless you are a Baker, and helped develop Platinum, then there is no way to know exactly "what is so complicated".  
 
I think it is safe to assume THEY know how complicated these things are, and are working to fix them.

1) All the installers may need to be repackaged. There are a lot of packages.

2) You will need to add logic to read registry values so the CCC know where everything is installed, see next points.

3) The current packages may have different logic when storing file paths etc, the clear thing to do would be to adopt some sort of standard logic rather than write bucket loads of code to accommodate every scenario, that would be time consuming and increase development time/allow more scope for bugs.

4) What about existing installs? What happens when you try to install something that's already installed elsewhere maybe a different path specified... how will that be handled?

5) It will need to be tested, what happens if the install fails or runs out of disk space, or there is a permissions or the storage is offline... how does that get reported back to the CCC afterwards?

6) There are probably other issues that may take priority over the CCC that we don't know about... How do you allocate resources when they are limited?