brettgoodkin wroteThis is precisely why it’s unhelpful to have comments from people unaffected by this glitch. It is decidedly not useful at all to proffer fixes for an issue that I’m not talking about...

Again... the issue at hand isn’t about the plugins not being discovered by the daw... s1 sees the plugins and allows you to insert them into your session... however, the GUI is grayed out and the plugins don’t work. Unless you’ve conquered that particular issue your workarounds to issues outside of this aren’t helpful and clutter the discussion.

Also, there should be zero need to add the file loc of the waves packages... they’re in your common files which s1 scans whether you have the directory visible in your scan or not.

This particular problem isn’t resolved even by uninstalling and reinstalling the waves plugin library, uninstalling and reinstalling the daw after removing the entire user setting folder...

So, clearly resetting the black list and jiggering with file locations within s1 also has no effect on this particular problem.

I’m not trying to be combative, just focused on getting this particular issue fixed.

gregghart wrote

brettgoodkin wroteThis is precisely why it’s unhelpful to have comments from people unaffected by this glitch. It is decidedly not useful at all to proffer fixes for an issue that I’m not talking about...

Again... the issue at hand isn’t about the plugins not being discovered by the daw... s1 sees the plugins and allows you to insert them into your session... however, the GUI is grayed out and the plugins don’t work. Unless you’ve conquered that particular issue your workarounds to issues outside of this aren’t helpful and clutter the discussion.

Also, there should be zero need to add the file loc of the waves packages... they’re in your common files which s1 scans whether you have the directory visible in your scan or not.

This particular problem isn’t resolved even by uninstalling and reinstalling the waves plugin library, uninstalling and reinstalling the daw after removing the entire user setting folder...

So, clearly resetting the black list and jiggering with file locations within s1 also has no effect on this particular problem.

I’m not trying to be combative, just focused on getting this particular issue fixed.

This is precisely why it IS helpful, my friend. THAT IS the issue that this fixes. The DAW sees them...but they do not work.

You must delete the location and put them back in. I do not know why this works, but it does. PLEASE TRY IT!

Jemusic wroteHave you got AERO turned off for any reason on your Windows machine.

When AERO is turned off I got the blank GUI thing as well. On other plugins too as well as Waves. As soon as I turned AERO back on everything was fine again. Not sure if this is your issue but there were some Windows tweaks that suggested turning AERO off and it is just plain wrong. There is nothing to be gained by doing so especially with our current fast computers.

Blank GUI suggests something else that might be video card driver related etc..Have you checked up on the video side of your system. Latest drivers etc..

jdurham wrote

brettgoodkin wrote

miked7 wrote
It’s tempting for some to pop into a thread like this to announce that it doesn’t impact them...

Resist that urge. It’s off-topic and it clutters the discussion.

For those of you who have-are dealing with this... please file CS tickets with Waves and presonus.

My inbox at Gearslutz has 16 private messages saying “me too!” That’s cool and all... but report it!

Another thing to look for if your plugins are working... if you drag a Waves plugin onto a track and it doesn’t launch until you do it a second time that’s s related problem that, again, should be reported.

I think it's helpful for people to post in a thread like this if they are NOT having a problem as well, granted if they are helpful with the process, because there may be a clue in their setup or process that may solve the problem for someone else. And some of us are willing to help out those who are having issues and see if we can replicate the problem on our side... all that info is invaluable in establishing the pattern and figuring out the potential issues for the developers to address.

In my case, I have NO problems with Waves v9 and v10 installed on the same system on Win 10 Pro 1803 with Studio One 4.1.

Having said that, with every new Waves plugin I buy, I have found that it's important to RESET, RESCAN, REMOVE, and RE-ADD the plugin paths EVERY time I install a new Waves plugin for Studio One. Other DAWs do not need as many steps. I just picked up the new AR TG Mastering plugin and had to do this once again.

My process to get new Waves plugins to show up in S1 4 is to go to Options > Locations and Reset Blacklist, and make sure the "Scan at startup" option is checked. I then also REMOVE the paths to the VST plugins from the Locations box. Hit OK, restart Studio One. Then I ADD the paths back into the Locations box. Restart Studio One. And voila, all my new Waves plugins show up.

For those having problems and that doesn't work, I totally agree you should submit tickets to both Presonus and Waves... but ALSO, please post the exact steps you are doing here in this forum so people here can help diagnose the problem. If we can duplicate the steps you are doing and it causes the same problem, then we have a repeatable recipe that the developers can test out, thus helping all of us.

gregghart wrote

brettgoodkin wroteThis is precisely why it’s unhelpful to have comments from people unaffected by this glitch. It is decidedly not useful at all to proffer fixes for an issue that I’m not talking about...

Again... the issue at hand isn’t about the plugins not being discovered by the daw... s1 sees the plugins and allows you to insert them into your session... however, the GUI is grayed out and the plugins don’t work. Unless you’ve conquered that particular issue your workarounds to issues outside of this aren’t helpful and clutter the discussion.

Also, there should be zero need to add the file loc of the waves packages... they’re in your common files which s1 scans whether you have the directory visible in your scan or not.

This particular problem isn’t resolved even by uninstalling and reinstalling the waves plugin library, uninstalling and reinstalling the daw after removing the entire user setting folder...

So, clearly resetting the black list and jiggering with file locations within s1 also has no effect on this particular problem.

I’m not trying to be combative, just focused on getting this particular issue fixed.

This is precisely why it IS helpful, my friend. THAT IS the issue that this fixes. The DAW sees them...but they do not work.

You must delete the location and put them back in. I do not know why this works, but it does. PLEASE TRY IT!

brettgoodkin wroteBut, for the sake of clarity... when you say "You must delete the location and put them back in." What location specifically are you referencing?

jBranam wroteyes i have known this and i always run as admin unless i need to drag and drop from outside S1 and those locations have always been in my locations but maybe others do not. thanks

and brett i know you are frustrated and rightfully so.. but don't take it out on others... especially for those that are trying to help. to be honest when PreAI first posted his 2 cents i scoffed and was about to post this...

"wash, rinse, repeat and if ALL else fails... spin to the left three times and throw a pinch of salt over your shoulder"

and the devil ALMOST made me do it lol but i thought better of it. i then looked into the .settings file and saw that RBass and MV2 were not found but my last purchases were. i then thought WTH.. i will give it a try and LOW AND BEHOLD it worked (i am glad i did not post my thoughts and am thankful he posted it) however bizarre it sounded to me at the time it proved to me that S1 writes intermittently. i would not have 'found my lost plugs' if i had not taken the off chance. also in the 192 interface section down below they had problems with bricked interfaces after a firmware update and Presonus claimed it had to do with certain systems with certain video cards. most ALL video drivers DO have sound drivers in them for HDMI output and that HDMI sound function is seen and is listed in Window$ audio devices. so again however bizarre it may sound it may be relevant so relax a tad.. i think all of us (well most of us) sympathize with your situation and completely understand the stress and most are only trying to help and you should remind yourself of that fact. cheers


jay

PreAl wrote

brettgoodkin wroteBut, for the sake of clarity... when you say "You must delete the location and put them back in." What location specifically are you referencing?

I was the guy who originally suggested this, and now this is the THIRD time I have stated this. So far you have completely ignored..

"Try remove the folder paths, clear blacklist and rescan, restart, then put them back in.. clear blacklist, rescan, restart."

That is ALL the folder paths. Every single one of them that points to ALL plugin folders.

brettgoodkin wroteI’m old and have been a power user and system builder since the Timex Sinclair.

brettgoodkin wrote
Also... I wasn’t aware of this, but, per the Waves CS guys, s1 automatically scans the vst2 vst3 paths in your /commonfiles... which means you don’t need to have these paths in your scan... so, you can’t actually remove these folders from your scan... if you do a fresh install you’ll see that s1 only natively included \vstplugins.... so, even though it’s not shown in the list of plugin scan love, the commonfile folders are being scanned by s1 and these are the locations where waves dumps the waveshells...

So, I don’t know how this fix would work unless you’re manually including the waves plugin packages in your scan, removing them, then putting them back per your walkthrough... but, regardless, it would seem that on your machine you have s1 scanning the same loc twice...

There are plenty of niggles that can’t be explained in a flowchart but somehow work... maybe this is one of those deals... good for you!