I'm also having problems with Magnetic (1 and 2) and Echoes. 

They are in the right folders but never show up in Sonar's plug-in menu. This started after I got the Integral Studio upgrade - Magnetic and Echoes worked fine prior to this!

Just got the latest suggestion from Nomad which I'll pass along for anyone else having this problem.

They say to uninstall ALL Nomad plugs (program files/nomad factory/uninstall)
and then download the latest installer and re-install all of them.

They also said I (you) should NOT have to re-authorize.  We'll see.  Would sure hate to lose my original Magnetic (it's working fine now).  Ahhh technology!

Roby,
Thanks for that.

Giannas,
Reinstall the original Magnetic and Echoes (if you still have the original install files) to see if its the new install, or the C++ install, that is the core of the problem.

Tom

Yea Roby, ol pal, I fiddled with that too.  Don't know why Magnetic and Magnetic II would be so different in their Sonar VST profiles.  Bet something's up with that.  But my fiddling...like yours...didn't make a difference. 

Here's what happened when I followed Nomad's suggestion to just uninstall ALL my Nomad plugs and then download and re-install from the latest 64bit installer.  Now my Magnetic, Magnetic II and Echoes ALL don't scan or load at all AND my British Bundle runs only in demo mode.  Before everything except Magnetic II was working so I've actually gone backwards with their advice.  My Studio Channell sc226, my Liquid Bundle and my Analog Mastering Bundle work fine. 

I'm sure this will all get worked out and I can't really gripe at the prices I paid for all this BUT it sure would be nice if something just worked right first time...everytime.  I'll keep ya posted.

Well, I followed th latest suggestion frm NF which was to temporarily MOVE the .dll files up to the VST folder and rescan. No love. At all. I wish I could even begin to understand exactly what you did Jon...and I'd Try that too. But I don't. Ignorant cuss that I am. Do you have a step by step you could hip me to?

yorolpal


Well, I followed th latest suggestion frm NF which was to temporarily MOVE the .dll files up to the VST folder and rescan. No love. At all. I wish I could even begin to understand exactly what you did Jon...and I'd Try that too. But I don't. Ignorant cuss that I am. Do you have a step by step you could hip me to?

Well I did pretty much outline what I did above.

I don't recommend anyone else try it as like I say NF wouldn't be the first people to wrongly tie in an application to a specific C++ library so doing what I did may break something else.

But if you take that caveat onboard and make sure you have a disk image to fall back to in that event here goes.

1/ First in Control Panel in W7 select 'Programs and Features'.

2/ Uninstall any instances of 'Microsoft Visual C++ 2005 Redistributable' and 'Microsoft Visual C++ 2005 Redistributable (x64)'

3/ While you are here also uninstall any NF plug-in installers that you may already have showing.

4/ Also delete any Nomad Factory folders in your DAWs VST scan paths, also delete any Nomad Factory folders in 'Program Files' and 'Program Files (x86).

5/ Probably a good idea just to reboot at this point to clear out any lingering references to the uninstalled libraries.

6/ Install the 32 bit NF installers to whatever path your 32 bit plug-ins go in.  This should be somewhere within your 'Program Files (x86)' folder and in a subfolder you have set your 32 bit DAW to scan.

7/ Do the same with the 64 bit NF installer these should go somewhere within your 'Program Files' folder and again in subfolder you have set your 64 bit DAW to scan.

8/  This may have been enough to get the job done so fire up the DAW scan the folder and see if the offending plugs load.  If they do all that is required it to re-authorize if necessary.  If they don't...
 
9/ Download and install these in this order.

http://www.microsoft.com/...n/details.aspx?id=3387
http://www.microsoft.com/...n/details.aspx?id=5638
http://www.microsoft.com/.../details.aspx?id=21254
http://www.microsoft.com/.../details.aspx?id=14431

That will ensure that you have both 32 bit and 64 recognized versions of the VC++ 2005 runtimes back on your system.

10/ Lastly if all this still hasn't yeilded the right result check this out.

http://support.microsoft.com/kb/927665/

Check all your drives to see if this .dll is lying in the root of one of them and put it back into place according to the instructions given.

11/ I got no more. Yell at Nomad Factory.

All I can say is it worked here on yesterdays installers but they seem to be changing installers without giving build references so there's no guarantee it will work on todays installers.

But I can categorically state the missing or unloadable VST problem that some (not all) are having are to do with building those offending VST's against specific VC++ 2005 runtimes.

Thanks so much Jon.  I'll copy all that and try if necessary.  I sincerely appreciate the time you took to spell it out for us dimbulbs:-)

Ok guys,i have done my test with Jonbouy's advices,but don't work.But the worst thing is that i have a Nomad Factory email that recommend me to change the dll location insade Cake vst folder!!!!It's the first test i did!!I told them that many guys are going crazy with their installer and many daw (Studio One too,kvr forum). Did you have more luck than me? Best. Roby

Jonbouy,
Thanks for all your help.
I did notice that drive and driver were italicized in the MS docs and subbed "C".
Same result (only it said "C:\Program"). I was in a hurry, never good.
Jonbouy mentioned:
But if you take that caveat onboard and make sure you have a disk image to fall back to in that event here goes.
Make an IMAGE BEFORE doing any of this gentlemen!
Like I said above I'm kind of over it, let Nomad sort it out.
Again Thanks Jonbouy!

Tom

Just for S&G (killing time waiting for the sun to come up) I went into Control Panel to see when all the Visual C++ 2005 stuff was installed.
The x86 was updated when I installed the Control Surface Plug for my FW-1884 (don't want that broke)
The x64 updates were done when I installed the Garratin Aria Player.
2008 2010 were done when I added IK's UA1176 and LA-2A emulations, Z3TA+2.
I guess my point here is Image, Image, Image and what's up with Nomad.
We all went nuts when X1 was a little buggy.
Just sayin'

Hi all,end of nightmare.The new installer is out and work fine!Magnetic 2 is awesome!Best.Roby

Yea Jon the email I got from them last night(!!) after I sent in another support request said that the installer now has a date so that you can tell if you have the latest. And it works for me now also. Magnetic, Magnetic II, and Echoes!!!

yorolpal


Can you just install the plugs you need (i.e. Echoes, Magnetic and Magnetic II)?? 

Install, Authorize then delete (or zip up) what you don't want.

Like with all the UAD stuff that installs I just zip up the entire folder contents, delete everything but the zip file and just pull out the ones I use.

Keeps the lists short and cuts down on scanning time.

Yup...same here.  Only even tho I emailed them several times about my specific problems (the fact, for instance, that my British Bundle was an earlier iLok purchase and that the only way it would run is to NOT uninstall it OR re-install the iLok only version in order for it to run, etc...) I only got the generic "uninstall and then reinstall all nomad plugins...no need to reauthorize" messages.  No matter.  I just did not uninstall the British Bundle and when the three "non-blacklisted" plugs said they would only run in demo mode only...I just reauthorized them with my existing key.  In any case running hot straight and normal again and WITH Magnetic II.  Haven't had a chance to put it through it's paces yet...but I'll keep ya posted, as per usual.  And "Wacky November" ain't even over yet!!!