Hi, just wondered if you managed to have a look at this at all?
I found out some more info that might be useful...
When switching modes on the LP Pro (LIVE, NOTES, PGM) some system exclusive messages are transmitted:
00 20 29 02 10 2D 01
00 20 29 02 10 2F 00
00 20 29 02 10 2F 03
Looking at the LP sysex documentation these seem to be Mode selection and Standalone Layout Select which makes sense to me
Presumably this data is being interpreted by the Nerdseq somehow and causing a "last note trigger" or something similar?
I didn't think the Nerdseq could respond to sysex? Or maybe the issue is caused by something else?
The only other reference to something like this I found is from the firmware v1.21A release. In the comments I see this:
- fixed midi issue which could create a hanging note on local CV-Gate tracks in very rare situations
Is it possible this bug got reintroduced in firmware v1.22 somehow? (I obviously don't know what the rare situations are!)
I can't see a way of disabling sysex either from the LP transmitting or the Nerdseq receiving, but it seems like that would be an easy solution to fix this (assuming the Nerdseq doesn't rely on sysex messages being received of course!)
Hope this helps
Thanks again.
I found out some more info that might be useful...
When switching modes on the LP Pro (LIVE, NOTES, PGM) some system exclusive messages are transmitted:
00 20 29 02 10 2D 01
00 20 29 02 10 2F 00
00 20 29 02 10 2F 03
Looking at the LP sysex documentation these seem to be Mode selection and Standalone Layout Select which makes sense to me
Presumably this data is being interpreted by the Nerdseq somehow and causing a "last note trigger" or something similar?
I didn't think the Nerdseq could respond to sysex? Or maybe the issue is caused by something else?
The only other reference to something like this I found is from the firmware v1.21A release. In the comments I see this:
- fixed midi issue which could create a hanging note on local CV-Gate tracks in very rare situations
Is it possible this bug got reintroduced in firmware v1.22 somehow? (I obviously don't know what the rare situations are!)
I can't see a way of disabling sysex either from the LP transmitting or the Nerdseq receiving, but it seems like that would be an easy solution to fix this (assuming the Nerdseq doesn't rely on sysex messages being received of course!)
Hope this helps
Thanks again.