listing vst plugins in umenu

    Feb 17 2010 | 1:09 pm
    Hi all,
    I'm new to max/msp, and I'd like to ask questions to hard-core vst fans for setting up patches using vst.
    I'm currently trying to list bunch of vst plugins (xxx.vst) located in user's library folder (~/Library/Audio/Plug-Ins/VST) in umenu using 'folder' object. I'm able to list text files located in this directory, but for some reason I don't see the vst plugin files. Is there a way to list vst plugin files in umenu? or since plugins are bundles, max/msp is not considering these as a file? (thinking it's a folder?)

    • Feb 17 2010 | 2:10 pm
      It you send folder the types message, it should work.
    • Feb 17 2010 | 3:01 pm
      Hi patrick!
      Thanks for the reply. So for the types message, will it be "BNDL"? or "VST" I kinda tried it out, but no success... probably I need to climb up the learning curve a bit more.
    • Feb 17 2010 | 4:14 pm
      One quick way to check on the file type is to open the help file for the dropfile object and then actually drop a .vst plug-in device onto it. You'll see the file type sent out the right outlet of the dropfile object, I believe. Don't know if that'll fix your problem, but it's worth a try.
    • Feb 17 2010 | 4:49 pm
      try this !
    • Feb 18 2010 | 5:53 am
      Thanks everyone!
      After couple tries and asking people, I was able to get Guillaume's patch running in my environment. Great! Just what I was trying to do!
      Now off to more vst loading....
    • Oct 22 2011 | 9:04 pm
      Thanks Guillaume,
      after 1 year, it's still very useful !
    • Dec 13 2011 | 6:06 pm
      I tried this, and have it filling the menu, but even with prefix mode set to ignore I still get the full path from inside the vst folder, as well as the extension, i.e. ["compressors and limiters"/"mega comp"/megacomp.dll]
      Is there a simple way to extract just the file name from the full string? I imagine there are third-party string tokenizers, etc. that could be used, but I wondered if max had a simple native way of doing this, given that is what the vst~object seems to require.... I haven't found a lot of string manipulation objects in the library.