IB as target for preset manager

[grego mondo]

Hello

What about IB as a target for the preset manger (so we can Use only one preset manager for all waht's in IB ...) ?


PS.
Usine, what else ?

[senso]

that's what the conductor is supposed to do?
the conductor stores all visible objects.

But more generally the association of preset/conductor has to be redesigned. I'm waiting for inspiration....

[grego mondo]

thanks for your answer.
Yes, that's what conductor does, but I use one conductor per song and one preset manager for each of my 9 effects tracks per song (where I can recall 8 preset) , so, with 20 song and one PM per track and per song : I have 20 conductors x 9 tracks wich make 180 PM in my work space ... a bit heavy
This is why I wonder If there's a way to have only one preset manger per conductor with all what's in IB as target so I can have only 20 PM in my workspace ...

thanks in advance


PS Usine is the Best !!

[woodslanding]

Olivier:

If you are rethinking the Conductor, I would have a look at reaktor's implementation of presets. Reaktor assigns a uniquely generated ID number to each storable control in a global preset.

This means that if I replace a knob with a slider in my layout, I can assign it the same ID as the knob had, and then all my presets are preserved.... Reaktor also has the ability to reorder/ compact the ID numbering, and updates the preset database when it does so. If you want a certain control to have a certain ID, you can change it, and reaktor will change the control that currently has that ID to the next available ID. So it's pretty easy to reorder and organize the IDs. In reaktor, these IDs correspond to the parameters it exposes when running as a VST. Don't know if that would make sense for Usine, as I haven't used it as a VST.....

To go one better, it would be great to have some basic editing of this file. For instance, if I changed some wiring so parameter X needed to have a different range, it would be great to be able to select this value in all the presets, and scale it, limit it, make it constant, etc. ( I did a lot of this kind of work with alesis, where they would change a preset range in the new generation of an instrument, and then I'd have to change all the factory presets from earlier machines to match the new range.... or they'd add a new parameter, and I had to find a useful value for it in each preset....) Maybe just exporting as a CSV file so you could work with the data in a spreadsheet.

Obviously the PM can store additional data about the VST. I don't know how this works at all..... I'm guessing it's a just big wad of binary data that only the VST itself knows what to do with. Still, it would be great if this could be stored in the conductor, as well as in individual PMs.

cheers,
-e