v17 (beta)

[MaartenvdP]

- after I uninstalled Monastary Piano and tried to install it again I run into permission troubles. After I returned to version 16 I could install it again.

After manually setting the permissions 'Full Disk Access' under settings to the MPluginManager this was no problem anymore. SOLVED.

With other installers there is a question about setting this permission but I don't think it was with the v17 version.

[martin-meldaproduction]

Hello Folks,

<snip>
In case some features in v17 are not working as expected, do not hesitate to contact our customer support.


 

Hi support,

I am not sure if this is the right place to post or if I should make separate topics for each bug.
These are my experiences with v17beta. Maybe it's helpful. In general, I like the new installer very much! Especially that it knows what I already have

Some bugs.
- after I uninstalled Monastary Piano and tried to install it again I run into permission troubles. After I returned to version 16 I could install it again.
- I was unable to paste my serial number for license activation
- in Logic Pro after choosing a sample from Sampler within MSoundFactory from an external SSD, Logic crashes and recovers. No crash in Cubase. Actually this does now also happens with version 16 in Logic. Maybe related to the permission problem.

Attached two screenshots about these problems.

gr.M


Screenshot 2024-07-06 at 11.50.23.png

Screenshot 2024-07-06 at 11.47.35.png


 

Transition from V16 to V17 can be problematic on macOS, due to insufficient permissions set already to some crucial folders.

To resolve your issue with MonasteryGrand, I recommend:

- delete the target folder /Volumes/nonKontakt/Melda/MeldaProduction/MonasteryGrand completely and install MonasteryGrand again (by double clicking its status)

- if you set to MDrummer factory path to /Users/username/Documents/MDrummer and MSoundFactory sample path to /Users/username/Documents/Samples , which are recommended
settings, it should be working ok. If you already have these folders from the past and get some permission issues, again delete then re-install. Then you should be OK.

This should help resolve your issues with addons.
Regarding the clipboard, yes we know about it, again macOS permission issue looks like another wall of restriction from macOS - we are working on fix.

As temporary workaround for the clipboard and also addons to have higher permissions, you can run the MPlunginManager from terminal as:

cd /Applications/MeldaProduction/Kernel/MPluginManager.app/Contents/MacOS/ && sudo ./MPluginManager.bin root

[MaartenvdP]

<snip lots of valuable info>

Thanks for the information and workarounds!

[sparella]

Is the intention to use the plugin manager to install user created MXXX .mproduct files too?

[martin-meldaproduction]

Yes, you can install your *.mproduct files via MPluginManager. On the second MSoundFactory & MDrummer addons tab click the button "Offline install", which lets you select and install your addons (*.mproduct files).

[martin-meldaproduction]

Guys,

For those who had issues with permissions on macOS, accessing the clipboard, etc., we have released MPluginManager version 01.04, which is now available for download. For those who already have it installed, just launch MPluginManager, and it will perform a self-update to version 01.04.

Main changes:

- No longer requires a password for plugin or addon installation on macOS.
- Fixed permission issues when installing addons from/to some folders on macOS.
- Fixed access to the system clipboard on macOS.
- Has the new style Argon as the default; hope you like it.
- Improved plugin installation speed.
- Other fixes based on your reports.

Additional features are coming soon. Please stay tuned. If there is anything else, please contact our customer support.

[Hexspa]

This is a long beta! Any word on a release date? I'm eager to try the new installer.

[martin-meldaproduction]

This is a long beta! Any word on a release date? I'm eager to try the new installer.

Probably next week if all tests goes well:-)

[MeldaProduction]

Next week should be the final release! But you can try it already, only minimal changes will be done probably.

[audiojunkie]

Out of curiosity, what copy protection type does your plugins use?

[Frankie.T]

Out of curiosity, what copy protection type does your plugins use?

SN with no C/R
The best one, and i hope they will never change it, cause that's one of the reason people like me approached Melda, and it's important they know, this is a value their customers appreciate

[audiojunkie]

Yes, indeed! That is the kind of copy protection I buy: A serial number or keyfile that doesn’t tie itself to anything and doesn’t call home—it must be able to let me authorize my software if a company goes out of business.

I’m thinking of expanding my sound palette a bit on my Linux system with WINE and yabridge.

[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.

[martin-meldaproduction]

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.

[Sampleconstruct]

Overall the new installation system is much better than the old one and it's MSuperFast too. Just updated all my plug-ins with installer version 1.05 and all issues seem to have been solved