I’ve got a patch containing one instance each of Bidoo cANARd, Sickozell sickoSampler, and Voxglitch Repeater. These are all modules that have “Load sample” options in the options menu.
When I load a sample in any of these modules on the Meta Module, a red dot does not appear on the Patch File Menu icon, suggesting that loading a sample doesn’t count as an unsaved change to the patch. Sure enough, when I choose Save from the Patch File Menu, open a different patch, and reopen my original patch, the samples aren’t loaded in the modules.
Changing something in a menu, such as loading a sample, not marking the patch as dirty is a known issue and I asked Dan if he could implement something for it a while ago (Marking a patch as needing to be saved) and he said he’d look into it so I’m sure it’ll happen eventually.
In the meantime you can just save it anyway without the dot showing and it should save the sample paths etc…
The sample modules themselves would need to read and check for that path.
Right now the samples are written for desktop computers, but they would need some re-writes to make them more orientated for the MetaModule
I just saw that on the SickoSampler, there is a menu option for “Store sample in patch”. By default this is checked, but this feature doesn’t work on the MM. So you need to uncheck this. If it’s unchecked and then you load a sample file and then save the patch, it should load that same sample file the next time you open the patch (I just tried it and it worked). Of course you’re right that the red dot won’t appear (eventually I’ll add an API for that but modules will need to opt-in to use it). You can still save the patch without the red dot and it’ll work. I also tested changing the sample and hitting save, then rebooting and it loads the right sample.
So it seems to be working. All that I can see happening is maybe there could be a feature request for @sickozell to disable this “Store sample in patch” menu option by default on the MM? Or just ignore it completely on the MM? I’m not sure it that would be a good thing or if it would mess up someone’s workflow if they intentionally checked the “Store sample in patch” box. Hmm…
To make it truly seamless we would also need some sort of system to convert paths on the computer to paths on the SD/USB. I have a few ideas, but that’s a bit OT…
On my modules when a patch is opened the previous sample should be reloaded only if the audio file is in the same previous location, whether the “Store sample in patch” option is ticked or not.
Please let me know if it’s not like this on MM hardware.
My plan is to no longer show disable the “Store sample in patch” option in the MM menu.
Oh, I see now, yes it works whether or not “Store Sample” is checked. Very nice.
I was getting confused over saving a sample that I just recorded vs. loading a sample. A limitation of the MetaModule is that there’s no Patch Storage directory (that is, createPatchStorageDirectory() just returns an empty string). So having “Store Sample” always disabled on the MM makes sense since it will always fail to write the sample.wav file to that directory when the patch is saved.
using the latest 2.0.1 firmware, and bidoo 2.0.1 plugin i had no issue w samples reloading., i created a patch on the mm using canard: loaded a sample into it. the sample reloaded fine after saving and restarting the mm. i even tried recording into canard, saving that recording wav file to sdc, then saved the patch. the recording loaded ok in canard upon restarting mm/loading the patch. maybe give bidoo 2.0.1 canard a try?