Edit :
Original title : Did Cake make a mistake on Nomad licencing control ??
 
** Does not applies if you never own any Nomad Blue Tube plugs (Blue Tube plugs are also bundled with Nomad Integral Studio III pack).
 
** This is only a problem if you use Nomad Blue Tube plugs (that is _NOT_ from X3 Studio/Pro) on multiple DAWs (including 8.5, X1, X2 and X3 basic).
 
** Nomad Blue Tube plugs from X3 Studio/Pro can only function in within X3 Studio/Pro as licensed.
 
** Problem occurs when you install X3 Studio/Pro version's of Nomad Blue Tube on top of your existing Nomad Factory vst folder which happens to be the Cakewalk default vstplugins folder.
 
** Suspected folder in question C:\Program Files\Cakewalk\Vstplugins\Nomad Factory\
NOTE : This may not be a problem if your original (none Cakewalk) Nomad plugs are installed elsewhere.
 
** Solution : Do a custom X3 Studio / Pro installation and do not select the Blue Tube plugs.
 
** If you come this far, you may only realized now, such as you've already install X3 Studio / Pro with Cakewalk licensed only Blue Tube plugs on top of your existing Nomad Factory folder. If that happens, simply re-install your original Nomad plugs and re-authorized it. If this doesn't work, delete the whole Nomad Factory folder, and re-install your original Nomad plugs. If that still doesn't work, you may have to un-install X3 Pro, remove Nomad Factory vst folder, install your original Nomad, then re-install X3 Studio / Pro with custom installation and de-select the Blue Tube plugs.
 
NOTE : Current Nomad installer is version 4 (as in COSMOS addition), and there are some fixes on the Nomad plugs as well.
 
NOTE : In case you've removed the Nomad Factory folder, don't forget your COSMOS plug too (if you've purchased them too recently).
----------------------------------------------------------------edit done
I've purchased my Nomad Intergral Studio Pack 3 in Dec 2011,
 
http://www.nomadfactory.com/products/isp/
 
which includes the Blue Tube effects pack
 
http://www.nomadfactory.com/products/bt_effects/index.html
 
And now it refused to work ? If I remember correctly, I've used it till X3 basic patch B without any issue.
 
Now, I've upgraded to X3d basic, as well as X3d Pro. I'm tracking using X3 basic today, and a message appears so say the internal audio will be by pass.

I'd strongly recommend for this type of problem to contact cakewalk support. We can guess and make all sorts of suggestions but if there's a work around to apply I'd say it will only come from the horses mouth.

Thanks, I will do so.
 
Was thinking if any X3 basic user also having Nomad encounter this problem after updating to the c/d patch.
 
Or could it be that my Nomad installation was updated with the control during my other X3 Pro upgrade.

It could be that but I can't think of a way to fix it short of the order in which they are installed so you don't overwrite files from your authorised plugins.

Actually I just had a thought.

If you uninstalled Sonar X3 producer and your licenced Nomad plugins.
When reinstalling sonar, don't install the Nomad plugins (tied to X3Prod). Then reinstall your licensed Nomad plugins.maybe that would work.

Thanks again Mike. I'll do that after completing my current project.. I'll just switch to Pro for now.. I'm liking to track with the Basic.. feels a little lighter.
 
Just wrote to Cake too.
 
Shall update the outcome.. depends when they're write back. Should be fine for now, with X3 Pro.

Just an update.
 
1. I've completely uninstalled X3 Pro.
2. Test running X3 basic, Nomad plugs still there, with the same licensing control.
3. Proceed to manually delete the whole Nomad vst folder.
4. Re-install Nomad Integral Studio III, authorized it using the previous authorization file that I saved.
NOTE : That is one reason off line authorization is better - in case Nomad keep tracks how many time you're allowed to authorize ?
5. Run X3 Basic - Nomad is working great.
 
I'll do the X3 Pro installation later and report back.

When your re-install X3pro, select "custom" installation.
Uncheck the Nomad plugs, that will leave the "authorized" plugs intact.
My guess is, and I probably did this myself, x3 "overwrote" the existing Nomad install.
Haven't tried to run them in X1 or 2 since the x3 install.
Tom

Thanks Tom.
 
I'll do that soon, just lacking of time for uninstall/install.. I'm working with X3 basic for now.
 
I've just send a feature request so that plugs that is only licensed for Cakewalk product is stored into a separate folder such as "Cakewalk Licensed Nomad Factory" and not to overwrite existing folder (unchecked).
 
I believed many simply install our plugs into ..\cakewalk\vstplugins folder since Sonar is our main DAW, then point others (Reaper, etc..) to this location, instead of the standard ..\steingberg\vstplugins folder.

Well I believe the default paths Sonar provide are not convenient. In my view VST's should not be installed inside the PROGRAM FILES folder as this can lead to permissions issues (meaning you always need to run Sonar as Admin). I have moved my plugins elsewhere and have organised then into specific folders. Every time I install or update plugins I always change the default folder paths. The only code I get permissions issues with now is Pentagon, one of these days I'll grant the file itself admin rights.