If I turn off the Clamp Output feature of the Serial DAT, is there still a maximum number of bytes it can receive, ie. what’s the byte size of the buffer ? In the wiki it says “it can be set to anything, including unlimited” but how would I do so using Python ?
Hi Axel.
Whether or not you turn on ‘Clamp Output’ all received bytes are still processed and appended to the DAT.
That feature just controls whether or not rows are removed from the DAT after they are processed.
In terms of the actual driver buffer size, its left at default, however its defined in the operating system. We haven’t yet run into any overflow issues from this, so wondering what type of data loss are you experiencing?
Rob.
When using an I-CubeX USB-microDig at the lowest sampling interval (ie. highest sampling rate) with 4 sensor inputs active, there are a few bytes lost at the end of the buffer, each time the ScriptOp gets all the buffer data from the Serial DAT. I see this when I process the buffer and split it out in sysex messages and store them in a Table DAT. The last sysex message of the buffer is incomplete and the number of missing bytes varies randomly. When I look at the data the USB-microDig is sending with MIDI-OX (having mapped the serial port to a MIDI port with our Connect software) it doesn’t seem to be sending such incomplete sysex messages - unless MIDI-OX filters out incomplete sysex. But I also looked at the same data using Max/MSP and all sysex messages are complete.