MFreebundle (new) not registering in DAW
-
- KVRer
- 8 posts since 14 Mar, 2020
I had to build a new computer after a crash. I re-downloaded the MFreebundle (which appears to be a newer version). In "Reaper"...my sessions are loading without recognizing the newly installed Melda VST (which works fine) as the same plugins. Is there anything I can do to get Reaper/Host to know that these are the same plugins?
-
- KVRAF
- 10376 posts since 2 Sep, 2003 from Surrey, UK
What folder(s) did you select for the plug-ins? Or did you just keep the defaults?
Are those paths in Reaper's Preferences VST plug-ins path list?
Are those paths in Reaper's Preferences VST plug-ins path list?
-
- KVRer
- Topic Starter
- 8 posts since 14 Mar, 2020
I kept the defaults...which are showing up in Reaper for use...but the old ones (in sessions) aren't finding them. Not sure how to make them...they new ones are acknowledge by reaper. What am I missing here?
-
- KVRAF
- 10376 posts since 2 Sep, 2003 from Surrey, UK
Start a new Reaper project, then in the Preferences, select "Clear cache / rescan" then try an old project.
Are the old projects using the same format plug-ins - VST, VST3, AU, AAX ?
Are the old projects using the same format plug-ins - VST, VST3, AU, AAX ?
-
- KVRAF
- 10376 posts since 2 Sep, 2003 from Surrey, UK
I do not think that Reaper project files contain plug-in paths, only plug-in names. And the names do not change between release versions. What version were you using before?
Exactly what happens / do you see when you load an old project?
Perhaps you can upload a small problem project (no audio samples needed) to somewhere safe so we can have a look and see what's (not) happening?
Exactly what happens / do you see when you load an old project?
Perhaps you can upload a small problem project (no audio samples needed) to somewhere safe so we can have a look and see what's (not) happening?
-
- KVRer
- Topic Starter
- 8 posts since 14 Mar, 2020
The melda plugins show up in the "couldn't load list" at start up...in the session they're "red" and when inspected in FX box...it says "The following effect plugin could not be loaded"..."effect configuration is preserved". I can find the new installed version manually and load them and they work fine. But of course they're not configured properly.
-
- KVRian
- 975 posts since 10 Jan, 2007 from London
Sounds like a VST versus VST3 thing, which is what DarkStar was getting at above. VST and VST3 versions can have the same name but they are different under the hood..they have a different ID..REAPER sees them as different plugins. Were the old plugins VST? And when you installed the new ones did you choose to only install VST3?
-
- KVRian
- 975 posts since 10 Jan, 2007 from London
Ok, so if the old was VST3 and the new install included VST3 then REAPER should have found it. So when in FX box...it said "The following effect plugin could not be loaded", it indicated VST3 yes?
Sometime ago Melda changed the names of a few plugins and even though the same ID was kept (to avoid these sort of problems) I think there was an (expected) backwards compatibility problem with at least one of them...not sure. Which plugins are you having problems with?
Another thing, and this is a long shot, but a few days ago I had a similar problem loading an old project where the message "The following effect plugin could not be loaded" indicated a VST3, but I knew that I had never installed the VST3 version of this particular plugin (I checked in common files..nope). I put it down to a glitch and then did a Clear cache/re-scan which fixed the problem.
Sometime ago Melda changed the names of a few plugins and even though the same ID was kept (to avoid these sort of problems) I think there was an (expected) backwards compatibility problem with at least one of them...not sure. Which plugins are you having problems with?
Another thing, and this is a long shot, but a few days ago I had a similar problem loading an old project where the message "The following effect plugin could not be loaded" indicated a VST3, but I knew that I had never installed the VST3 version of this particular plugin (I checked in common files..nope). I put it down to a glitch and then did a Clear cache/re-scan which fixed the problem.
-
- KVRer
- Topic Starter
- 8 posts since 14 Mar, 2020
Yes, when the session loads...the plugins that don't load are all VST3. Either way, I've loaded both VST and VST3. The Melda that I"m having problems with is the MFree stuff. MTremolo, MPhaser, etc. Also, other Plugins that were doing the same thing...also are listed as name/title and not path. So, I'm not able to see the path that was originally associated. This certainly isn't the end of the world. I can go back and add the plugins and mess with the settings until I get something I like (again). I was just hoping to save that hassle since I have a lOT of sessions with these plugins.
-
- KVRAF
- 10376 posts since 2 Sep, 2003 from Surrey, UK
Ah ha, I asked about plug-in formats but you did not comment.
Try uninstalling. Then reinstall, selecting VST3 plug-ins only. VST3 plug-ins go into a fixed location as far as I know.
Try uninstalling. Then reinstall, selecting VST3 plug-ins only. VST3 plug-ins go into a fixed location as far as I know.
-
- KVRAF
- 10376 posts since 2 Sep, 2003 from Surrey, UK
Perhaps you can upload a small problem project (no audio samples needed) to somewhere safe so we can have a look and see what's (not) happening?
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Try contacting Cockos, if the host doesn't find the plugin, despite you know it is installed and you can open it, that's most likely a bug in that host.
