-
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
midi feedback on update is not always sent properly #35
Comments
Can you make a new PR for this issue ? So I can merge this fix in master easily. |
sure, i'll be back home next week and cant start working on that before
|
Did you notice xruns when you have feedback issue ? Can you retry with gui window reduced (not visible on screen) ? |
@sonejostudios tells me apparently there are xruns on song-load sometimes. Do you think this can be responsible for midi messages in the out_queue not being sent? (that sounds not safe to me) |
I think QT part sometimes slow down python interpreter, if you increase refresh rate of progress bar (main gui), you will have many xruns. Gui should not slow down jack callback because callbacks are called from another thread. Xruns is a big issue in superboucle |
I assume, superboucle would not be the only pyqt based program having trouble with xruns then? |
When a song is loaded, midi feedback for all clips states is sent, so on the device (i.e. the launchpad) the lights will be displayed according to the song's clip setup.
Mostly this works fine, but sometimes (in an unpredictable fashion) it does not: it just doesn't send anything or only a part of the expected midi signals (noticed with launchpad and double-checked with qmidiroute)
I plan to fix this in sonejostudios:Device_Rewrite but still creating this issue for reference
My guess is, the reason has something to do with concurrency/blocking of the queue, but i have yet to further investigate it.
The text was updated successfully, but these errors were encountered: