Saving of active presets

Official support for: meldaproduction.com
Post Reply New Topic
RELATED
PRODUCTS

Post

I spent a long time yesterday making a large active preset. I made sure I saved my work but when I reloaded only half of it had saved!
After various tests I figured out what was happening!

MXXX will not save Multiparameters unless they are assigned to a parameter.

I had started by designing the UI by naming all my parameters and grouping them with colours and using a combination of buttons, knobs, XY pad etc. All of this work was lost as I hadn't assigned all the parameters that I intended to.
Melda Production & United Plugins
Surface Studio = i7, 32gb, SSD.
Windows 11. Bitwig, Reaper, Live. MTotal.
Audiofuse, Adam Audio monitors + sub, iLoud MTM.
Polybrute, Summit, Pro 3, Tempest, Syntakt, AH2.
Ableton Push 2, Roli Seaboard Block.

Post

Also before saving an active preset make sure to save the intended Macro value by using the "use current value as default“-function, otherwise all Macros reset to 50% by default after saving or reloading the patch.

Post

Yes, both are true. As for saving the multiparameters - the plugin saves space by storing only relevant subsystems. The presets could be HUGE otherwise. So you need to attach it to something first. A multiparameter that doesn't actually affect any parameters is useless, so the engine doesn't save it.
Vojtech
MeldaProduction MSoundFactory MDrummer MCompleteBundle The best plugins in the world :D

Post Reply

Return to “MeldaProduction”