Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> Version 4 Upgrade (x64) Not Working
soulone82
post Jul 21 2013, 08:08 PM
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?


Go to the top of the page
 
+Quote Post
orlandoX
post Aug 3 2013, 03:41 PM
Post #2


Newbie
*

Group: Members
Posts: 1
Joined: 3-August 13
Member No.: 13,282



I can confirm this :-(

Just installed my Integral Studio Pack V4 (Win7 64bit) and Reaper doesn't recognize it.
Go to the top of the page
 
+Quote Post
Nick
post Aug 7 2013, 04:41 PM
Post #3


Staff
***

Group: Team
Posts: 615
Joined: 19-June 12
From: Montreal - CA
Member No.: 11,576



QUOTE (orlandoX @ Aug 3 2013, 04:41 PM) *
I can confirm this :-(

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


Hello orlandoX,

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

Should have an answer soon.

Best Regards,

Nick
Go to the top of the page
 
+Quote Post
soulone82
post Aug 22 2013, 06:48 PM
Post #4


Newbie
*

Group: Members
Posts: 3
Joined: 21-July 13
Member No.: 13,127



QUOTE (soulone82 @ Jul 21 2013, 09: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?


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...
Go to the top of the page
 
+Quote Post
rofman
post Sep 1 2013, 03:14 PM
Post #5


Newbie
*

Group: Members
Posts: 2
Joined: 1-September 13
Member No.: 13,437



QUOTE (soulone82 @ Aug 22 2013, 07: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...

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.
sad.gif
Go to the top of the page
 
+Quote Post
neilwilkes
post Dec 5 2013, 10:09 AM
Post #6


Newbie
*

Group: Members
Posts: 2
Joined: 5-December 13
Member No.: 14,412



QUOTE (rofman @ Sep 1 2013, 02: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.
sad.gif


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
Go to the top of the page
 
+Quote Post
radio12
post Dec 5 2013, 03:59 PM
Post #7


Newbie
*

Group: Members
Posts: 2
Joined: 5-December 13
Member No.: 14,419



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.
Go to the top of the page
 
+Quote Post
endlessblue
post Dec 5 2013, 10:04 PM
Post #8


Newbie
*

Group: Members
Posts: 2
Joined: 5-December 13
From: San Marcos - US
Member No.: 14,421



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.

This post has been edited by endlessblue: Dec 5 2013, 10:07 PM
Go to the top of the page
 
+Quote Post
endlessblue
post Dec 6 2013, 01:08 AM
Post #9


Newbie
*

Group: Members
Posts: 2
Joined: 5-December 13
From: San Marcos - US
Member No.: 14,421



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.
Go to the top of the page
 
+Quote Post
rofman
post Jan 2 2014, 05:38 PM
Post #10


Newbie
*

Group: Members
Posts: 2
Joined: 1-September 13
Member No.: 13,437



QUOTE (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.


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
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 

Lo-Fi Version Time is now: 28th March 2024 - 09:59 AM