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

MIDI click to bind detection algorithm bug? #205

Open
freecodecampster opened this issue Dec 29, 2020 · 2 comments
Open

MIDI click to bind detection algorithm bug? #205

freecodecampster opened this issue Dec 29, 2020 · 2 comments

Comments

@freecodecampster
Copy link

Hi, I’m playing around with midi input using an Arturia MiniLab mkII and Behringer X-TOUCH MINI into UCR v0.9.0. I think I’ve found a bug with the “click to bind” function. It only works when midi notes or midi cc messages send more than two values - so rotary encoders or the midi keyboard/pads work if you keep rotating or pressing with a variety of values/velocities. Buttons which send only two values typically 0 and 127 are never recognised no matter how many times you spam the button. I verified this by setting velocity sensitive pads to output only 0 and 127. Before they would be picked up if I varied the velocity, now they will never be recognised no matter how many times I tap them. I can however manually assign the midi note/CC through the hamburger menu.

@life-on-mars
Copy link

I tried it with my Samson Graphite and it doesn't matter if the buttons send Notes or CCs, they get never recognised by the bind function. Also notes don't work at all, neither as simple on/off nor with polypressure. I can assign them using the burger menu but that doesn't have any effect. Assigning CCs works, however.

@Nicklefront
Copy link

So, how did you get it to work exactly?

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

3 participants