Just making clear this design allows each instance to be saved with separate presets in a parent patch. Not that I find it crucial. I guess that 2 sharing the same preset bank should be fine for most cases. So using a file to load and save inside the abstraction (as it was possible before) was kinda fine. So this is where I start to think I could be compromising my beloved "KISS" principle... but I was already thinking import/export was nice to allow people to store these things in the patch rather than a file, so it's cool. It's versatile and still simple enough.