Hey all, I’ve just got a meta module and I am having a bit of trouble with knob mappings (jack mappings seem fine?).
I power on the module, spend about 10-15 minutes mapping panel knobs and MIDI buttons/knobs to the knobs in my patch. I press the save icon. Have fun for a good while.
The next day I power on and things have been automapped (I guess) and nothing is consistent. Nothing has been saved. Everything is just mapped up to random stuff.
This is on the latest firmware as I updated yesterday.
Am I doing something wrong here? Do, I need to specifically save a knob set (rather than hitting the save button on the patch). I don’t see an option for this?
Any assistance would be great
Edit: Just for some additional clarity, this is a module that I have compiled myself. It is stored on the SD card. So, when I first loaded it, I used the scan plugins option. I then selected the option to preload this plugin. (perhaps this is overwriting the saved data?).
Mappings are stored exclusively in the patch yml file. First, I would just sanity check and make sure you don’t have multiple versions of the patch file (on SD card, internal flash storage, or USB drive, including sub-folders).
If you’re compiling your own plugin, perhaps a different version of the plugin got loaded? Pre-loading will scan the root directory and the metamodule-plugins/ directories of both SD Card and USB drive, and it will load what it thinks is the latest version (based on filename). If there are multiple matches with the same file name, it will silently ignore any other matches. Easiest way to make sure it’s doing what you expect is to have only one .mmplugin file that begins with your plugin slug on any the disk that’s inserted at startup.
One useful thing to help debug is to look at the patch yaml file. The mappings are based on the param ID, input jack ID, and output jack IDs. So if those IDs changed in your plugin then when you reload the patch file, all the mappings will be wrong. To help debug you could open the yaml file in a text editor and see if the param and jack IDs match what your plugin is using and/or match what you expected the mappings to be.
Also you can manually edit the patch yaml file if you want to test if loading a patch with particular mappings is working.
Appreciate the response! I just had a look at the SD card and I had two .yml files for the same patch, one suffixed with 2. I deleted that. Unfortunately it was probably the one with the mappings I want However, on editing the loaded patch and saving again, then power-cycling. It looks like the mappings have been saved!
Thanks for the help, i’ll keep an eye on this in the future
And just for clarification, the name the MM looks for is the filename entered /saved by the MM Hub on your PC in the “Enter Patch Name” field and visible within the first few lines of the YML file itself when you create the YML and not the YML filename created by the PC so opening the YML with notepad will show you the relevant filename of the correct patch.
However, on editing the loaded patch and saving again, then power-cycling. It looks like the mappings have been saved!