Here's an example of how you can use the xtor manager with the xtor system:
It saves presets with this template: prefix000.xtor. "000" is the preset number padded with up to two zeros, so you can use from preset 000 to 999.
All the inlets are optional, but, if you need to have multiple presets, you have to pass it a preset number, and, if you need to have multiple preset managers or multiple patches in the same folder, you need to pass it a prefix. You can use the inlets or the embedded buttons to save and load presets. They all work when the button goes from 0 to 1. It displays the last preset used at the bottom.
Finally, the params attribute decides the maximum number of parameters that can be saved. Generally, you don't need to worry about it and you can set it as high as you want without performance penalties, but, if you are having memory problems, you can save a little memory by reducing it the most you can. Most of the time you shouldn't care, it caches very little data, I only added it for some very extreme cases.
Right now it doesn't have a way to control it with midi directly in the object. Should I add midi controls to it? I should, shouldn't I? Or shall I add a separate midi controller object that connects to its inlets? I don't use midi cc or program normally, so I don't know which has better usability. Maybe it should be a separate xtor manager? I wonder...
Also, it doesn't have an audio fade outlet because I haven't had any glitches or drops. It caches some of the calculations that the preset manager does and avoids some others, that's on top being able to limit the parameters saved and also being in another thread, so it's faster. Yet, if someone has problems with glitches, I'd be happy to put it.