-
Notifications
You must be signed in to change notification settings - Fork 172
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
Jack Transport not active when "auto" engine is used (even if it selects JACK) #392
Comments
the audio driver in the preferences dialog. Use the class name of the audio driver to detect if jack driver is active.
Should be fixed now.. |
Fresh rebuild from today's GIT (2e23685) and I can confirmed that the buttons are now shown whether I select manually the audio-engine to be JACK, or if the "auto" mode is choosing JACK as the audio engine. Then, a second related bug is appearing: when "auto" is used (and choosing JACK by its own), if I click on one of those 2 buttons ("J.TRANS" or "J.MASTER", I've got a pop up window telling me that: " Hope that helps. |
Sorry, i forgot to modify the checks for the transport/master buttons. Please check again 😄 |
Fresh rebuild from today's GIT (cd9b7e1) and I can confirmed that the pop-up window is not poping anymore. I've checked with a 0.9.6.1 version (debian jessie repo) and this (unexpected/incorrect) behavior was already there, so I did put a line here https://github.com/hydrogen-music/hydrogen/wiki/New-features-in-Hydrogen-0.9.7#bugfixes I'm closing this issue and removing the screencast then. |
I was just reading at this discussion: #379 and playing around with Hydrogen when I suddenly faced up a strange behavior:
Screencast: http://download.tuxfamily.org/librazik/volatile/hydrogen-issue392.mp4
Comments about the screencast:
What would I be expecting ?
As a user, I'd expect Hydrogen to show my the JACK transport controls whether I select manually the audio-engine to be JACK, or if the "auto" mode is choosing JACK as the audio engine.
Hope that helps.
The text was updated successfully, but these errors were encountered: