(I used mdaDX10 for testing this) Load it, select a preset and save the audiomulch project then re-open it and open up the preset list, it will show the first preset checked but the controls will reflect the preset which you saved it on.
Load a FXB bank and find a preset you like and save your audiomulch project, open up the project and that bank will not be loaded at all and it will be set to the first preset of the default bank however the controls will reflect the preset which it was saved on. Its a bit mind blowing how terrible this is.
Is there even a way to save banks of the native preset format?
When you say "native" I'm not sure if you're talking about VST programs or native AudioMulch contraption presets. These are two different things.
Right now AudioMulch has limited support for VST programs. You can load and save program banks (.fxb files), and you can switch/recall VST programs. However, because AudioMulch presets work completely differently from VST programs they do not interoperate cleanly. Thus it is recommended that you don't use VST programs, but just use AudioMulch contraption presets.
The main difference is that AudioMulch contraption presets are only saved when you click "Store". When you're editing contraption parameters you are in a separate edit buffer that is independent of any AudioMulch contraption preset. VSTs on the other hand don't have an edit buffer.. or rather, every VST program is a separate edit buffer, and you are always editing one of them (destructively) -- there is no concept of "storing" a VST program. So effectively, when you select a different VST program you are switching AudioMulch to use that as the current edit buffer.
Also, when you save an AudioMulch document, AudioMulch only ever stores the current VST parameter values (no matter what VST programme number is selected). All the other VST programs are not stored. The reason for this is that many VSTs have hundreds of programs, and if AM stored all of the programmes in every .amh file you would end up with multi-megabyte documents. It's also often very time consuming to switch a plugin to each programme and save it.
So the best solution is always to use AudioMulch presets and everything will work properly.
If you can think of a way to make AM work better keeping in mind all of the above, then I'd love to hear about it.
Note that there are a few related things that people have requested or that I'm considering for the future:
- Ability to switch VST programs from MIDI
- Option to tell AudioMulch to store all VST programs in the document
- Option to copy VST programs to/from AudioMulch presets
- VST program management window similar to AudioMulch preset popup window