I’ve noticed some erratic behavior when I my EN16 and BU16 attached together.
When used individually the velocity tracking of the BU16 is spotless, but as soon as I attach the EN16 some buttons stop reading high velocity values (those specific buttons only record velocity above 0 when touched very lightly).
This buggy behavior disappears as soon as the BU is used separately.
I was close to open a ticket for the BU16 thinking that the affected keys were defective…but as the module performs perfectly bu itself I assume that the problem is not hardware related and more software related.
How could I debug or solve this issue? What does motivate this behavior?
The other interesting thing is that only some buttons are affected, I can see that button 4 and 8 are the ones affected, the rest behave as expected when attached to the EN16.
Velocities with the module by itself.
Velocities with the BU16 and EN16 together. The first “0” are triggered by high velocity pushes.
This behavior has been recorder with the units plugged to a PC via USB 3.0.
Same behavior is detected when using external gear like the 1010 Blackbox via the dedicated device USB.
How are they side-by-side, which module is plugged in? Does this happen even when monitored without Editor open? Oh I can see it even happens on the Blackbox, reading comprehension…
I will attempt to replicate this in the office tomorrow.
More than reading comprehension it might be writer skills, I should have structured the post better
They are side by side, USB connected to the EN16. BU16 to the right of the EN16.
I’ve been thinking if any of my code in the EN16 might be affecting those exact buttons somehow. Is weird because if they were affected by index all the buttons on the same row should experience the same behavior.
I’ll keep thinking…
Any advance debugging technique that I could use to try to trace the chain of execution/events triggered by the button? it would be awesome if there was any way of tracing the execution somehow.
Well, you can monitor events on another module with eventrx_cb() but it will probably show the same thing as Editor.
What I was thinking is that the order of the modules could maybe cause this, but it’s unlikely. If you have the time, testing the setup where the BU16 is the one directly plugged in could be useful.
Not sure how your custom code could cause this, though I have no idea what your configuration is.
My code in the EN16 is directly setting val for elements, but is not pointing to elements in other modules, just elements from 0 to 15.
Just tested connecting the pair via the BU16 socket and in that case they velocity is recorded correctly, so seems to be only when connecting both via the EN16.
If there is any way for me to do a dump of the config of both units, let me know, happy to pass it so you can test with the same software running.
