I hear MIDIBox_NG is 10x slower in scanning the keyboard matrix than MIDIBox_KB.
Is this ONLY due to the amount input scanning? If I upload MIDIBox_NG and edit the configuration file so that only 2 in/out shift registers are used, will it match the speed of MIDIBox_KB?
I want to build a controller w/ 61-key Fatar keyboard (I’ve already built it and it works - mostly; more on that later) but I also want to use only a couple of buttons and LEDs (octave up/down keys with indicators etc) in addition to the keyboard. If I chain another DIO_MATRIX module and build a second matrix for LEDs/buttons, then configure MIDIBox_NG to use only 4 in/out shift registers will I achieve something between the performance of MIDIBox_KB and MIDIBox_NG? I don’t want to add a second CORE_STM32F4 module just for a couple of buttons and LEDs, but I am not feeling great with the ~3ms scan time of MIDIBox_NG (I also didn’t like the quantization in velocity values; 50-1000 “delay value” is a much more detailed range than 5-100, the latter isn’t enough, not even for the full 8-bit range of 128 values that MIDI supports (at least not without using velocity mapping - unless I am doing something wrong)
EDIT: read some of the .NCG configuration examples of the documentation, the answer is right there:
Quote
reduce number of SRs for faster scan
with 2 SRs the scan takes ca. 500 uS instead of 2.5 mS
SRIO num_sr=2
however, delay values are still in the same range, although I’m now able to get less “stepped” velocity values
My tests with NG vs KB had the result that no matter what I change in the official NG-app, I’ll never get those fine velocity steps, that KB gives. So I created my own NG app and kicked out all of the functions, I do not need. There is a thread about it in this forum. Just use the search engine and you’ll find it quick.
Anyway: I still feel, that KB outputs more velocity values as my NG does still. So I think it depends on your needs.
Btw: please be aware, that there is no octave shift function (regarding if NG or KB) yet
Thanks for the info! I’m just getting started on the project, still learning the NG platform. There is a transpose parameter in EVENT_KB event, so I thought it would be possible in some way, with all the scripting capabilities of the software and whatnot:
|
kb_transpose=<-128..127>
|
Anyway, I could always just send a MIDI CC with the octave shift buttons and let the host software do the transpose.
My tests with NG vs KB had the result that no matter what I change in the official NG-app, I’ll never get those fine velocity steps, that KB gives. So I created my own NG app and kicked out all of the functions, I do not need. There is a thread about it in this forum. Just use the search engine and you’ll find it quick.
Anyway: I still feel, that KB outputs more velocity values as my NG does still. So I think it depends on your needs.
Btw: please be aware, that there is no octave shift function (regarding if NG or KB) yet
Hi
since i couldn’t find the mentioned thread, could you please post a link or thread title?
I’m currently deciding between NG vs KB for a masterkeyboard project. It looks like you can’t have buttons and displays with KB, so i’m intrested in a fast(er) scanning NG version.