MIDI Target Manufacturer(s):
Having set a control (Knob) to send a 'Preset Header Request' (F0) 00 01 38 00 6D 46 V (F7) where 'V' is the preset number (two byte word). I have been experimenting with how well the 'MIDI Log' handles the dialogue, I have set the number of ticks to 256, default value to 63(25% 0-63) and 'Snap To Default Value' to max of 16s. It is difficult to run a full cycle without receiving an error, which is a bit concerning for the following reasons:
<1> Maximum data throughput Tx+Rx is only 26,880 bits/16 = 1,680 bits per second. # Basic MIDI Spec = 31,250 Max
<2> The error(s) are consistent and always consist of the same (location) 6 bytes from the middle of the packet.
<3> An example of an error is as follows:
Message In: Length=6: 32 00 00 08 20 00 # Bytes 25 to 30 of the expected 32 byte packet
This is not a valid MIDI command (top bit not set), yet it is not showing as an error, while I understand that this is only dialogue and no action is required, does this mean no validation ?
<4> As I ramp up the throughput we start to lose Rx Packets completely.
I have included a copy of the MIDI log which unfortunately is limited to 80 lines, which when you take into account the Tx Request and the short length wrap-around only gives us around 26 TX/RX cycles.
Request: F0 00 01 38 00 6D 46 V F7 # 46 Request Preset Header (P)
Expected Response: F0 00 01 38 00 6D 20 PP PP 01 48 (15xAA Preset Name) (5xXX Tag+Step) F7 # 32 Bytes
Not sure if this is relevant but if MIDI Receive is set to on we seem to get more errors.
It might be worth mentioning the reason I started this in the first place, it was to extract the Preset Names in order to populate the ticks, I could then copy from the MIDI Log and then use Notepad++ to edit. Sorry if this has been a bit long winded but not easy to explain :-)