Save plug-in midi controller mappings

[gpkcaminha]

Is it possible to save the midi assignments for a given plug-in, so that if I load another instance of it in the same or a different project I can load them? I know I can save a handful in the control surface settings section but that's only the first few parameters, which is not enough and different plug-ins will have different mappings.

[Watchful]

Try saving it as a preset. Ideally, name the track something memorable for yourself and then save the whole track as a preset. This allows you to save, reuse the settings as well as create variants for yourself. Waveform's presets function is a massive time saver and I keep finding more uses for it.

[gpkcaminha]

Try saving it as a preset. Ideally, name the track something memorable for yourself and then save the whole track as a preset. This allows you to save, reuse the settings as well as create variants for yourself. Waveform's presets function is a massive time saver and I keep finding more uses for it.

Good idea, I had some high hopes for it but it doesn't seem to work. Waveform is not preserving MIDI Controller Mappings when I save presets. I tried saving the whole track, track plugins, and even tried putting the plugin inside a rack and saving the rack (would be so cool if this one worked), but none of those are preserving the mappings.

[Watchful]

Sorry to hear.

As an aside, this may not be a Waveform issue (although it could be). Arturia's Pigments, for example, doesn't honor all of its own mappings: the plugin disregards a couple made in the standalone version. Peter Widdecombe recommended I put a MIDI monitor before Pigments, and we were able to see that Waveform was passing the CC information to the plugin, but Pigments itself was ignoring it. Very frustrating but nothing Waveform was doing wrong.

[gpkcaminha]

Sorry to hear.

As an aside, this may not be a Waveform issue (although it could be). Arturia's Pigments, for example, doesn't honor all of its own mappings: the plugin disregards a couple made in the standalone version. Peter Widdecombe recommended I put a MIDI monitor before Pigments, and we were able to see that Waveform was passing the CC information to the plugin, but Pigments itself was ignoring it. Very frustrating but nothing Waveform was doing wrong.

Hmm I see but I believe this is on Waveform's side, since it applies to any plugins (including e.g. Biotek2 or Collective which were the ones I tested). I think MIDI controller mappings are stored on Waveform, just like things like Faceplate configs etc. I just can't seem to save the mapping for reusing in any way... Could be useful for for example mapping Biotek's macro controls and reusing that mapping on other instances of Biotek2. It makes no sense that I'd have to remap like 20 knobs every time I want to use my controller with it for those macro controls...

[Watchful]

We'll need either FigBug or DRowAudio to comment. I am, like you, under the impression that this is live data that can be--and should be--stored with with the presets or with the project file.