Oh god, so much feedback for a work of three hours :o 
Christoffer: it seems that your MIDI interface isn’t multi client capable - so the best solution: just use “Hubis feedback cable” (freeware -> web) which allows you to create virtual connections between multiple MIDI devices. I used this really usefull tool many years before I bought a newer MIDI interface - hopefully it still works with newer Windows versions…
After the tool has been installed, you’ve 4 additional MIDI IN/OUTs. First you should remove the hardware MIDI device in your \windows\win.ini file; [logic] section. Logic should only use the virtual OUT ports. The JSynth editor should use another virtual OUT port. Now you can create virtual connections between the two virtual OUT ports and your physical OUT port with two “feedback cable” instances. It’s a little bit tricky, but it works! 
And if it doesn’t: “MIDI Yoke” in conjunction with MIDI-Ox should do the same
Ian: oh, you are right. It’s a good idea to add some simple button functions. Which could be usefull… I think one button for “dec”, another for “inc”, a button for storing patches and two others which allow to select the MIDI channel and the MIDI device number. Ok - I will support one DIN register with the next release.
Maniac: let us know about the offer from the distributor in Poland! If the offer is good, we could maybe start a centralized order, because currently a lot of people are searching for encoders.
Concerning the number of required encoders - since this is really a FAQ and I don’t want to give imprecise answers to this issue anymore, I’ve started to design a frontpanel for my surface:
So as you can see: 16 encoders are required.
Btw.: not all parameters are controlled by encoders and buttons, some are only accessible with the button/jog wheel combination at the right corner.
Btw2: all parameters will be accessible over the 4 buttons and the jog-wheel. So for people who don’t want to create a big (and expensive) surface, this will be the low-cost solution. It’s also be a nice solution for a low-cost 19" rack version 
Btw3: it’s also possible just to left out some sections - not everybody wants this big modulation matrix
Btw4: the purpose of the “assign” controllers is to assign them to internal or external (-> MIDI controller) functions.
Btw5: SID 1/2/3/4 means that it is possible to control a lot of SIDs from this panel
Btw6: the frontpanel design is preliminary
Btw7: big thanks to NothernLight who gave me a lot of inspirations for this design!
Best Regards, Thorsten.