Nomad Plugins - are these new, representing 2013?

Not at all impressed with these. They feel old. Not anything that contributes to a nice new X3 at all in my opinion. Strange plugins.  Not smooth or nice to operate. Feels like plugins from 5-10 years ago. What is this Nomad plugin package really? Sometimes it's not possible to have the meters showing left and right channels at the same time etc. Lot's of screen estate taken up by displaying silly big poor graphics of blue tubes for no good reason etc... Whilst the text is tiny, tiny...
 
I think those old Sonitus (although not exactly the same functions of course) are much better designed and much more pleasent to use. They still represent good professional serious plugins. This Nomad package feels cheap.
 
Can we uninstall this Nomad package so that it's not accidentally used in a project? If so, how?
 
Thomas

ThomasEngineer
 
Can we uninstall this Nomad package so that it's not accidentally used in a project? If so, how?
 

 
I "assume" they are in a vst folder somewhere named nomad perhaps ? just move that elsewhere and rescan OR do a custom install in sonar, and you should have the option to not include em... don't have x3 , so can't be specific.
 

If you do not want to use the plugins just use the plugin manager to just include the plugins you want. 
 
I like the Nomad plugins and have used them on a lot of projects.

No they are not new. Several years old in fact. IMHO they are not the best but certainly not the worst.
 
I'm curious, how does one "accidentally" use them in a project? 

Another Troll thread from long time members.

How can a plug-in accidentally get used?
 
Since they are installed as part of the SONAR installer, you have a few removal options. Delete them. Disable them in Plug-in manager. Use a custom plug-in layout. Move them out of the VST scan path like was mentioned above. Do a clean re-install of X3, using the advanced install option, do not install them.

I sometimes accidentally apply a low pass filter @ 100Hz across the master bus. It takes me ages to rebuild the whole project from scratch. I wish there was some kind of safeguard in place to stop me doing this. 

With "accidentally" I mean the following:
 
Anything is OK if it sounds fine and everyone are happy. Sometimes, depending on the work you do in a studio, there has to be some "standards" etc. If everyone invents new things all the time and send projects here and there etc. it can lead to confusion and problems. Let's say someone thinks a Nomad de-esser is fine and we already have the Fabfilters De-esser and use them in a certain way and our client has the FF's too etc. then you may chose to "prevent" someone from "accidentally" using Nomads de-esser...
 
Nothing strange about it. Just being practical and trying to avoid confusion and mistakes, that's all.
 
I didn't mean to a situation like if someone was leaning over to the right to grab a cup of coffee and then accidentally enabled the Nomad de-esser on track 18... ;)
 
Thanks for your replies...
Thomas

I'm old and I'm cool!

I think in defence of the OP he made a reasonable explanation just a few posts earlier.  Maybe it's the choice of word "accident" that is confusing, but what I believe he is referring to is maintaining a standard set of plugins in a studio environment that are consistent with what a client is using.  That way they can safely exchange project files without either party dealing with a "missing plug-in" issue.  
 
Of course, one doesn't literally "accidentally" use the new plug, because clearly there is some intent in selecting it.  But if you had many people working at a studio then you might want to avoid the situation of having someone select a plug-in by removing it completely.  I get that.