MeldaProduction

VibraSound · Post by **VibraSound** » Mon May 04, 2015 6:07 am

Hi

The installer will install both 32-bit and 64-bit plugins.
I just want the 64 bit no 32 bit.
Why no option to select 64 bit only ?

Thanks

MeldaProduction · Post by **MeldaProduction** » Mon May 04, 2015 10:26 am

Hi,

sorry, it won't happen. It takes almost no space now and way too many people don't even understand what 32 & 64 is, so the installer will just install both, no need to worry about it.

Mace404 · Post by **Mace404** » Mon May 04, 2015 10:40 am

MeldaProduction wrote:Hi,

sorry, it won't happen. It takes almost no space now and way too many people don't even understand what 32 & 64 is, so the installer will just install both, no need to worry about it.

Wait, what? Whats so hard about a checkbox? (and not to mention underestimating your users)

fyi, the path isn't even checked in the installer and can be blank! It will install the plugins in the working folder/path of the installer.
So while you are busy adding handlers take that time to add that checkbox as well

It isn't about space btw. Its about keeping your production machine clean and uncluttered.
Why should I want duplicated plugins to start with? Most host nowadays have automatic bridging and they show up twice.

MeldaProduction · Post by **MeldaProduction** » Mon May 04, 2015 10:50 am

Sorry, but no. A few files in the 10s of thousands won't do any harm.
But I'd like to know more about the 2 things you mentioned:
1) You said there was a blank path - I don't see how that could be possible, unless you'd write blank path and the installer would store it.
2) If a host bridges a plugin despite it has a correct bitversion, then it is a bug in that host - which one are you talking about? I'm personally checking all hosts I'm aware here and I don't recall any of them having that bug now.

Mace404 · Post by **Mace404** » Mon May 04, 2015 11:32 am

MeldaProduction wrote:Sorry, but no. A few files in the 10s of thousands won't do any harm.

Yeah, you could also skip installing files not needed for the selected plugins. Good idea!

An example:
I only select MPhaser in the installer. What do I get:
Full data files for all plugins (Presets, Impulse responses, MRotary data, EQ comparisons etc etc)
And a 32 and 64 bit version of the selected plugin. Now in context - yeah that 32/64 bit version selection is not that big of an issue

MeldaProduction wrote:But I'd like to know more about the 2 things you mentioned:
1) You said there was a blank path - I don't see how that could be possible, unless you'd write blank path and the installer would store it.

Yes, I removed the path manually - to find out the installer would just accept that. Not logical.

MeldaProduction wrote:2) If a host bridges a plugin despite it has a correct bitversion, then it is a bug in that host - which one are you talking about? I'm personally checking all hosts I'm aware here and I don't recall any of them having that bug now.

I stand corrected. As long as they have the same name they only show up once.
But in case for Reaper its the one last in the path. So if one uses the 64bit version of Reaper and has their 32bit plugin path last in the config it will load the 32bit one even if there is a 64bit one available.
Host (and user) dependent of course so not a biggie.
Still, why forcing to install a plugin you never going to use? (and will be scanned by the host)

alexis1 · Post by **alexis1** » Mon May 04, 2015 11:44 am

Re: plug-ins downloaded that were not selected ... removing them won't affect the function of the separate purchased plug-ins, will it?

Re: removing the 32-bit versions ... are they clearly identified as such, to distinguish them from the 64-bit versions? I don't recall seeing anything in my hard drive from Melda labelled as either 32-bit or 64-bit.

Thanks -

DarkStar · Post by **DarkStar** » Mon May 04, 2015 11:58 am

^^^
They will be in a different set of folders, unless the same folder was selected in the installer for both the 64-bit and 32-bit VSTs. Also, the 32-bit plug-ins are 135 KB here, and the 64-bit plug-ins 164 KB.

---------------------------------
Q: in general (not just MeldaProduction) are VST3 plug-ins 64-bit and 32-bit? How are they organised?

alexis1 · Post by **alexis1** » Mon May 04, 2015 12:58 pm

Thank you, Dark Star. TBH, I don't remember being asked about 32- vs 64-bit at installation, just VST2 vs 3 (I tried to choose only VST3, I think I was successful, but am not sure).

Though I guess it's possible I may have forgotten that I made that choice!

Thx -

MeldaProduction · Post by **MeldaProduction** » Mon May 04, 2015 3:48 pm

Mac404: So by planting an empty path you basically tried to hack the installer

. Anyway you may be aware of what the difference between 32 & 64 is, but I spent already numerous hours explaining people that if their host is 32-bit, they must not use 64-bit plugins despite using 64-bit Windows. Some people even think that 64-bit plugins have better audio quality... Here we have simple solution - it installs all, all data and both plugin versions. Simple. Nothing is ever missing. That's years of experience. Sorry, but the few people like you will have to survive the few additional files.

alexis1: Sure, you can remove any plugin.

32-bit & 64-bit naming: There may be no differences in naming at all. It is not that hard for the host to technically find out if the DLL is 32-bit or 64-bit without doing any odd things with the path. If Reaper is doing that, then that's a big "!!" for improvement in it...

Wanterkeelt · Post by **Wanterkeelt** » Mon May 04, 2015 7:13 pm

As I don't need the 32-bit version, I simply told the installer to put the 32-bit files in a dummy folder like for example C:\Waste and when it was done I simply deleted that folder.
It would be cool simply not to install them at all, but this solution only takes a few seconds too.

mesaone · Post by **mesaone** » Mon May 04, 2015 7:54 pm

I set the Recycle Bin as the install path for the 32 bit versions

VibraSound · Post by **VibraSound** » Mon May 04, 2015 8:58 pm

Mace404 wrote:It isn't about space btw. Its about keeping your production machine clean and uncluttered.

That was my point

Thanks

MeldaProduction · Post by **MeldaProduction** » Mon May 04, 2015 9:43 pm

I'm sometimes so surprised by the solutions you came up with folks!

Personally I think there's really no need to even discuss this... after all on OSX they just have 32 & 64 always and they don't mind, why would they...

dmbaer · Post by **dmbaer** » Tue May 05, 2015 8:17 pm

For what it's worth, the solution I've come up with is a VST-32-bit-Dups directory. If the product insists on installing a 32-bit version, then that's where I direct the installer to put it. And I naturally don't put that directory in my DAW's VST search path.

Of course, for products that differentiate between VST vs VST3 and can install either or both, choosing just VST3 solves the problem up front.

MeldaProduction · Post by **MeldaProduction** » Tue May 05, 2015 9:00 pm

I actually think there's an easier way - use the default paths (c:/program files/vstplugins and c:/program files (x86)/vstplugins) and let the host use just the right path. Of course that means that you'll be using only 32-bit or only 64-bit plugins, but that's recommended anyway... thanks god we have everything 64-bit

.