ArrayArrayArrayArrayArray BrainModular BrainModular Users Forum 2021-12-30T03:25:59+02:00 https://brainmodular.com/forums/app.php/feed/topic/6935 2021-12-30T03:25:59+02:00 2021-12-30T03:25:59+02:00 https://brainmodular.com/forums/viewtopic.php?t=6935&p=43843#p43843 <![CDATA[Re: Plugin Manager / presets]]>
Hello,

In HH5, you can save your presets list as a text file and reload it with or without confirmation. I think it could be a good solution for you, same preset file for all your plugins, with the address as a text input and a trigger "on initialisation" and you always recall the good preset.

If you do not understanding, I can share a little patch.

Sylvain
This does not work. There is no confirmation required for the file name, but the IDs inside that preset file
do not match elements in the patch you are trying to load into.
If would need special Polyphony support to allow this between subpatches with polyphony.
I have raise a new suggestion for this.

Thanks,
Simon.

Statistics: Posted by sm_jamieson — 30 Dec 2021, 02:25

]]> 2021-12-29T21:50:48+02:00 2021-12-29T21:50:48+02:00 https://brainmodular.com/forums/viewtopic.php?t=6935&p=43839#p43839 <![CDATA[Re: Plugin Manager / presets]]>
But I realised/hoped I could just use the plugin manager to save the current patch (as .fxp file). This might store the whole current state of the VST.
I can then load this fxp file in another VST instance and I have copied the state. This works with Omnisphere, and the midi mappings are transferred.

I looked in the FXP file generated by Omnisphere and seems to be a small binary header and then an XML dump of the current multi, so basically the
same as saving a multi. When the FXP is loaded, it imports the midi mappings but ignores the "import midi mappings with multi" setting, which is
solving the exact problem I had, since this menu setting kept going missing.

But I suppose what is actually stored in an FXP file is up to the VST concerned.

Simon.

Statistics: Posted by sm_jamieson — 29 Dec 2021, 20:50

]]> 2021-12-17T13:58:22+02:00 2021-12-17T13:58:22+02:00 https://brainmodular.com/forums/viewtopic.php?t=6935&p=43818#p43818 <![CDATA[Re: Plugin Manager / presets]]> When I get the time ...!

Statistics: Posted by sm_jamieson — 17 Dec 2021, 12:58

]]> 2021-12-17T10:31:31+02:00 2021-12-17T10:31:31+02:00 https://brainmodular.com/forums/viewtopic.php?t=6935&p=43814#p43814 <![CDATA[Re: Plugin Manager / presets]]>
In HH5, you can save your presets list as a text file and reload it with or without confirmation. I think it could be a good solution for you, same preset file for all your plugins, with the address as a text input and a trigger "on initialisation" and you always recall the good preset.

If you do not understanding, I can share a little patch.

Sylvain

Statistics: Posted by SylvainT — 17 Dec 2021, 09:31

]]> 2021-12-17T02:44:39+02:00 2021-12-17T02:44:39+02:00 https://brainmodular.com/forums/viewtopic.php?t=6935&p=43813#p43813 <![CDATA[Plugin Manager / presets]]> When these various instances are stored in a preset the plugin state is stored and restored when the preset is recalled.
However, I used midi control of some plugins and I want them to all have the same state when the workspace is opened,
i.e. for them to be clones of each other.
If I copy and paste a plugin or a patch containing a plugin, this is what happens - they have the same internal settings.
I would like a way of doing this without having to edit the patch.

I think this could be done with polyphony in some way. So the cloned "voices" of the patch could effectively share the same preset.
You would need a new setting to designate a "master" voice whose preset would be saved, since they cannot all save to the same
preset. On loading a workspace all these polyphony patches would load the shared preset and be in exactly the same state.
The preset manager would also have to be able to reload all the polyphony voices from the same preset.

How would this be used ?
It you create a new preset or change some common setting in one instance of a plugin, you have to save the setting in the
plugin (as a new patch, multi or whatever) and then go into the GUI of each plugin and reload, which is a real pain.
With the new feature, you save the plugin patch to a Usine preset, then reload all the polyphony patches from the shared preset
and it's done !

Simon.

Statistics: Posted by sm_jamieson — 17 Dec 2021, 01:44

]]> BrainModular BrainModular Users Forum 2021-12-30T03:25:59+02:00 https://brainmodular.com/forums/app.php/feed/topic/6935 2021-12-30T03:25:59+02:00 2021-12-30T03:25:59+02:00 https://brainmodular.com/forums/viewtopic.php?t=6935&p=43843#p43843 <![CDATA[Re: Plugin Manager / presets]]>
Hello,

In HH5, you can save your presets list as a text file and reload it with or without confirmation. I think it could be a good solution for you, same preset file for all your plugins, with the address as a text input and a trigger "on initialisation" and you always recall the good preset.

If you do not understanding, I can share a little patch.

Sylvain
This does not work. There is no confirmation required for the file name, but the IDs inside that preset file
do not match elements in the patch you are trying to load into.
If would need special Polyphony support to allow this between subpatches with polyphony.
I have raise a new suggestion for this.

Thanks,
Simon.

Statistics: Posted by sm_jamieson — 30 Dec 2021, 02:25

]]> 2021-12-29T21:50:48+02:00 2021-12-29T21:50:48+02:00 https://brainmodular.com/forums/viewtopic.php?t=6935&p=43839#p43839 <![CDATA[Re: Plugin Manager / presets]]>
But I realised/hoped I could just use the plugin manager to save the current patch (as .fxp file). This might store the whole current state of the VST.
I can then load this fxp file in another VST instance and I have copied the state. This works with Omnisphere, and the midi mappings are transferred.

I looked in the FXP file generated by Omnisphere and seems to be a small binary header and then an XML dump of the current multi, so basically the
same as saving a multi. When the FXP is loaded, it imports the midi mappings but ignores the "import midi mappings with multi" setting, which is
solving the exact problem I had, since this menu setting kept going missing.

But I suppose what is actually stored in an FXP file is up to the VST concerned.

Simon.

Statistics: Posted by sm_jamieson — 29 Dec 2021, 20:50

]]> 2021-12-17T13:58:22+02:00 2021-12-17T13:58:22+02:00 https://brainmodular.com/forums/viewtopic.php?t=6935&p=43818#p43818 <![CDATA[Re: Plugin Manager / presets]]> When I get the time ...!

Statistics: Posted by sm_jamieson — 17 Dec 2021, 12:58

]]> 2021-12-17T10:31:31+02:00 2021-12-17T10:31:31+02:00 https://brainmodular.com/forums/viewtopic.php?t=6935&p=43814#p43814 <![CDATA[Re: Plugin Manager / presets]]>
In HH5, you can save your presets list as a text file and reload it with or without confirmation. I think it could be a good solution for you, same preset file for all your plugins, with the address as a text input and a trigger "on initialisation" and you always recall the good preset.

If you do not understanding, I can share a little patch.

Sylvain

Statistics: Posted by SylvainT — 17 Dec 2021, 09:31

]]> 2021-12-17T02:44:39+02:00 2021-12-17T02:44:39+02:00 https://brainmodular.com/forums/viewtopic.php?t=6935&p=43813#p43813 <![CDATA[Plugin Manager / presets]]> When these various instances are stored in a preset the plugin state is stored and restored when the preset is recalled.
However, I used midi control of some plugins and I want them to all have the same state when the workspace is opened,
i.e. for them to be clones of each other.
If I copy and paste a plugin or a patch containing a plugin, this is what happens - they have the same internal settings.
I would like a way of doing this without having to edit the patch.

I think this could be done with polyphony in some way. So the cloned "voices" of the patch could effectively share the same preset.
You would need a new setting to designate a "master" voice whose preset would be saved, since they cannot all save to the same
preset. On loading a workspace all these polyphony patches would load the shared preset and be in exactly the same state.
The preset manager would also have to be able to reload all the polyphony voices from the same preset.

How would this be used ?
It you create a new preset or change some common setting in one instance of a plugin, you have to save the setting in the
plugin (as a new patch, multi or whatever) and then go into the GUI of each plugin and reload, which is a real pain.
With the new feature, you save the plugin patch to a Usine preset, then reload all the polyphony patches from the shared preset
and it's done !

Simon.

Statistics: Posted by sm_jamieson — 17 Dec 2021, 01:44

]]>