Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drumlogue doesn’t correctly respond to program change messages #124

Open
HLammers opened this issue Oct 9, 2024 · 0 comments
Open

Drumlogue doesn’t correctly respond to program change messages #124

HLammers opened this issue Oct 9, 2024 · 0 comments

Comments

@HLammers
Copy link

HLammers commented Oct 9, 2024

I don’t know if this is the right place to report a bug in the Drumlogue, but I couldn’t find a direct way to report to Korg (I’ve also send an email to the local Korg distributor.

I found a bug in the Drumlogue’s response to program change messages. The ones sent out by the Drumlogue (firmware 1.2.0) start from 1 (on a 0-127 scale) for A1, 2 for A2, ... 15 for A15 and 0 for A16. The same strange logic for the next 16 programs: 17 for B1, 18 for B2, ... 31 for B15 and 16 for B16, etc.
Programs A16 (16 or 0), B16 (32 or 16) , C16 (48 or 32), D16 (64 or 48) etc. send out a little awkward numbers, but the even bigger problem is that the Drumlogue doesn’t respond to program change values 0, 16, 32, 48, 64, etc. which means that programs A16, B16, C16, D16, etc. cannot be selected from an external device.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant