Plugin browser doesn't see Eventide plugins

[dennisnv]

After installing the latest version of REAPER none of my Eventide plugins appear in the plugin browser. The Eventide plugins that already existed in projects are being recognized and are working properly so I know REAPER can "see" them. I just can't add new instances of Eventide plugins since they aren't showing up in the browser.

REAPER v5.50/x64 rev.b44734; Windows 10; Intel Core i7 2.8GHz quad-core; 24Gb ram

[foxAsteria]

Yea I can't get Reaper to see that new freebie EQ they just put out. I thought it must be something to do with the stupid iLok bs...

[RobU]

I've got the 2016 Stereo Room (installed months ago), and the new EQuivocate (installed after upgrade to 5.50) - no FX browser issues here.

You could try clearing your VST cache and rescanning ?

[grinder]

on my install the plug was installed in my
common files Steinberg (spelling?) folder.
Might be there in yours this should be in your scan path if this is so.

Grinder

[ivansc]

I just got round to installing that new free EQ plug and it wanted to install in program files/common files/steinberg/vstplugins too.

Sine I am about halfway persuaded to start using the common files approach (well vst3 stuff is already going there whether I like it or not and there IS a VST sub-folder) it made sense to me to go with the flow apart from the Seinberg sub folder, which I omitted.

Worked perfectly first time including the auto authorisation part.

[dennisnv]

I have all my VST locations loaded in the REAPER scanner and, as I mentioned, the Eventide plugins were working just fine until the REAPER update. The REAPER update and the free EQ plugin came along about the same time but I had successfully tested the new Eventide EQ in REAPER and still have an instance of it in REAPER that still works; that's why I think the problem is with the REAPER update. However, I am going to log a support request with Eventide, maybe they can shed some light on this. I'll post whatever I get back from them. In the meantime, perhaps a REAPER guru will see this and offer the solution.