Old 09-25-2018, 06:14 AM   #1
Oubliette One
Human being with feelings
 
Oubliette One's Avatar
 
Join Date: Jun 2011
Location: Virginia
Posts: 2
Default VST Plugin Paths

I don't remember exactly when I noticed this starting but it seems that Reaper only recognizes up to 3 VST Plugin paths consistently. While I understand how to enter additional paths to locate other plugins... sometimes it works sometimes it doesn't.

Then once I update the software, Reaper doesn't properly read those paths, and I have to delete them from the location string, purge the plugin directory, and re-scan. Sometimes that works, sometimes it doesn't.

This is a relatively new problem, perhaps in the last year or so.

Anyone else running into this issue?
__________________
TC Electronics - Impact Twin (Audio Interface - which Rocks B.T.W.)/ Presonus Faderport / Win 7/ 24GB RAM
Oubliette One is offline   Reply With Quote
Old 09-25-2018, 08:33 AM   #2
Paul99
Human being with feelings
 
Join Date: Aug 2014
Location: Netherlands
Posts: 882
Default

I have four (4) libraries. No problem her so definitely no bug.
You should however add the 64 bit libraries last for Reaper to take the 64 bit version in stead of the 32 bit version. And check your "reaper-vstplugins64.ini" to check if plugins are blacklisted and erase that line.
Paul99 is offline   Reply With Quote
Old 09-26-2018, 09:10 AM   #3
Oubliette One
Human being with feelings
 
Oubliette One's Avatar
 
Join Date: Jun 2011
Location: Virginia
Posts: 2
Default

Thanks Paul99 I'll look into that. Hopefully that will solve it. How do you determine if they've been blacklisted in that .ini file?
__________________
TC Electronics - Impact Twin (Audio Interface - which Rocks B.T.W.)/ Presonus Faderport / Win 7/ 24GB RAM
Oubliette One is offline   Reply With Quote
Old 09-26-2018, 09:32 AM   #4
Paul99
Human being with feelings
 
Join Date: Aug 2014
Location: Netherlands
Posts: 882
Default

Quote:
Originally Posted by Oubliette One View Post
How do you determine if they've been blacklisted in that .ini file?
Simply.
Right entry:
PG_8X.dll=0053D7F9AAA8D101,1346844760,PG-8X (MLVST)!!!VSTi

Wrong entry:
PG_8X.dll=0053D7F9AAA8D101

See the difference?
Solution: delete the wrong entry and do a scan again. Now Reaper will test the plugin again and hopefully accept it when it is good.
Paul99 is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 04:51 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.