Bug in MidiboxKB?

[FantomXR]

Hey people,

 

for my keyboard project I'm not using a DIO-Matrix-Modul, but a DIN and a DOUT-Modul. I configured the KB-app like this (excerpt):

 

[9275.100] kb 1 debug off
[9275.100] kb 1 midi_ports 0x1011
[9275.100] kb 1 midi_chn 1
[9275.100] kb 1 note_offset 21
[9275.101] kb 1 rows 12
[9275.101] kb 1 velocity on
[9275.101] kb 1 release_velocity off
[9275.102] kb 1 optimized on
[9275.102] kb 1 dout_sr1 1
[9275.102] kb 1 dout_sr2 2
[9275.103] kb 1 din_sr1 1
[9275.103] kb 1 din_sr2 2
[9275.103] kb 1 din_key_offset 40

 

So... I'm wondering, that I get "Note On"s too, if I use SR 3 and 4 of the first DOUT... why that? I thought, that they were "disabled". If not, is there a chance to disable them for the first kb?
The reason why I'm asking this:
The keyscanning of my keyboard is a bit tricky and this is the only solution I can get this to work. I want to use kb 1 and the first two SRs of the DOUT to scan all C#-F#, kb2 and the other two SRs to scan all Gs-Cs on my keyboard. The DINs are the same for both kbs. But if I configure the app like this, I get two notes everytime I hit one key...

 

Thank you !

Chris

Edited October 22, 2013 by FantomXR

[FantomXR]

I solved the problem by using Midibox_NG. It seems, that it's not the same driver on NG and KB.