32bit Meldaproduction plugins

Official support for: meldaproduction.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Just wondering how folks would feel if we had the ability to deselect the installation of all 32bit Meldaproduction plugins during installation.

It’s been many years since I have used 32bit plugins.

Currently, what I do a is set a folder that is never scanned by my DAW.

Post

My current workaround is to go into the 32-bit plugin folder after install, delete all the 32-bit Melda plugins and then open my DAW and scan for plugins. Downside is this needs to be done after each update install.

Would be nice to be able to deselect the 32-bit version of plugins from installing altogether.

Post

Oh, Yes : I have requested that several times. I really, really wish that we had the choice to NOT install 32bit plugins.
I also wish that Melda doesn't add custom "genre" folders ("dynamic, eq, etc"), because i have my own folders categories, and i have to manually move them after each install...

Post

promidi wrote: Mon Mar 15, 2021 5:26 am Just wondering how folks would feel if we had the ability to deselect the installation of all 32bit Meldaproduction plugins during installation.

It’s been many years since I have used 32bit plugins.

Currently, what I do a is set a folder that is never scanned by my DAW.
I think that if you specify an invalid directory for the 32 bit plugins, they won't install.

Post

A user shouldn't have to do that to prevent installing of unwanted stuff....

Post

goldglob wrote: Wed Mar 17, 2021 12:19 pm
promidi wrote: Mon Mar 15, 2021 5:26 am Just wondering how folks would feel if we had the ability to deselect the installation of all 32bit Meldaproduction plugins during installation.

It’s been many years since I have used 32bit plugins.

Currently, what I do a is set a folder that is never scanned by my DAW.
I think that if you specify an invalid directory for the 32 bit plugins, they won't install.
You're right for VST2, it says on the installer to do just that.

But for VST3 there is no choice of path; selecting VST3 installs both 32-bit and 64-bit versions at the default VST3 path (on Windows at least). Luckily it separates them into its own Melda folder, so it's quick to go in and delete the 32-bit versions manually.

Post

quietzone wrote: Wed Mar 17, 2021 9:07 pm
goldglob wrote: Wed Mar 17, 2021 12:19 pm
promidi wrote: Mon Mar 15, 2021 5:26 am Just wondering how folks would feel if we had the ability to deselect the installation of all 32bit Meldaproduction plugins during installation.

It’s been many years since I have used 32bit plugins.

Currently, what I do a is set a folder that is never scanned by my DAW.
I think that if you specify an invalid directory for the 32 bit plugins, they won't install.
You're right for VST2, it says on the installer to do just that.

But for VST3 there is no choice of path; selecting VST3 installs both 32-bit and 64-bit versions at the default VST3 path (on Windows at least). Luckily it separates them into its own Melda folder, so it's quick to go in and delete the 32-bit versions manually.
Good point!

Post

Why do you need to delete anything? I have all my 32-bit plugs install to a folder in My Documents, and Reaper doesn't know it exists. I have a 64-bit folder that Reaper looks for, and the 32-bit plugs can sit in their folder ignored for years. Unless you have an issue with space, and it's been forever since hard drive space was a problem.

Post

edkilp wrote: Sun Mar 21, 2021 12:57 am Why do you need to delete anything? I have all my 32-bit plugs install to a folder in My Documents, and Reaper doesn't know it exists. I have a 64-bit folder that Reaper looks for, and the 32-bit plugs can sit in their folder ignored for years. Unless you have an issue with space, and it's been forever since hard drive space was a problem.
You don't need to delete them.

That said, VST3 install to the default 32-bit and 64-bit VST3 folders that cannot be changed in the Melda installer. I do use the odd 32-bit VST3 (bridged to 64-bit in my DAW), so it's just faster to delete the ones that are force-installed there than to figure out how to get the DAW to ignore the 32-bit VST3 Melda subfolder while keeping the rest.

The Melda 32-bit plugins don't take much drive space, because of the shared plugin core architecture Melda plugins use. In my case I delete them to shave off 10 seconds or so of the DAW rescan all plugins time (1000+ VSTs... it adds up), and also because I don't like having things installed that I know I'll never use. Same with deleting forced AAX plugins installed by other companies and other clutter.

Post Reply

Return to “MeldaProduction”