Please give us the option to opt out of all 3rd part services and goods from Cakewalk Command Centre

but, if that 3rd party thing is a prerequisite for some functionality (eg, meodyne for ara, etc) there should be some clear indication/notification of this somehow somewhere

Bippety bumpety boo....

+1

Voted 5*
Trying to keep my system as slimlined and streamlined as possible!

Edit:doublepost

Voted +1

I agree because otherwise we are forced to trust all companies that cakewalk trusts.

There were technical reasons we did that for this release. This has been discussed to death already in other threads. 
gswitz, Cakewalk has always had 3rd party components for decades now - how far can you take this? Don't install Izotope radius, POWr dither, and other DSP thats used in SONAR? How about the VST sdk itself - thats all third party code and from a competitor to boot :-P
 
Anyway having said that, we are experimenting with a different approach that we are testing, that should greatly alleviate this for the next update. This is assuming it works and we don't run into blocking issues.
1. At install time from C3, SONAR will now only download the landr component but will NOT install it.
2. This happens exactly once. i.e subsequent updates will not re-download if nothing has changed.
 
3. The actual Landr install now happens dynamically when the user chooses to export to Landr. i.e. a prompt is thrown and the Landr installer is run. After installation the file is uploaded to Landr.
 
The net effect is that users who aren't interested in using the service will not have Landr installed.

boy, that's the very last plugin i would ever want in a sonar product.
 
color me sad.