I have a suggestion:
 
1) Threads announcing a new release should be read-only to forum members. For offical cakewalk announcements only. Forumites can always start their own threads to complain or praise an aspect of the "monthly" release.
 
2) By all means have a second thread called "shooting the sh*t about the Yountville Release", but document that it will be locked once the Zealandia Release comes out.
 
...or something like that. 

mettelus
Unfortunately, these threads end up descending into this quite often from both sides and totally detract from the main points which were originally made. I personally could care less about LANDR, but I do care very much care about CW's direction and the single comment made of packaging a third party program into SONAR. This release in general has been an eye opener, and as it is the last for my current year it has also made me take an objective look at the "past year in review," as it were. As that is my preference, I won't go into details of the good and the bad, but I did realize how "old school" I really am.
 
"Good faith" with a brand only extends so far, and the reality of gapping membership for months or even years is not an issue for me as I want product in hand, not hope. A quick pass on the features forum solidified this with the reality that the core SONAR program can just as easily be purchased outright when the ones I am concerned about materialize, rather than invest in the time between now and then - and in reality lose nothing as the core program is cumulative. I do not feel CW is listening to their customers all that much TBH, which is a shame since when new users become more savvy, they are going to see the same (legacy) issues, it is only a matter of time.

 
Apparently the installer issue is being reviewed and our voices were heard amongst this other rabble. Don't lose faith yet.
 
Cheers, bud.

i dont get the problem. 50megs and u never use it, doesnt intrude on normal activities. crazy times...

stickman393
1) Threads announcing a new release should be read-only to forum members. For offical cakewalk announcements only. Forumites can always start their own threads to complain or praise an aspect of the "monthly" release.

 
A great idea.  This thread could be reduced to the very first post and all would be well.
 
As usual, Andrew's comments are a breath of sanity.  The price to pay for receptiveness and tolerance is that they will be at times abused.  Cakewalk's management of these forums is outstanding.

kennywtelejazz
Why don't you go over to Bob K..."s house and wash the LANDR off his truck .
 
 
Kenny
 

Hahahaha.... good one . Made my day :-))
 

mettelus

Unfortunately, these threads end up descending into this quite often from both sides and totally detract from the main points which were originally made. I personally could care less about LANDR, but I do care very much care about CW's direction and the single comment made of packaging a third party program into SONAR. This release in general has been an eye opener, and as it is the last for my current year it has also made me take an objective look at the "past year in review," as it were.

Agreed. It always ends up people being on one side or another whilst the real problem is overlooked.
 
These are the points being made here.
i) LANDR is great
ii) LANDR is crap
iii) LANDR installation is crap.
 
I could not care less about the first two points, if you don't want LANDR try not to install it, if you like it install it. The only real issue is the half baked installation. If this is "by design" I can only think it just was not thought about for very long, or somehow LANDR suppliers insisted it should be part of the main package.
 
Cakewalk has been gracious enough to acknowledge the issue, others seem to have completely overlooked as they probably haven't read the thread properly. Let's hope they actually do something here...

Andrew Rossa [Cakewalk]
And we understand that LANDR is a polarizing topic coupled with some issues on how it gets installed.

 
These are the current issues as it now stands.
 
# If you don't want LANDR the only way not to install is to untick the option in verbose mode, hopefully you will get there is you select the right options. As most people probably won't know about verbose mode I assume they will just install it anyway.
# Next month if you forget to run verbose mode - will it install LANDR or just leave the preferences as it was last month (say if it was not installed), this is NOT CLEAR and I suspect not thought out.
# If somebody installs Sonar without verbose mode, and decides to remove LANDR, if they run the installation again and deselect the option - will it uninstall? Or won't it?
# Why oh why oh why didn't Cakewalk supply a separate package like Melodyne and Drum Replacer?
# If Cakewalk does supply a separate package next month, how would people uninstall if they it already installed the previous month? I assume they would have to install the LANDR separate package and then remove it? PITA if so. Hopefully by default it will autoremoved it so it can be installed later via separate package, by users choice.
 
The LANDR package has just added to the legacy mess, the main package contains legacy plugins, directx plugins, 32 bit plugins, third party plugins (inc now LANDR), instrument VST's. Please just take this all out of the main package and supply separate packages. I thought that the reason why all this stayed there is because of Cakewalk has not have had the resources to do the work, that is something I understand. Now LANDR has just been chucked in willy nilly I no longer understand or want to tolerate it.
 
Hope Cakewalk clears up this mess next month , and my point will be distant history. Please abstract the main program into multiple packages, and please make the verbose install of the main package much simpler. I don't understand why I am prompted for a VST path that gets ignored for instance. Sonar Verbose upgrades are a bit crap anyway and reminds me of computing in the 90's. Please sort it out.
 
Thanks for listening.

And how many alternate identities do you have FanCake? 
 
I believe you are mistaken about what is bundled into the main Sonar package. In the CCC the plug ins are divided into different packages as are several other bundled bits. You have the option to install the core Sonar only, update everything or simply pick what you want to install/update. If there is content that you don't want to use or even see, then you can hide that component. Since LANDR is an export option from the main program it seems logical that it was put in the core download. Options to change this have been presented and I used them on my update.
 
Smooth sailing, no worries.

ampfixer

And how many alternate identities do you have FanCake?

I believe you are mistaken about what is bundled into the main Sonar package. In the CCC the plug ins are divided into different packages as are several other bundled bits. You have the option to install the core Sonar only, update everything or simply pick what you want to install/update. If there is content that you don't want to use or even see, then you can hide that component. Since LANDR is an export option from the main program it seems logical that it was put in the core download. Options to change this have been presented and I used them on my update.

Smooth sailing, no worries.

** Since LANDR is an export option from the main program it seems logical that it was put in the core download. **
 
That seems rather warped logic, anybody could make exactly the same argument about Melodyne and Drum replacer. You appear think export and regionFX should be treated differently when it comes to packaging? In other words where the functionality is in the user interface should dictate where the package is installed. Well I entirely disagree, it should be what the functionality is, give users a clear choice, make installation and upgrade as simple as possible every month, avoiding package bloat and reliance on verbose mode for upgrading every month. And I was not the first person who made this point in the thread.
 
I am obviously fully aware of the difference between a separate package with it's own installer, and a custom install within the main package. It's pretty clear if you had fully read my #bullets. I will not repeat them.
 
Rather than question my points, which would have made for a happy debate, you would instead prefer to ignore them, counteract with your rather weak logic, and then top it with a conspiracy theory to discredit me.  Well I don't have time to waste when it comes to rudeness and silliness. Go and have an argument somewhere else please.

Cakewalk has already acknowledged the install issues. That's good enough for me.
 

Andrew Rossa [Cakewalk]
So I am asking that we keep it civil and constructive - and most important be kind to your fellow SONAR users. We're all in this together :)

I could not agree more. Roll on next month...

backwoods
i dont get the problem. 50megs and u never use it, doesnt intrude on normal activities. crazy times...

Yeah, no kidding. I don't think this is any different than the SoundCloud and YouTube options - just another entry in the drop-down list. I don't remember anybody complaining about those. And in this day and age, why wouldn't Cakewalk enable integration to cloud services?

groovey1
I don't think this is any different than the SoundCloud and YouTube options -

Well, it is a little different.
 
1) Some people are concerned about the considerable extra download size that all users will have to accept for all releases in the future.  If that were the only issue, I'd say "get over it".
2) Some people wish that this had been packaged like most other things, giving the user an easy way of not installing it.  Again, seems like a really good idea, but not the end of the world either.
3) Some people are concerned that, unlike Soundcloud, it appears there is a revenue sharing model at work here.  I think this is a more serious issue, more akin to selling a person's private information without permission.  It would have been a lot better for Cakewalk to be up front about that, as in: "Cakewalk and Landr are partnering to bring a new mastering option to Sonar users ..."
4) Some people are concerned that the offering is not priced rationally.
5) But mostly the storm is caused by what comes across as a hard sell for a service that seems hyped beyond its actual capabilities.
 
This food fight doesn't really do much good for anybody.  My suggestion would be for Cakewalk to agree to take these concerns under consideration, perhaps with some better positions in the March release, and just put this thread to a merciful end.