Weird Reaper Behaviour

Discussion in 'Reaper' started by Stevie Dude, Apr 27, 2022.

  1. Stevie Dude

    Stevie Dude Audiosexual

    Joined:
    Dec 29, 2020
    Messages:
    2,178
    Likes Received:
    1,906
    Location:
    Near Nyquist
    Hi,

    I've encountered a weird behaviour on Reaper. Not sure if it's bug or it's just me a noob at setting it up to work as I intend it to be, because it doesn't happen on other DAWs. (Live, Cubase)

    It's how Reaper will only display one VST3 plugin with the same exact file name if you have more than one installed even if they are from different developers/brands.

    1. DJ Swivel Spread
    2. Yum Audio Spread

    Both of the plugin VST file name is Spread.vst3 and displayed as "Spread" in the plugin browser. It happened before my system failed (another story) where only the DJ Swivel's one appear and the Yum Audio's nowhere to be found. I checked at "Plugin That Failed To Scan" list and it's not there. Now that I've installed fresh Windows 11 and everything, only the Yum Audio Spread appears on the list, pretty sure because I've had it installed before the DJ Swivel Spread, meaning I've scanned the plugins few days before I had the Swivel's installed.

    I'd appreciate it, if Reaper users here do the experiment on your system (if you have the time, of course) and see if you encounter similar behavior. If you don't own the plugins, both of them available to try at the sister's site. :wink:

    ..or maybe something about the setting that I don't know.

    Also, I'm not looking for a solution, because I already have one, which is simply rename the VST3 file and both will appear on the list. It's not a stable solution though as some plugin's "protection" will break if you rename the file.

    Just talking about the weird behavior and maybe learn something new because I have too much free time today. Thanks.
     
    • Like Like x 1
    • Agree Agree x 1
    • Interesting Interesting x 1
    • Useful Useful x 1
    • List
  2.  
  3. bigboobs

    bigboobs Kapellmeister

    Joined:
    Oct 10, 2011
    Messages:
    331
    Likes Received:
    58
    • Interesting Interesting x 3
    • Useful Useful x 2
    • Like Like x 1
    • Creative Creative x 1
    • List
  4. Sinus Well

    Sinus Well Audiosexual

    Joined:
    Jul 24, 2019
    Messages:
    1,969
    Likes Received:
    1,514
    Location:
    Sanatorium
    [​IMG]
     
    • Like Like x 3
    • Useful Useful x 1
    • List
  5. Stevie Dude

    Stevie Dude Audiosexual

    Joined:
    Dec 29, 2020
    Messages:
    2,178
    Likes Received:
    1,906
    Location:
    Near Nyquist
    I thought it only applies to the X64, X86 architecture because I assumed Reaper will read the "Developer" metadata in the plugin and naturally show only one if you have both from same dev.
     
  6. No Avenger

    No Avenger Moderator Staff Member

    Joined:
    Jul 19, 2017
    Messages:
    8,912
    Likes Received:
    6,110
    Location:
    Europe
    Oh, it does, even for VST2 pluggies and it shows it (e.g. VST: Valve Exciter (AudioThing)), but this name is not written in the dll's name.
     
  7. Stevie Dude

    Stevie Dude Audiosexual

    Joined:
    Dec 29, 2020
    Messages:
    2,178
    Likes Received:
    1,906
    Location:
    Near Nyquist
    yeah, I noticed that, why it still didn't show same file name files but from different developers is what I'm wondering. If it does read that, I suppose it knows that those aren't the same plugin even they have the same file name, and should display both of them.

    Different with Ableton Live, for VST3, it will still display both files with same name, but if the same file with different names it will only show one. I hope I make sense. :)
     
    • Interesting Interesting x 2
    • List
  8. naitguy

    naitguy Audiosexual

    Joined:
    Jan 9, 2017
    Messages:
    732
    Likes Received:
    512
    Location:
    Canada
    (never mind, sorry!)
     
    Last edited: Apr 27, 2022
  9. No Avenger

    No Avenger Moderator Staff Member

    Joined:
    Jul 19, 2017
    Messages:
    8,912
    Likes Received:
    6,110
    Location:
    Europe
    ->
    :winker:
     
  10. midi-man

    midi-man Audiosexual

    Joined:
    Sep 25, 2013
    Messages:
    1,592
    Likes Received:
    796
    Yes you can rename the dll's. Reaper will scan. I usually use the ver number. For example Blue Arp = BlueARP.x64.2.3.7.dll
     
    • Agree Agree x 1
    • Useful Useful x 1
    • List
  11. naitguy

    naitguy Audiosexual

    Joined:
    Jan 9, 2017
    Messages:
    732
    Likes Received:
    512
    Location:
    Canada
    Woops, my bad. Why can't I disagree with my own post? :P
     
  12. justsomerandomdude

    justsomerandomdude Platinum Record

    Joined:
    Aug 24, 2020
    Messages:
    423
    Likes Received:
    278
    Sometimes i get this issue "Terminate Vst" after installing a new plugin, sterday this happened with EZDrummer 3, problem was i only installed Vst3, i had to reinstall along with the standalone version and it worked but had to rename the .vst3 to something, i was fucking tired of the renaming ritual, so i figured a solution, maybe this was mentioned b4 and well known, but i didnt look for it, i was tired of looking up tat too.
    So here it is
    If u r using 64-bit Reaper open up C:\Users\(username)\AppData\Roaming\REAPER\ in that folder open "reaper-vstplugins64.ini" this is ur plugin cache - both ur 64-bit and 32-bit vst or vst3 will be in this.
    if its a 32-bit
    open reaper-vstplugins.ini
    Open it In a text editor ( i use Notepad++) Find the problematic .vst using ctrl+f, usually if u have installed it lately it will be in the bottom. When u have found the line (eg. EZDrummer "EZdrummer_3.vst3=.............so on for vst2 it ll be .dll,") select just that entire line hit delete, and now if u reinstall the plugin again u dont have to rename it and it will be scanned as new, and more than that u dont have to clear the cache and go through the rescan nightmare again.

    But remember, always make a back up of the user data folder [C:\Users\(username)\AppData\Roaming\REAPER\ ] somewhere safe.
     
Loading...
Loading...