Michael Peters

I used Plogue Bidule for years, 64 bit, on a Windows 64bit machine. (Bidule is a software that is similar to Max in many ways.) Many VST plugins that I used came in 32bit versions, so I used a jBridger program to convert them to 64bit. I keep the 32bit and the 64bit versions in different folders, and I point Bidule to the 64bit folder, so it recognizes only the 64bit plugins. Everything works fine.

When I try to do the same in Max, there is apparently no way to specify where the 64bit plugins are. Instead, Max finds the 32bit plugins and lists them for me to choose from, and when I choose them, I get a "no format VST exists" error. 

What can I do? I'm already in love with Max and would like to migrate from Bidule but I need my VST plugins.

I used Plogue Bidule for years, 64 bit, on a Windows 64bit machine. (Bidule is a software that is similar to Max in many ways.) Many VST plugins that I used came in 32bit versions, so I used a jBridger program to convert them to 64bit. I keep the 32bit and the 64bit versions in different folders, and I point Bidule to the 64bit folder, so it recognizes only the 64bit plugins. Everything works fine.
When I try to do the same in Max, there is apparently no way to specify where the 64bit plugins are. Instead, Max finds the 32bit plugins and lists them  for me to choose from, and when I choose them, I get a "no format VST exists" error. 
What can I do? I'm already in love with Max and would like to migrate from Bidule but I need my VST plugins.

I used Plogue Bidule for years, 64 bit, on a Windows 64bit machine. (Bidule is a software that is similar to Max in many ways.) Many VST plu

vst-3264-bit-problem-on-windows

You can point Max exactly to which file you want by sending the vst~ object the message "plug" into its left inlet. It will open a folder and let you choose exactly which DLL file you want. Is this what you mean?

half of what I mean (thanks so far). In Plogue Bidule (a software somewhat similar to Max) I can simply specify a folder in the general settings that contains all 64bit plugins and it then offers me a list to choose from (it even differentiates automatically between instruments and effects). I can't believe that Max cannot do that

> Is this what you mean?

half of what I mean (thanks so far). In Plogue Bidule (a software somewhat similar to Max) I can simply specify a folder in the general settings that contains all 64bit plugins and it then offers me a list to choose from (it even differentiates automatically between instruments and effects). I can't believe that Max cannot do that

nothing in max automatically refers to the default locations for VST32 and VST64 in windows, and nothing will default to a random folder, either.

however, you can always program that stuff yourself. 

objects like [folder] or [ubumenu] will be of help to create a list of files inside a folder. since on windows plug-ins basically must have an extension, you could then filter by name to get only the .vst files listed.

including plug-ins which are in subfolders can be reached with a similar method, where you first filter for "type folder", then list all of the files in these locations.

same with number of outlets of vst~; doesnt work automatically, but is possible to implement it.

you might find it silly that the mandatory locations

C:\Program Files (x86)\Common Files\VST3 

are not found and used by the vst objects itself, but we call it flexibility.


nothing in max automatically refers to the default locations for VST32 and VST64 in windows, and nothing will default to a random folder, either.

however, you can always program that stuff yourself. 

objects like [folder] or [ubumenu] will be of help to create a list of files inside a folder. since on windows plug-ins basically must have an extension, you could then filter by name to get only the .vst files listed.

including plug-ins which are in subfolders can be reached with a similar method, where you first filter for "type folder", then list all of the files in these locations.

same with number of outlets of vst~; doesnt work automatically, but is possible to implement it.

you might find it silly that the mandatory locations

C:\Program Files\Common Files\VST3
C:\Program Files (x86)\Common Files\VST3 

are not found and used by the vst objects itself, but we call it flexibility.


As first you must delete the max vst scans.

On windows plugscanner seems not to update paths to plugins if

they changed location or type (32 or 64 bit for example).

There are no fixed rules for plugin location in windows

even companies like NI install their baggage to own folder and tell user to move

plugins to whatever proper location should be, silly.

Or simply use plug message to load plugin from wherever you want

As first you must delete the max vst scans.
On windows plugscanner seems not to update paths to plugins if
they changed location or type (32 or 64 bit for example).
There are no fixed rules for plugin location in windows
even companies like NI install their baggage to own folder and tell user to move
plugins to whatever proper location should be, silly.
Or simply use plug message to load plugin from wherever you want
and store absolute path for the future.
Only drawback is with shell type plugs


there is a fixed rule in the VST3 license agreement. :) but i also prefer custom folders, like him.

VST 32/64 bit problem on Windows