![]() |
![]() |
![]()
Post
#1
|
|
![]() Newbie ![]() Group: Members Posts: 3 Joined: 21-July 13 Member No.: 13,127 ![]() |
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? |
|
|
![]() |
![]()
Post
#2
|
|
![]() Newbie ![]() Group: Members Posts: 3 Joined: 21-July 13 Member No.: 13,127 ![]() |
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? 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... |
|
|
![]()
Post
#3
|
|
Newbie ![]() Group: Members Posts: 2 Joined: 1-September 13 Member No.: 13,437 ![]() |
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... 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. ![]() |
|
|
![]()
Post
#4
|
|
Newbie ![]() Group: Members Posts: 2 Joined: 5-December 13 Member No.: 14,412 ![]() |
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. ![]() 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..... -------------------- www.opusproductions.com
www.so-audio.com |
|
|
![]() ![]() |
Lo-Fi Version | Time is now: 5th July 2025 - 01:56 AM |