@pwalpwal again check agile development. I wouldn't expect to see a full roadmap either consumers are not part of the development team. Consumers give feedback it's cakewalks jobs to listen. If they didn't want to listen they wouldn't respond to threads like these and they wouldn't send out surveys.

Splat, I'm well aware of agile development since I have used it in various projects I worked on (with both good and bad results). And I have said many times I like the new CW model and that it should work well when other people were complaining about it.
 
But this discussion is certainly getting circular.

Just one small point - isnt the sensible approach to just run an installation routine that asks for install paths, but fills in default values? *Everybody* is used to seeing this, and everyone knows that - if you're not sure, just stick with the default. OK, this means we don't have a "silent install" but everybody from complete beginner, to power user, is used to seeing this. Surely this wouldn't scare off new users who want to make music quickly.

Also, there was a comment (somewhere in this thread) that there isn't always necessarily a registry entry to indicate that a program has been installed or not. could I suggest that the CCC bakers add a registry entry for everything they need - when installing things?

I do think CW missed a few obvious things, but I'm also pretty sure that CCC get better, in time.
(I've asked for all these things already in the feature request forum btw)

Oh, one more thing - we also really need to be able to install soft synths and/or VST plugs individually rather than as a whole suite. Anybody who has upgraded any VST or VSTi to a "full" version, does not want to overwrite it with a "Cakewalk" version, as a dozen VSTs get installed in one batch.