-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
VST stupid hack to make Bitwig Linux work #109
Conversation
Not really, there is still a case of failure if you
Gdb stack of attached debugger to the plugin bridge process
|
Would this be related to the use of zenity for this dialog box? |
I sincerely don't know at this point. From what I can at least tell, Bitwig host is buggy in that it never notifies the plugin of X11 events. |
Heh... Well, do they care enough to try and fix this? |
For reference, it's this inelegantly written bug report, the probable reason why fd select fails on Linux hosts. |
This makes Bitwig work and fixes all problems. Note: to debug Bitwig, the way to do is substitute |
Other than the small |
The host-side X11 event loop is broken, it never notifies events.
Thankfully, we have a way of fixing Bitwig in the plugin. 🤡
Bitwig provides a working timer notification. This timer notification is a place where we are able to process X11 events.
Solution: create a periodic timer; as long as no events arrive in the X11 socket notifier, keep processing events in the callback of our timer.
@tank-trax