v17 (beta)

[Hexspa]

The new installer is cool, congrats. Will the new installer detect which plugins I have installed next time I run it? If not, can we have presets? I haven't been installing a single-band plugin when the MB version is there i.e. MBitFun vs MBitFunMB. Thanks.

Thanks. Yes, it remembers what you have installed. These plugins are selected, and if there is any update, it updates only the installed items. So if you have installed, for example, MBitFunMB, it will not install MBitFun unless you select it manually and then install it. MPluginManager will keep your current set of plugins.

However, some plugins, such as TurboDelay and MTurboDelayMB, are both under MTurboDelay. For this, we could possibly add some settings or similar options if it is important to someone.

I appreciate your attention. In practice, it's not a huge deal. It's maybe 10 plugins that have both MB and non-MB versions. The features you describe seem cool. Congrats on the progress.

[VariKusBrainZ]

- No longer requires a password for plugin or addon installation on macOS.

Please could we have parity on Windows and also do away with the password

[prototypicalDave]

Having some terrible issues on an Intel Mac running Ventura 13.6.7 (22G720).
I'm a subscriber to the complete bundle and aside from some quirks in loading instruments in MSoundFactory and occasional UI issues have been loving it.

The progression of issues looks like this:
1. Attempt to reinstall 16 due to longstanding UI quirks that took the form of an inaccessible settings menu.
2. Try the 17 beta with partial success. Vst plugins weren't visible in Reaper and MSoundFactory instruments weren't loaded despite them being present in the target folders.
3. Delete everything melda related from my system and try with the latest 16 installer.
4. Looks like it's successful, but when I went to install the instrument packs, the installer seems to think that I already have them installed despite this being untrue.
5. In an attempt to work around this, I decide to use the offline install function in hopes that I can delete everything again and attempt to install in Offline mode.
6. Everything looks fine until Mac tells me that I am out of system memory and that Melda is using 200 ish gb.
7. Kill the application.
8. Try 17 again, everything looks normal until program crashes (segfault) at the end.
9. Try 16 with the same result. segfault
etc, etc.

Obviously I have corrupted something somewhere and I am lost!

[prototypicalDave]

Sorry, just saw the reply to my earlier complaint. This is a similar error and probably related. And yes indeed the problems seemed to go away after a waves update. There IS currently a Mac update that I have yet to apply due to a basic skepticism lol. I'll give that a try and report back.

[prototypicalDave]

Same error after applying the Os update.
Attempting to start MPluginManager results in thread-ruining crash log

[Sampleconstruct]

It doesn't make sense to ruin this thread with crashlogs...

[sinkmusic]

With this new installer, is it possible to chose the location where the plugins (VST2) get installed?
(As far as I remember, with a previous version, I had files all over the place, with newer versions of the plugins installed in a new folder -where my DAW would not scan for plugins-, while older versions were kept intact and still installed in my usual -but custom- location).

[satYatunes]

With this new installer, is it possible to chose the location where the plugins (VST2) get installed?
(As far as I remember, with a previous version, I had files all over the place, with newer versions of the plugins installed in a new folder -where my DAW would not scan for plugins-, while older versions were kept intact and still installed in my usual -but custom- location).

It does for VST2, in settings section. I would suggest you set those options before starting the installation. It also allows to set content folder for mdrummer and msoundfactory.
I like this installation manager, pretty smooth experience for me and no issues so far.

[sinkmusic]

Thank you, Satyatunes (and thank you for your skins, as well)

[satYatunes]

Thank you, Satyatunes (and thank you for your skins, as well)

Thank you

[prototypicalDave]

I worked my way around the errors and got everything installed and working.
17's plugin download manager still segfaults when attempting to open it and 16.11s version thinks that I have all instruments installed even when the sample directories have been deleted.
It seems to be that there must be some file written somewhere that has the side-effect of informing the installers of a fictional system state.
IDK. Still love the plugins enough to keep paying for them and to deal with this headache, so....
Sorry for "ruining" the thread that seemed to exist for the purposes of documenting errors related to a beta release by including thorough documentation of bugs in the beta release lol.

[Frankie.T]

I prefer a tread "ruined" with crash logs, than projects ruined by crashes.

So everyone who has issues, please continue to let Melda know about them, so we can have better stability

[24toSX]

Hi,
now, that v17 is on final on the website, is there a plan for the offline installer?

"For those without an internet connection, an full offline mode for this installer will be available soon, in about a week or two."

Thanks
24toSX

[Hexspa]

I prefer a tread "ruined" with crash logs, than projects ruined by crashes.

So everyone who has issues, please continue to let Melda know about them, so we can have better stability

I think the point is that long crash logs make it hard to read this thread. The logs can be placed into code blocks or emailed directly to the devs.

[Sampleconstruct]

I prefer a tread "ruined" with crash logs, than projects ruined by crashes.

So everyone who has issues, please continue to let Melda know about them, so we can have better stability

I think the point is that long crash logs make it hard to read this thread. The logs can be placed into code blocks or emailed directly to the devs.

I should have phrased it like this rather than causing controversy by my comment so whoever felt offended, sorry.