Confused about program numbering and duplicate entries on receive bank.

[tomphillpotts]

I'm trying out the Take 5 and Teo-5 panels. They are excellent!
Things mostly seem to work well. There's a small layout issue on the TEO-5 panel, I know it's in testing still. Happy to assist if I can!

I want to use these mostly to organize the presets on the synth into categories so I can find presets more easily.
I am confused about program numbering on receiving banks from the synth into the librarian, this is in the Take 5 panel.

In the Take 5 panel, when I receive user bank 1 for example, this is what I get (screenshot below).
It seems to be showing user and factory entries, which would explain the duplicates, but the numbering doesn't really make sense. So I'm wondering if there's something not working correctly here?

When I load a bank file I downloaded from the Sequential website, the presets are numbered normally without duplicates. I haven't tried sending that bank to the synth yet to see what happens.

Thanks

[synthmutt]

The bank reflects MIDI input received by Ctrlr - does your setup include MIDI hardware or software which is echoing input, causing the same SysEx program dump to be received twice (even though only sent once from the hardware synth)? The MIDI Monitor within Ctrlr can be used to view what's being received. Take 5 programs are over 4600 bytes, so if being duplicated, that's a lot of extra MIDI data.

Banks in this panel contain variable numbers of programs which are in the format of the SysEx edit buffer dump, without including the original bank and program number - this makes it easy to reorder programs, add or remove, insert programs from another bank, etc. When a bank is saved to file or sent to the Take 5, then the bank and program numbers are added, unless there are more programs in the bank then the Take 5 allows - then they are stored as edit buffers in a file, or when sending to the Take 5 the number of programs is limited to what it can receive in its banks.

This approach allows creating a file of hundreds or thousands of programs. Perhaps a downside of this approach is that if Ctrlr is sent the same program "80s Cali Dreamin" twice, then it stores each in successive locations 1.01 and 1.02 in the bank, rather than detecting that program 1.01 was being received a second time and overwriting the 1.01 program already saved in its bank.