BobF
No prob.  FWIW, CCC doesn't run on it's own.  It's purely On Demand so you don't have to worry about it sneaking around looking for pRon when you're not expecting it.
 
I do understand.  I held out for a really long time.

I just think it's an extra thing to manage/go wrong and I much prefer to do these things on my own. I like to organize and store my installers in my own way, pick and choose what goes where, etc and don't want to learn/manage a special program to install another program.
 
I'm also rather displeased with Cakewalk's push into this "App-y/cloudy/always online" world. I know they have kept it tame because they know us Sonarites are a curmudgeony lot but there does seem to be a lot of forceful nudging in that direction. I'm assuming this is at the insistence of the hyper modern new Gibson and their efforts to be cutting edge.
 
The Baker's though, from my experience, are hyper modern in that regard as well but are also practical old school programmers who understand the desire for hands on management of systems by those who don't want/need to be spoonfed.
 
It is partially because I simply do not like these types of systems but it is also very much a protest against them becoming the only option if one is to use the program. It is the type of thing that has made me avoid other programs in the past.
 
It's creeping up slowly into the NI/Adobe style distro/registration model and I think that will sorely damage the brand.
 
Aaaaaaaand we've gone back into ranto mode.
 
Sorry... it is important to me though.
 
Cheers.

Beep, the only time, and I mean ONLY time my machine is connected to the internet is when downloading updates for Sonar, and sometimes IK Multimedia/FXpansion

Bristol_Jonesey
Beep, the only time, and I mean ONLY time my machine is connected to the internet is when downloading updates for Sonar, and sometimes IK Multimedia/FXpansion

For sure and hopefully it will stay that way (but we gotta be pricks about it because the younger folks don't seem to care about such things as much).
 
All I need is
 
a) To be able to continue being able to download installer packages manually
 
b) Dates of when an installer package has had any changes, additions, updates to it
 
c) A description of what those changes, additions, updates were so I can decide whether to download/install them now, later or never.
 
I can handle it from there. Currently it's a matter of hunting things down on my system based on point versions, keeping elaborate notes and annoying you guys for extra info on specifics. Not very efficient.
 
Of course the "solution" is to succumb to the CCC but that has it's own issues and I don't particularly trust it to do exactly what I need it to... also I don't think the CCC provides the type of detail I am looking for anyway.
 
Then there is the matter of I don't want to encourage Cakewalk to think the CCC is something that can be made mandatory. They were good enough to allow "offline" installations and that is to be commended. They need to stick to that and make it an at least SEMI efficient experience.
 
Dates and descriptions on the installers would go a long way to that. Maybe some kind of tracker system in our accounts that puts a checkmark beside something we have already downloaded (and a date of when) would be helpful too. That way it is stored on site and we can see we have downloaded something already (that has not been altered/updated in the interim.
 
The focus has been on the CCC while the store accounts remain chaotic.
 
 
Anyway... everything has been installed now. I have absolutely no clue as to what exactly some of these vague installers did but it is done and I have a restore point setup in case something stupid happens.
 
I'm sure I'm gonna dig Lexington though... but fingers crossed.
 
Cheers.