ABP Electronics

Hi Thorsten, Thanks for your reply. I solved the problem with midi Note OFF - this was strange. Looks like MidiBox doesn't like DIN /DOUT modules which are not fully connected to buttons / Leds in a chain between modules fully connected. In example chain like this Midibox->>DIN (all pins connected)-->>DOUT(all pins connected)->> DIN (only few pins connected)->>DOUT (all pins connected). Now I have DIN/DOUT modules which are not connected / assigned at the end of a chain . It cured the problem with midi note OFF messages. I also had some Leds flashing a bit before this change (like 10% of the full brightness). It also stopped after I put partly assigned DIN/DOUT at the end of chain. I have added SRIO debounce_cycles=0 to my .ngc file. Unfortunately it didn't help with multiple (4) different note on/off being sent when I press 1 button. It works fine on version 1.031. Regards, Bartosz

Hi, Here is a quick description of a problem. I recently updated my midiBOX NG to version 1.032. PROBLEM 1. I am using 20 notes pedal board, here is a configuration: # Pedal BOARD MATRIX EVENT_BUTTON_MATRIX id= 1 button_matrix_mode=OnOff type=NoteOn chn= 16 key=24 range=0:64 ports=1000100000001000 # DIN_MATRIX hardware DIN_MATRIX n= 1 rows=4 inverted_sel=0 inverted_row=0 mirrored_row=0 \ sr_dout_sel1= 7 sr_dout_sel2= 0 sr_din1= 7 sr_din2= 0 After installing v 1.032 pedal matrix stopped working correctly. Every time I press 1 button - I always got 4 notes on / off at the time. I have tested different different sr_dot / sr_dout - same problem. I also made short 1 wire connection DinOUT/ DinIn - even in this situation I have 4 notes on/off when 1 pin from in is connected to single pin from out. Looks like every pin on sr_out sends output for all 4 rows. When I change to rows=8 - I get 8 notes on/off at the same time. Desperately I changed back to v 1.031 - problem doesn't exist in version 1.031 - everything works as expected. PROBLEM 2. I have 2 x 61 notes velocity keyboards connected... Configuration script: # KEYBOARD hardware KEYBOARD n=1 rows=8 dout_sr1=1 dout_sr2=2 din_sr1=1 din_sr2=2 din_inverted=0 break_inverted=0 din_key_offset=32 \ make_debounced=0 \ scan_velocity=1 scan_optimized=1 note_offset=36 \ delay_fastest=5 delay_fastest_black_keys=0 delay_slowest=100 KEYBOARD n=2 rows=8 dout_sr1=3 dout_sr2=4 din_sr1=3 din_sr2=4 din_inverted=0 break_inverted=0 din_key_offset=32 \ make_debounced=0 \ scan_velocity=1 scan_optimized=1 note_offset=36 \ delay_fastest=5 delay_fastest_black_keys=0 delay_slowest=100 EVENT_KB id=1 type=NoteOn chn=15 key=any use_key_number=1 range=0:127 kb_velocity_map=map1 ports=1000100000001000 EVENT_KB id=2 type=NoteOn chn=14 key=any use_key_number=1 range=0:127 kb_velocity_map=map1 ports=1000100000001000 Sometimes (very randomly) when key is pressed and hold down (note ON) all the sudden my midibox sends note OFF. It can send midi note Off message few times - only for notes which are still hold down. In Example - I can play C, E, G and hold these three notes.... after few seconds I will have C off..and off again and off again. Then G will go off...and so on. It is very difficult to repeat this fault - but it happens all the time. Again - problem only exist with version 1.032,...1.031 seems to be working fine. Any help or ideas would be much appreciated. :) Regards, Bartosz

Hi, I know this is strange. Here is an explanation: i am working with some software, 1 of the functions is tempo control. For some strange reasons software only allows me to assign buttons to tempo+ / tempo -. To make it more complicated: tempo + button will respond to CC x/ any value and tempo - button needs different CC y / any value. For example: tempo + = CC12/0:127, tempo - = CC13/0:127. I cant use the same CC for +/-. I think it explains the problem...which is solved thanks to TK :) Regards, Bartosz

Hi TK, Thanks for your reply. YES- problem solved with SD card. Seems like NG needs SD card to run properly. If no card present - then it loads default values. Now I have loads of buttons working, some sliders and some LED - so far it is going good. NEW PROBLEM - I am trying to set-up encoder to work following way: when turned clockwise - sends CC12 value 127, When turned anticlockwise sends cc13 value 127.... I am a bit lost with this exercise. Any suggestions? .......well, well...it is worth reading what other people write. I just have found a solution :rolleyes: . Regards, Bartosz

Hello All Midibox users, I am a complete newbie with MIDIbox, please forgive me if my question looks stupid. Here is my configuration: Mios Studio, MBHP_CORE_STM32F4, 1xMIDI IO module, 1xDIO_MATRIX module, Fatar keyboard (61 keys with velocity). My core module doesn't have SD card for now - I am waiting for a SD socket to arrive from suppliers. OS-Windows 8.1. bootloader installed ok, standard project.hex file to start with. For the moment I am trying to make my Fatar Keyboard talking to midi OUT of MIDI IO module. I started with following configuration: KEYBOARD n=1 rows=0 dout_sr1=0 dout_sr2=0 din_sr1=0 din_sr2=0 din_inverted=0 break_inverted=0 din_key_offset=32 \ scan_velocity=1 scan_optimized=0 note_offset=36 \ delay_fastest=5 delay_fastest_black_keys=0 delay_slowest=100 With this configuration I could see midi see some midi messages on midi monitor when keys were pressed / released - these messages were incorrect so I changed above configuration in Mios Studio to: KEYBOARD n=1 rows=8 dout_sr1=1 dout_sr2=2 din_sr1=1 din_sr2=2 din_inverted=0 break_inverted=0 din_key_offset=32 \ scan_velocity=1 scan_optimized=0 note_offset=36 \ delay_fastest=5 delay_fastest_black_keys=0 delay_slowest=100 and I also added: EVENT_KB id=1 type=NoteOn chn=1 key=any use_key_number=1 range=0:127 ports=1111111100000000 after above change I can't see any midi messages on Mios Studio, also Midi OUT LED doesn't flash anymore (it flashed on first / default configuration). When I enter the debug mode for KB 1 I can see on terminal all key presses working absolutely perfect with correct note numbers and correct velocity. But there is no midi Output visible at all. When debug mode is set to "off" - there is absolutely no signs of life from Fatar keyboard - looks like hw_id KB:1 is disabled. Please help me, is this happening because I have no SD card installed?? Am I missing something? Regards, Bartosz