Suppress 32 bit plugin installation?

[sekim]

I'm sure there must be a way to stop 32 bit plugins from installing, but I haven't figured it out other than to put in a non-existent directory and then cancel one by one the 32 bit plugins as they try to install. I searched the forum but didn't find anything with my search terms. Surely there is a better way that I am missing?

[rasmusklump]

Sadly it's the way it is...

[sekim]

Sadly it's the way it is...

You've got to be kidding me.

[vectorwarrior]

I just install them into a newly created folder on my desktop and then just delete when installation is complete. It's not great, we've asked for this before, but it's not the worst thing in the world to live with.

[sekim]

That does not leave a good impression on newcomers. Or on existing customers like me for that matter.

People can live with it but why should they have to? It really is a wart on a pretty face IMO.

[rasmusklump]

+1

[MeldaProduction]

This indeed has been discussed before - people often don't understand what 32-bit/64-bit is, which leads to problems... and results in support responding to lots of question, which they wouldn't need to. Considering how small the plugins actually are, this is still a no, sorry.

[sekim]

The issue is not the size on disk, it is the spamming of the plugin lists inside DAW when one has a few legacy 32 bit plugins they need to keep and then the full suite of Melda 32 bit and also a pile of 64 vst2 and the whole suite of Melda and a pile of 64 vst3 and the whole suite of Melda. Sure there are other ways to fix it. And it has to be redone every time we update Melda. As it stands, unless I jump thru hoops (which I do), my DAWs enumerate three instances of each Melda plugin. Spam.

[sekim]

It seems that implementing a "secret" hotkey or some other "known to those who want this feature" type way of disabling any of the flavors would be a way to satisfy Melda's desire to have all flavors install by default in order to avoid problems from the less knowledgeable, while allowing the more knowledgeable to do what they need to do. jmo of course.

[noizejoy]

The issue is not the size on disk, it is the spamming of the plugin lists inside DAW when one has a few legacy 32 bit plugins they need to keep and then the full suite of Melda 32 bit and also a pile of 64 vst2 and the whole suite of Melda and a pile of 64 vst3 and the whole suite of Melda. Sure there are other ways to fix it. And it has to be redone every time we update Melda. As it stands, unless I jump thru hoops (which I do), my DAWs enumerate three instances of each Melda plugin. Spam.

Have you tried to change the default installation folders for the Melda 32bit and 64bit VST2 plugins to a folder that's not enumerated by your DAW?

That should be a one time change since, the Melda installer remembers your preferences for install folders for those.

[Nobdi]

This indeed has been discussed before - people often don't understand what 32-bit/64-bit is, which leads to problems... and results in support responding to lots of question, which they wouldn't need to. Considering how small the plugins actually are, this is still a no, sorry.

This is your answer to a customer question for a feature (option) that has been implemented by pretty much every other plugin company on the planet ? Seriously ?!?

[MeldaProduction]

Why don't you simply put it into some irrelevant folder not attached to any DAW? The thing is the existence of 32-bit plugins should be completely irrelevant, the DAW should choose the best option, but I suppose you are using some DAW, which cannot do that for some reason.

[sekim]

I fail to see how providing a way for user to tell the installer to place the unwanted plugins into a "junk" folder is somehow going to cause Melda less headaches than allowing the user to tell the installer (by leaving the folder field blank) to not install them at all. Once the user changes the default folder, which is currently allowed, is when the uninformed would potentially get confused. No?

All that said, I have my way of dealing with the issue (I just delete them from the folder after install), and the issue isn't a deal killer by any stretch, just a nuisance. So I'm back to making music for now (with Melda plugins of course). Cheers.

[promidi]

I just install the 32bit Meldaproduction plugins to my windows temp folder. This folder gets cleaned out during nightly maintenance.

Because most of us pretty much know what we're doing, it would be nice if Meldaproduction gave us a way to suppress 32bit plugin installations. However, because most of us pretty much know what we're doing, we can find suitable workarounds.

[MeldaProduction]

I just install the 32bit Meldaproduction plugins to my windows temp folder. This folder gets cleaned out during nightly maintenance.

Because most of us pretty much know what we're doing, it would be nice if Meldaproduction gave us a way to suppress 32bit plugin installations. However, because most of us pretty much know what we're doing, we can find suitable workarounds.

Exactly!

The no choice thingy is there simply because of the users, who do NOT know what they are doing too well, and because it doesn't take almost any space anyways.