Printable Version of Topic

Posted by: soulone82 Jul 21 2013, 08:08 PM

After upgrading my Nomad Factory plug-ins to version 4.0 (x64), both DAWs (REAPER x64 & Studio One x64) can´t seem to find the plug-ins.

The strange thing is, all of the Nomad Factory plug-in .dll files are in the appropriate folder on my harddrive. All licenses are stored in the my documents folder (win 7). But I can´t get REAPER or Studio One to see the plug-ins in the fx browsers.
I have cleared the plug-in cache, re-scanned my plug-ins several times and i have even deleted the file reaper-vstplugins64.ini.

Still no luck.

Can anyone confirm this?

Posted by: orlandoX Aug 3 2013, 03:41 PM

I can confirm this :-(

Just installed my Integral Studio Pack V4 (Win7 64bit) and Reaper doesn't recognize it.

Posted by: Nick Aug 7 2013, 04:41 PM

Hello orlandoX,

I have sent a note to Nomad Factory to see what they think.

Should have an answer soon.

Best Regards,

Nick

Posted by: soulone82 Aug 22 2013, 06:48 PM

just a heads-up that nomad factory wasn´t able to reproduce the problem i am having. so unfortunately i can not use the latest update for the 9 products i own.

guess it´s time to say goodbye to nomad factory...

Posted by: rofman Sep 1 2013, 03:14 PM

Hello,

I ran into the same problem (W7 pro 64). After upgrading to v4 plugins are no longer seen as valid in any DAW. Replacing them for the v3 plugins again and these work fine. I have no idea what causes this problem with the v4 plugins but seems system . I thik that at Nomad they also dont know what cause this strange behavior.

Posted by: neilwilkes Dec 5 2013, 10:09 AM

I've not tried this update as yet (will give it a go) so need to ask a couple of things:
1 - What plugs are missing?
2 - Did they get name changes?
3 - Has the DAW plugin scan files been cleared/deleted? (In Cubendo, this lives in C:/Users/<username>/AppData/roaming/Steinberg/<Cubendo>/ and the file names are "vstpluginfo.xml" (or vstpluginfo2.xml) and also "vst2xpluginsNuendo.xml" (or cubase) and maybe also the blacklist.
The purpose here is to force a full rescan, which often helps out - especially when a name has changed, or similar.
The downside is that all VST2 paths will be lost, and will have to get re-added in the relevant place.

Worth a try.....

Posted by: radio12 Dec 5 2013, 03:59 PM

Hi,
it might have something to do with the c++ runtime libraries, i bought Magnetic, echoes and cosmos yesterday and they did not work in Reaper 64, after updating with the All in One Runtimes, (a collection of libraries) they showed up. I guess its because the 64 Versions only instal the 64 Versions of the runtime libraries.

Posted by: endlessblue Dec 5 2013, 10:04 PM

Same exact problem here with the 32-bit versions of the plug-ins and REAPER. v3 works great, v4 doesn't. I'll give the All-in-one-Runtimes a whirl and report back.

One other note, MAGMA works fine. It's just all the other plugs.

Posted by: endlessblue Dec 6 2013, 01:08 AM

Okay, that did the trick. I think the installer is missing a redistrib. I used the All-in-One-Runtime installer and installed:

.NET Framework 3.5
.NET Framework 4.0
Visual C++ Runtimes 2001-2013
Microsoft DirectX 9c runtimes

Worked like a champ on next run of REAPER, all plugins detected.

Posted by: rofman Jan 2 2014, 05:38 PM

What is the OS you are using?
My DAW has W7 ultimate x64. As far as I know .NET Framework 3.5 is part of W7 OS. I recently updated .NET Framework 4.0
to 4.5.1. I have all Visual C++ Runtimes installed and I think it runs Microsoft DirectX 11.
The v4 plugins are not recognized as valid plugins, so the question is what is missing on my system?

Rob