well, I renamed 'massive X.dll' and re-scanned Reaper vsts and the scan failed to read again... so, I then moved the dll to another scannable folder (still renamed) and re-scanned and again it failed... maybe I misunderstood your post? Did I do the process incorrectly?
(There is no older version installed - I removed it before the new install)

 

Last edited: Apr 15, 2025 at 4:37 AM

I tried this with other pluggies and it worked. For instance to compare two versions I renamed the installed one from (as an example) bestcompressor.dll to bestcompressorv1.dll and installed the new with its ori name - simply because you can't change the name during the installation. But in case the file only has to be copied I renamed the new one to bestcompressorv2.dll.

 

ok @No Avenger, I screwed it up somehow I guess... I'll try again when I'm home... THX!

 

well, I got pretty discouraged when the renaming/relocating didn't work... so I said to myself "frack it, I'll start again", so I removed all traces of MX... then tried R2R and the keygen failed to activate the product - crap... then I removed all traces again and retried @bobdule and this time it worked!?!? I changed nothing but it worked, so I have no solution for this post... I do thank you all for suggestions and mostly @bobdule for his version and hard work... did I miss something when I removed MX before? Who knows? I don't! LOL

 

If i understand correctly, if i may ask,, the bobbule version works for u. but did it work after the update, or just nothing. if so just check where the vst3 or whatever it is installed to the location. for ex. vst3 usually installs to PGM files\common files\Vst3, and inside a specific folder of the manufacturer, but some times from a different release it gets placed there without folder. just check the date created and modified etc.

Edit: Just went thru other posts..
Try Opening the reaper resourses folder and 'reaper-vstplugins64.ini' in Notepad++ and look for a line that says "Massive x', clear or del the line, and now scan. There is no need to clear cache and rescan fully. Just make sure u keep a backup of the file u r editing.

 

Last edited: Apr 16, 2025 at 2:18 AM

both the R2R and bobdule releases failed to display in Reaper... I removed all traces of each before installing the next... I don't recall any odd installation placements of .dll or .vst3 files, all seemed as it should... also, I made sure the folders were scanned by Reaper (they are my default vst folder settings and I was pretty careful becuz of all the difficulty)...

just saw your edit: now that MX is working (ie. displays in Reaper, loads in Reaper) I'm not going to mess with it thanks... your suggestion would certainly speed up the testing process, however, so thanks for the idea! I'm sure it will help someone

 

Last edited: Apr 16, 2025 at 5:42 PM

[deleted]