Home › Forums › General › Programming › Storing received sysex dump as memoryblock then process › Reply To: Storing received sysex dump as memoryblock then process
- Topics: 15
- Replies: 62
- Total: 77
midiMessage:getData():getByte(i) was a keypoint but error still occured.
I messed with the script and removed the “local” tag and it worked.
So everything is dumped from the unit to ctrlr every parameter are updated.
I have to think about a way to add a timer between sent messages because the unit is cluttered rapidly.
Everytime a message is received, processed and complete the unit send an acknowledge “error” message telling the unit is ready for operation again.
Message received is (my commented console report) :
LUA>> Displays the RAW Received Midi Message LUA>> f0 0f 40 00 00 02 00 f7 LUA>> Displays the Received Midi Message Type in decimal LUA>> 2 LUA>> Displays the MessageErrorCode in decimal LUA>> 0 LUA>> 0 Meaning TX over - Ackowledge (ACK) - No Error
So I’ll think about a way to wait the ACK message for sending new message to avoid cluttering the input of the DP4.
Thanks a lot for all your help! I deeply appreciate the support.