MUX VS BIDULE UPDATE
You could duplicate the dll and have one with each name, but you'll have to remember you did that if you ever update the plugin. You can just change the name back, but any project referencing the new name will begin to report the plugin as missing. This will happen if you've renamed plugin dll files. I ran into this problem again, so here's another potential solution if anyone's interested(it's working for me). Closing Reaper and restarting a new project allows new plugins to be loaded. If I close Reaper, start a new project, add many plugins that are not used in the problem project, open the problem project in a new tab or as the only project (new one is closed), some previously ok plugins of project cannot load, but the ones from the new project can load.Īfter closing the problem project, loading plugins on a new project is still limited. If I delete all plugins, save the project without plugins, close reaper, reopen the project, I can load any plugin. If I delete many or all plugins, only 2 or 3 new plugins will load. Only fabfilter volcano is on this project though. I have also experienced this problem over a year I have installed some plugins from all of those companies you listed, except UAD. I usually have Heda's Track Inspector script running, but the behavior happens with it not running also. This includes Reaper vst plugins such as Reagate. It is not specific to any certain plugins, any plugin that is not already loaded in the project will not load. It is as if my project has reached its limit for adding new vst/vsti plugins. ini/rescaning plugins has no effect (thanks for your input though FoxAsteria). My situation is very similar to blackart's. In the attachment example I can't instantiate the UAD VSM-3 plugin but i can instantiate the mono version Its a very random issue but VERY frustrating but it might be hard to provide exact steps to achieve the same but i can provide sample projects where i have the issue Waves plugins mostly seem unaffected but my UAD and fabfilter and soundtoys have issue but not with all of their plugins, only some. Firstly all plugins are available and then after some time when the project gets bigger i am no longer able to use certain plugins. It seems to me this starts to happen at a certain point when mixing a big projects. Sometimes i already have an instance of the plugin on another track but i can't instantiate it on said track but i can drag and drop it over.
there is no problem with Reaper detecting them. If i close Reaper and open a blank project i am able to load these plugins. Basically i can't instantiate some plugins even though they are working fine in other projects or even this project! i get an error saying "The following effect plug-in could not be loaded". This error/issue happens on multiple different projects.
MUX VS BIDULE WINDOWS 10
I'm running Reaper 5.40/圆4 Windows 10 圆4 pro.
0 kommentar(er)
