|
|
|
05-23-2018, 01:57 AM
|
#1
|
Human being with feelings
Join Date: May 2010
Posts: 31
|
Reaper Sees 64-bit VST as 32-bit
Hi - I'm running the latest version of Reaper. I have Battery 4 and it keeps crashing whenever I offline it or close the floating window.
The .dll is 64-bit architecture (verified in Dependency Walker and Windows properties), but for some reason Reaper sees it as x86 and opens it in a bridged window.
I think this may be causing the problem - but why is Reaper doing this, and is there any way to force it to open it as a 64-bit VST?
|
|
|
05-23-2018, 04:38 AM
|
#2
|
Human being with feelings
Join Date: Sep 2009
Posts: 863
|
Quote:
Originally Posted by swichlicour
Hi - I'm running the latest version of Reaper. I have Battery 4 and it keeps crashing whenever I offline it or close the floating window.
The .dll is 64-bit architecture (verified in Dependency Walker and Windows properties), but for some reason Reaper sees it as x86 and opens it in a bridged window.
I think this may be causing the problem - but why is Reaper doing this, and is there any way to force it to open it as a 64-bit VST?
|
Native Instruments (from memory), always installs both 32 and 64 bit versions.
When Reaper scans VST locations, if it finds two .dll's with the same name, the last one wins. The order of scanning is set in preferences - Check that your 32 bit path comes first, then your 64 bit path. If you make any changes, you should clear the cache and re-scan.
If you only have a 64 bit vst path, or the path order is correct. Are you sure Reaper isn't loading the 64 bit version in bridged mode? Check in the FX browser, right-click Battery and choose an appropriate option (unbridged...)
Incidentally, Reaper can also bridge 64 bit plugins
|
|
|
05-23-2018, 05:11 AM
|
#3
|
Human being with feelings
Join Date: May 2010
Posts: 31
|
Quote:
Originally Posted by RobU
Native Instruments (from memory), always installs both 32 and 64 bit versions.
When Reaper scans VST locations, if it finds two .dll's with the same name, the last one wins. The order of scanning is set in preferences - Check that your 32 bit path comes first, then your 64 bit path. If you make any changes, you should clear the cache and re-scan.
If you only have a 64 bit vst path, or the path order is correct. Are you sure Reaper isn't loading the 64 bit version in bridged mode? Check in the FX browser, right-click Battery and choose an appropriate option (unbridged...)
Incidentally, Reaper can also bridge 64 bit plugins
|
Hmm. I think at least the bugginess has been fixed!
I had deleted the 32-bit .dll to make sure only the 64-bit version was being loaded.
But I've selected to run it as a dedicated process and although it's still bridging for some reason, now the Battery UI window says "(x64 bridged)".
Hopefully that's done the trick, thanks. Any idea why the 64-bit Reaper is bridging a 64-bit VST? I haven't asked it to...
|
|
|
05-23-2018, 05:48 AM
|
#4
|
Human being with feelings
Join Date: Sep 2009
Posts: 863
|
Quote:
Originally Posted by swichlicour
Hmm. I think at least the bugginess has been fixed!
I had deleted the 32-bit .dll to make sure only the 64-bit version was being loaded.
But I've selected to run it as a dedicated process and although it's still bridging for some reason, now the Battery UI window says "(x64 bridged)".
Hopefully that's done the trick, thanks. Any idea why the 64-bit Reaper is bridging a 64-bit VST? I haven't asked it to...
|
There's no need to run it as a dedicated process, Battery is quite stable in Reaper, for me anyway
Just a word of warning about deleting the 32 bit version, if you try to update Battery via Native Access (or whatever the old updater/installer was called), if it can't find the 32bit version, it will remove the plugin altogether.
I install all my unwanted 32bit stuff (NI, Melda, and a few others...), in a separate folder that is not scanned by Reaper.
|
|
|
05-23-2018, 06:00 AM
|
#5
|
Human being with feelings
Join Date: Feb 2009
Location: Nashville, TN
Posts: 209
|
I am also having this issue with Reaper and Native Instrument plugins, Battery, Absynth and Massive. All latest versions.
|
|
|
05-23-2018, 06:48 AM
|
#6
|
Human being with feelings
Join Date: Aug 2007
Location: Near Cambridge UK and Near Questembert, France
Posts: 22,754
|
Like switchlicour said,
"Check that your 32 bit path comes first, then your 64 bit path. If you make any changes, you should *****clear and re-scan****."
NOT just "re-scan"
Have fun!
__________________
Ici on parles Franglais
|
|
|
05-24-2018, 09:05 AM
|
#8
|
Human being with feelings
Join Date: Feb 2009
Location: Nashville, TN
Posts: 209
|
Quote:
Originally Posted by RobU
Native Instruments (from memory), always installs both 32 and 64 bit versions.
When Reaper scans VST locations, if it finds two .dll's with the same name, the last one wins. The order of scanning is set in preferences - Check that your 32 bit path comes first, then your 64 bit path. If you make any changes, you should clear the cache and re-scan.
|
Changing the order of path scans (32bit is now first) has fixed my issue. (NI should have different names for the two.)
Thanks!
|
|
|
04-27-2023, 12:38 AM
|
#9
|
Human being with feelings
Join Date: Mar 2023
Location: Poland
Posts: 35
|
Quote:
Originally Posted by RobU
When Reaper scans VST locations, if it finds two .dll's with the same name, the last one wins. The order of scanning is set in preferences - Check that your 32 bit path comes first
|
Thanks for the info.
But what if 32 and 64bit versions of the same plugin are both in the same folder?
I have Trash2 from Izotope and Reaper shows me only 32 version.
How can I find 64 version in Reaper nad force it over 32?
...and it looks like I have them booth in two different Izotope folders on my PC. Only makes it more confusing to me
Last edited by Wojtek Stecyszyn; 04-27-2023 at 01:20 AM.
|
|
|
04-27-2023, 02:51 AM
|
#10
|
Human being with feelings
Join Date: Sep 2008
Location: UK
Posts: 3,690
|
Quote:
Originally Posted by Wojtek Stecyszyn
Thanks for the info.
But what if 32 and 64bit versions of the same plugin are both in the same folder?
I have Trash2 from Izotope and Reaper shows me only 32 version.
How can I find 64 version in Reaper nad force it over 32?
...and it looks like I have them booth in two different Izotope folders on my PC. Only makes it more confusing to me
|
DO you even need 32 bit version? If not just uninstall it.
If you do then as said you need them to be in different scan paths and make sure the 64bit path is listed AFTER the 32bit path.
If they are both in the same folder or subfolders of the same folder you'll need top move one. For neatness you would usually install 64 bit to sub folders of Program Files and 32 bit to suns of Program Files (x86)
|
|
|
04-27-2023, 09:26 PM
|
#11
|
Human being with feelings
Join Date: Mar 2023
Location: Poland
Posts: 35
|
Quote:
Originally Posted by Stella645
DO you even need 32 bit version? If not just uninstall it
|
Hi
Yes I would like to keep 32 version because I've already excessively used it in some project and I dont want to loose my precious tweaks. So removing 32 version is rather poor option.
...or maybe someone could instruct me on how to replace 32 with 64 without loosing settings and rich web of automation? Btw it is Trash2 from Izotope, if it matters....
Quote:
Originally Posted by Stella645
If you do then as said you need them to be in different scan paths and make sure the 64bit path is listed AFTER the 32bit path.
If they are both in the same folder or subfolders of the same folder you'll need top move one. For neatness you would usually install 64 bit to sub folders of Program Files and 32 bit to suns of Program Files (x86)
|
But witch one to move? From witch of these two folders? Can you help me to distinguish 32 from 64?
Here are the paths:
C:\Program Files\Common Files\VST3
C:\Program Files (x86)\Common Files\VST3
Here how it looks like:
Last edited by Wojtek Stecyszyn; 04-27-2023 at 09:34 PM.
|
|
|
04-28-2023, 04:53 AM
|
#12
|
Human being with feelings
Join Date: Sep 2008
Location: UK
Posts: 3,690
|
Those are vst3 folders. You shouldn't be installing vst2 there at all really.
The dll in the (x86) folder is most likely the 32bit one.
You want the 32bit dll in a vstplugins folder under the Program Files (x86) folder
You want the 64bit dll in a vstplugins folder under the Program Files folder
Then you want to make sure the 64bit folder comes after the 32 in the path listing.
Leave the vst3 versions where they are.
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 02:14 PM.
|