Please expose Presets to the DAW

[rod_zero]

The last Ableton Live update, 9.5, allows for Push1 and the new Push2 to browse presets from the controller but only if the VST exposes its presets to the DAW.

U-he are some of the few plug ins I use, and DIVA the one I use more, my favorite instrument by far.

I know there might be technical reasons why this is not done, but hope it can come someday.

Thanks

[Urs]

Coincidentally we're working on ways to batch-convert presets. I reckon that presets need to be converted to .fxp to be visible for Live.

[rod_zero]

So the batch-convert will do it? or it is just a first step? either way very happy to read you guys are working on it.

[Urs]

I suppose a batch convert will do it. I don't know any other way to expose presets to hosts.

[EvilDragon]

Well, some plugins expose the whole banks of presets to the host in the preset browser (example: Synth1 has an option to do it, LinPlug plugins, etc.)...

This is all probably moot with VST3 though.

[Sahul]

I love the way NI Reaktor implements this feature (at least, in Cubase): as soon as you load a particular instrument inside of Reaktor, it exposes its presets to the host. If you then select another different bank of sounds, then those sounds will be automatically exposed, and so on. Really handy if you have an external controller that allows you to switch between patches with a key (Nektar Panorama, in my case), and no conversion needed.

[Cyoon]

Coincidentally we're working on ways to batch-convert presets. I reckon that presets need to be converted to .fxp to be visible for Live.

will that include .h2p to .bwpreset conversion?

[jdoo]

You can also expose presets from most any software instrument in Logic Pro.. (auinstrument format, channel strip, or as a patch). Doesn't help the OP Abelton question .

[jipumarino]

Regarding Push 1, according to https://www.ableton.com/en/help/article/push1-live95/:

It is now possible to load VST and AU plugins. Hotswapping plugins with Push enables browsing the plugin's presets (AU only).

With this in mind, I wrote a script for converting all .h2p U-He patch files into .aupreset files, which are now browsable in Live. There are actually two ways to browse and load presets from my Push 1 (which are equivalent to the ones available in the Live UI) now:

1. Go to Places → Plug-ins, where I have my plugin presets sorted by folder, including the original folders in U-he plugins.
2. Go to the new Plug-ins category and then go to the specific plugin. If it's an AU plugin, presets are shown too, but as a flat list.

I can share the script (or even the preset themselves) if it's OK with Urs.

[SaganTech]

I don't know any other way to expose presets to hosts.

For VST2.x:

struct AEffect* m_AEffect; // Pointer to the plug-in's AEffect structure

m_AEffect->numPrograms

[Urs]

I don't know any other way to expose presets to hosts.

For VST2.x:

struct AEffect* m_AEffect; // Pointer to the plug-in's AEffect structure

m_AEffect->numPrograms

Well, our "program banks" consist of 1 program. That's because one cannot support the bank paradigm consistently across multiple plug-in formats. VST3 doesn't have it, neither has AAX, AU has only readable presets and VST2 has writable ones.

The bank concept is hilarious and dated. It was good maybe for synths like Neon and Model E, but if we were asked to support it, we can make a poll:

[ ] support preset banks
[ ] improve preset browsing with search, tagging and smart folders

you have one choice.



(banks pretty much add too much complexity to modern ways of preset management to make this viable. IMHO it's either or)

[Urs]

I can share the script (or even the preset themselves) if it's OK with Urs.

Sure, I wouldn't mind it (just don't share 3rd party preset banks without author's consent)

[rod_zero]

I like to use VSTs more right now because I move between Mac and PC, I will give ti a try to AU soon and see if it's worth the hassle to switch.

By the way, what do you guys refer as banks? banks of 127 presets which respond to MIDI program change as in the MIDI program folder in u.he plug ins?

[jipumarino]

Sure, I wouldn't mind it (just don't share 3rd party preset banks without author's consent)

Thanks, Urs. Just to be sure: can I share all of the presets that come with the plugins by default?

Here's the script: https://github.com/jipumarino/presets2aupreset

You should create a config.yml file with the right paths and then run it like this:

Code: Select all

presets2aupreset.rb Diva

[jipumarino]

By the way: until last week I used a very similar script which converted presets to .adg (Live Rack) files. This works for VSTs too.