3.02 free plugins update (and install) problems

[mabian]

Hello,

a couple glitches in the 3.02 freebies installer/updater:

1) Just like happened with 3.0->3.01, after the update (3.01 -> 3.02) REAPER is no longer able to show the plugins own GUI - they only show up using the standard "anonymous" multislider panel.
The only way to fix this seems uninstall and reinstall using full setup instead of updater.

2) Even though the installer says that to avoid installing VST3 version you can specify an invalid path for it, the setup program completely aborts when a non existant path is given (I tried "S:").
When supplying a non existant folder but under an existing path, the setup program creates the missing folder structure and installs anyway the VST3 plugins...

Any chance to have those fixed?

Thank you,
Mario

[MeldaProduction]

Hi Mario, so

1) I wasn't able to simulate this yet, nevermind I'll keep trying. Btw. did you check with another host? Also do you have up-to-date Reaper? x32 or x64?

2) Ha, what?? :shocked: Where is that written?? There is a switch, but only in MTotalBundle yet, or commercial bundles, I'm not sure, I'll check. Anyway you can just delete the VST3 files if you don't want them. But specifying nonexisting path is definitely not a solution.

[mabian]

1) I wasn't able to simulate this yet, nevermind I'll keep trying. Btw. did you check with another host? Also do you have up-to-date Reaper? x32 or x64?

SONAR 8.5 seems to work well, and opening any Melda plugin in SONAR after the update also seems to make the plugins work fine in REAPER too.
In other words, the problem seem to happen only opening any Melda plugin in REAPER just after the update.

REAPER 3.68, Windows XP SP3 x32.

2) Ha, what?? :shocked: Where is that written?? There is a switch, but only in MTotalBundle yet, or commercial bundles, I'm not sure, I'll check. Anyway you can just delete the VST3 files if you don't want them. But specifying nonexisting path is definitely not a solution.

It's written in the free plugins full installer, below the VST3 path.

Thank you,
Mario

[MeldaProduction]

1) I wasn't able to simulate this yet, nevermind I'll keep trying. Btw. did you check with another host? Also do you have up-to-date Reaper? x32 or x64?

SONAR 8.5 seems to work well, and opening any Melda plugin in SONAR after the update also seems to make the plugins work fine in REAPER too.
In other words, the problem seem to happen only opening any Melda plugin in REAPER just after the update.

REAPER 3.68, Windows XP SP3 x32.

2) Ha, what?? :shocked: Where is that written?? There is a switch, but only in MTotalBundle yet, or commercial bundles, I'm not sure, I'll check. Anyway you can just delete the VST3 files if you don't want them. But specifying nonexisting path is definitely not a solution.

It's written in the free plugins full installer, below the VST3 path.

Thank you,
Mario

I checked using all updating methods and seems working fine. You did restart Reaper, right? Does restarting the computer help? (Maybe Reaper or ASIO is leaking)

Below the VST3 path there is written, that "if you specify an invalid directory, then the VST3 plugins won't be available", which is NOT that they won't be installed. They will just be in different location, so that the host won't know where to find them.

[mabian]

Hello, I always update with no host running.

Maybe it's relevant that I don't use the default paths?

I install the package in M:\Audio\MeldaProduction and the plugins in M:\Audio\Plugin\VST\MeldaProduction.

Don't know about the reboot because I never rebooted after the install/update...

AFAIK, there's at least another REAPER user having the same exact issue.

Ok for the VST3 thing, I got it wrong.

Thank you,
Mario

[MeldaProduction]

Ok, please then next time try to reboot and let me know. I'll try to find out what is wrong, but we need to be able to simulate it, and unfortunately no luck yet.

[Mercado_Negro]

Greetings,

I'm also experiencing (for a long time now) a bug with the "Free bundle". I've tried to find a good recipe to reproduce it consistently but unfortunately I can't find where the problem is. I thought I should comment it here because it's also something in REAPER and these plug-ins' GUIs. Every time I try to add an instance in a project using more than 1.2 GB of RAM, REAPER crashes. Plug-ins are inserted but there's no GUI and a few seconds later (1 or 2 seconds) it crashes.

I'm using

REAPER 64-bits (latest version)
Melda Free VST Effects 3.02 64-bits
Win7 64-bits
Core i5
4 GB RAM

P.S. I found an interesting thread in Cockos' Forums and a response from one of REAPER developers, schwa. Maybe it is related?

http://forum.cockos.com/showthread.php? ... ight=melda

Thanks for your time and consideration,

Best regards.

[MeldaProduction]

Hi,

so it works like this 100%? When you add a different plugin (ideally something that takes some memory), it works well? Also are you 100% sure you are using 64-bit versions of our plugins? And finally, do you have enough memory? For example, I was pretty surprised when I found that Win7 32-bit take more than 1GB just after the startup.

PS. I know about the link, but that's about another "weird" thing in reaper, not related to this.

[Mercado_Negro]

Yes, it works like this 100%

Yes, the rest of my plug-ins works fine

Yes, I'm 100% sure I'm using the 64-bits versions of your plug-ins

Yes, I have 4 GB (as you can read in my specs) and most of the time the project is above 1.2 GB (I've also checked this in Windows Task Manager. I always have like 2 GB free).


Thanks again.

[MeldaProduction]

Ok. So basically you can create a project without any of our plugins, make it big enough and then with 100% certainty it crashes, correct? Ok, please send me an email to info@meldaproduction.com, I'll send you a debug version of one of the plugins. It will create a log, which hopefully let us know, what is wrong.

Cheers!

[Mercado_Negro]

Not *without* but *with*

Thanks for looking into this issue, mail sent.

Best regards