-
Notifications
You must be signed in to change notification settings - Fork 10
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
Losing midi controls, except from clips start/stop #78
Comments
@manucontrovento Did you try to turn off and on your midi controller ? I will check the learning code to see if there is some reset message sent. |
@Vampouille I tried, but nothing changes |
Hello, yesterday I noticed a similar kind of issue, but at reverse: only clips buttons were detected and working, while transport buttons were not working anymore |
@manucontrovento I think I found a bug is the process that map midi event to action. I will try to push the fix as soon as possible. |
@manucontrovento I push a new commit in the Can you re-test device mapping with this commit it should fix most of the bug in device mapping ? |
@Vampouille Sure! I think I'll test it tonight. |
@Vampouille yeah man! using debug version, seems to be working! |
I did some tests, imho you could load this fix in master branch. Or maybe you prefer to wait and update master branch when you'll have a bunch of some other fixes/features ? |
yes |
Hi @manucontrovento ! Should I close the issue? Or should I wait the fix in master branch? |
needs #83 |
HI everyone, in latest days testing several sessions, I found this further problem: midi controller is fully working, then something happens and the only buttons working in midi controller are the clips start/stop buttons. Transport buttons, line buttons etc. don't work no more, while from the transport buttons on screen all is working.
The only way to get the buttons working again is to re-do the midi learning, creating a new controller. Also loading a saved controller doesn't work, nor setting None controller and selecting it back again.
This time Jack latency is ok, 1024 or 2048 and period = 2
So I reloaded the session, using the debug SB version, and I found that there's an error, but I don't know if it could be related:
is it enough to understand something about the problem?
have a nice day
manu
The text was updated successfully, but these errors were encountered: