Some problem with a Preset manager expansion patch

[gurulogic]

I have taken a go at expanding bsork's 3PM patch (1 fader controlling 3 preset managers) but I have run into issues.
The idea of this patch is that there are eight X16 preset managers connected to just one listbox and all Storing and clearing is done with only two buttons.
The problem I am having is that the preset managers are not storing in their correct slots. They do however appear to be recalling the correct slots. I have also encountered some internal error messages when clearing slots.
My initial thought was that it would be the Store&Clear Button Router sub patch that was causing the issue, but after deleting it, the behavior was the same even when storing directly from the preset manager UI.

I'm stumped! Any ideas?

http://www.sensomusic.com/forums/upload ... _test5.pat

[gurulogic]

Oh...it seems that even bsork's original 3PM patch that I expanded from doesn't store slots properly. Presets are stored to slot 0 every time.
Back to the drawing board?

edit:
correction, presets are stored properly on both patches if they are selected via the PM interfaces but not if they are selected by fader or listbox...

[bsork]

Guess I have to take a look at my add-on sometime in the near future...

...but one thing just strike me as a source of your problem: Is the fader or list box stored with the preset? It shouldn't...

[gurulogic]

nope,neither the fader or listbox are stored as part of the preset. If Senso made one big preset manager (X128) then this would be way easier and probably quite a bit lighter on the system
Before someone points out the Conductor to me, I already understand the Conductor functionality but I am looking to have extensive sub patch preset control in conjunction with the Conductor, ie: I am looking to have 128 recallable presets via the preset manager per specific sub patches within 128 master Conductor presets. (one per midi CC value)

I have just tried moving the three preset managers in the 3PM patch to a subpatch and cabling them with data inlets from the dispatch to the sub patch and the behavior is the same so all I can think is that one preset manager must be storing values received at the recall inlets on the other preset managers or else presets recalled with the recall inlets are not seen correctly by the store function. Is this possible?