Forums > MaxMSP

VST preset change for AU

Oct 08 2012 | 2:42 pm

I am porting a patch from Max 5 to 6. I have an Audio Unit plug in with an instrument that has many presets. In my original patch, I had a message box with a number, refering to the preset which worked well. The old audio units seems to be different,because when I want to change preset now, with a message box carrying a number the preset does not change. Could I have some help to know how we address preset changes for audio units plug ins please.

Oct 09 2012 | 11:58 am

Is there nobody who uses vst as an audio unit plug in who could say why I do not get a preset change sending a number from a message box?
I use an OrangeVocoder which has 60 presets. In the prvious version all presets got listed in an ubu menu. This is now been changed, but I can not change presets anymore. Please tell me what is wrong.

Oct 09 2012 | 5:07 pm

Hey Hans,

Does it work if the plugin editing window is open? I’ve been struggling with preset recall for two specific VSTis recently, and one peculiarity of both of them is that they won’t respond to programme change messages unless their interface windows are open (they don’t need to be front-most though).

Oct 09 2012 | 5:48 pm

Hi David,

I am glad there is someone!!

Under Max5 there was a ubu menu which loaded all the presets. after they had been loaded you coud just use a message box with a number inside, press it and the preset would change! When I load the Orange Vocoder under the Max help for VST, I can set a number box and connect it to the first input on the left, but nothing changes when I send the number. There is no other indication on what else to do to change presets. How does it work now? We have to ask Timothy!

Oct 09 2012 | 8:39 pm

I think you may be right there.

I mentioned this problem to the plugin developer and he told me that their plugins use 2 different methods of recalling presets depending on whether the edit window is open or not (I can’t say more than that as this is now totally out of my area of expertise. I’ll paste his reply below in case it’s in any way enlightening). Which is why I suggested you try recalling presets with the interface open. But if that still doesn’t work, then I’m afraid I’m flummoxed. However, recalling presets with the edit window closed did work for me in max5, so _something_ has changed.

I wish the vst~ object worked just like a vst loaded into a sequencer channel (ie it stored and managed the various states of the plugin). Maybe it does, but it doesn’t do as much, as easily. Maybe there’s a reason…

Here’s that reply.

About the program change not taking place, well I need to become technically here, can be if the host does not supply an "idle" call, that is, when nothing else is to do the plugin gets time to update itself (e.g. in responce to a program change request). However, I never heard of any host not doing so. If the GUI is open we have an alternative way of processing the program change. However, if we neither have our GUI being active, not getting any time to process … we’re lost (as I said, never had that case so far).

Oct 09 2012 | 9:50 pm

Here’s partial solution in the patch below. Couple of problems- the plugins menu does not update to reflect the new patch selected from the Max window, although you can see the parameters change in the plugin window. Secondly not all the presets in the plugin menu respond to patch change or show up in the presetnames dump, such as the Jingle preset.

-- Pasted Max Patch, click to expand. --

Oct 10 2012 | 1:26 pm

Hi Rick,
this is a work around which unfortunately does not help me, because I want to use an OHM64, as a controller. The OHM has plenty of buttons, which I want to assign to presets. I tried to send a number with a message box to the object, but it does not change anything. As you said the plug in does not write the new preset in the window. Thanks for the patch. We might have to ring the bell at Timothy’s door…..


Oct 10 2012 | 4:12 pm

You know you can sent a number to the umenu right?

-- Pasted Max Patch, click to expand. --

Oct 14 2012 | 1:23 pm

Thanks Rick!! It would do the job for a start. I wonder if we get some feedback from cycling on this issue.
Cheers Rick, great.

Oct 19 2012 | 12:11 pm

Hi Rick,
I trying to control a parameter which is chosen by the umenu, but I do not know what to do to address it? Any idea how to control a parameter?

Oct 19 2012 | 8:30 pm

Here’s one way.

-- Pasted Max Patch, click to expand. --

Nov 13 2012 | 1:15 pm

HI Rick,
I was disappointed to see that 6.08 had no changes for the vst object.

I am working on the patch again and I have problems controlling parameters with an external controller. Could you download NorthPole from Prosoniq, it is free and see if you can address parameters, please?

Nov 13 2012 | 2:26 pm

It seems to work if you use the parameters numbers instead of their names. So 4 $1 instead of Distortion $1 does work (on my computer under X.6.8 and latest Max). Not sure it’s a Max problem.


Nov 14 2012 | 2:39 pm

Yes, Patrick how did you figure that one out?! It is not elegant, but I can keep building the patch. Thanks!!!

Nov 14 2012 | 2:56 pm

I’m currently working on a project using the Crystal plugin (also free) which has ±256 parameters, but almost none of them have their names exposed (only numbers), so I’m used no work in less elegant ways ;-).

If you want more elegance, you could use a coll to map the parameters names to their numbers.


Nov 14 2012 | 8:49 pm


This might help you understand how it works.

In Max clear your Max message window. Hit the param message box in the patch below. You’ll notice that Distortion is number 4 in the list, Cutoff is number 2 etc…

Where the parameter name appears in the list is the same as its parameter number.

-- Pasted Max Patch, click to expand. --

Nov 14 2012 | 9:54 pm

Thanks Rick, it works fine now. I can live with this. I got four computers running a network now…….The octopus performer. Cheers

Viewing 17 posts - 1 through 17 (of 17 total)

Forums > MaxMSP