dhjdhjdhj

I recently replaced my Apple MainState system with a collection of Max patchers to handle MIDI routing, layering, splits and so forth.

Now that it is all working well, I need to make a decision whether to leverage the VST~ object to add softsynth support or whether to use an external AU/VST host and just send MIDI data to it from Max/MSP.

A key piece of functionality will be the ability to load an arbitrary set of soft synths on demand AND the ability to change the current preset of an already loaded soft synth.

I just read the "Investigations" by Gregory Taylor (very useful) and played around with his examples. The former (loading the desired VST on demand) is clearly simple but I was unable to figure out how to change the loaded "Preset" --- I was able to retrieve the "current" preset as shown in Taylor's example, but that's all.

I'd be happy to use MIDI Program Changes but I noticed the posts about issues using MIDI Program Changes with NI FM8 and it wasn't clear whether other soft synths might have similar problems (or no ability at all to respond to Program Changes)

best-approach-to-leveraging-vsts

I've figured out one problem --- the mechanism for changing presets (programs) seems to only work for some VSTs and not for others. I was trying to change the preset on the U-He ACE but that wouldn't work.

I then loaded the Crystal and it changed presets just fine.

I've figured out one problem --- the mechanism for changing presets (programs) seems to only work for some VSTs and not for others. I was trying to change the preset on the U-He  ACE  but that wouldn't work.

I then loaded the Crystal and it changed presets just fine.


Make sure the preset name is sent as a symbol.

So if the name consists of several words you may need to apply [tosymbol] first.

Make sure the preset name is sent as a symbol.
So if the name consists of several words you may need to apply [tosymbol] first.


That's exactly what I've found - some VSTi's work fine with the max commands, others can be used by dumping out their presets to a Coll and using that as the recall mechanism, a few can be controlled by midi format messages (like 144 x y for notes). But there are lots for which none of these methods will work ( and though sympathetic, the plug in makers aren't pup for doing anything about it).

So, I'd say your best bet is to use something like Rax.

That's exactly what I've found - some VSTi's work fine with the max commands, others can be used by dumping out their presets to a Coll and using that as the recall mechanism, a few can be controlled by midi format messages (like 144 x y for notes). But there are lots for which none of these methods will work ( and though sympathetic, the plug in makers aren't pup for doing anything about it).
So, I'd say your best bet is to use something like Rax.

In my experience the [vst~] object works well, for example with Kontakt and Reaktor.

The advantage is that you can process audio output directly in Max. So I wouldn't give up too early.

In my experience the [vst~] object works well, for example with Kontakt and Reaktor.
The advantage is that you can process audio output directly in Max. So I wouldn't give up too early.


Now I'm more confused. I discovered that the ACE can respond to MIDI Program Changes but you have to create MIDI patches in a particular folder. So I'll try that and see what happens.

So I can see how sending messages containing an integer will subsequently work but is it really also the case that a message can actually be a preset name and that will work independently of MIDI Program Changes?

Now I'm more confused. I discovered that the ACE can respond to MIDI Program Changes but you have to create MIDI patches in a particular folder. So I'll try that and see what happens.
So I can see how sending messages containing an integer will subsequently work but is it really also the case that a message can actually be a preset name and that will work independently of MIDI Program Changes?


I investigated both Rax and Jambalaya in the past (I have current licenses for both of them) but found them to be lacking on the MIDI processing side and so couldn't consider them as possible replacements for MainStage.

However, once I switched to using Max to handle the MIDI stuff, I took another look at Rax but frankly I don't find it to be very good nor does there seem to be a lot of support for it.

I'm also wondering whether the software part of Maschine might do the trick but there's no way to try it out to see if it can be made to change the set of loaded soft synths on demand.

If I can make the Max VST~ work reliably, that might just do the job for me.

Best approach to leveraging VSTs