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

Workaround raspi selecting jack server instead of ALSA. #604

adamcik opened this Issue Dec 6, 2013 · 3 comments


3 participants

adamcik commented Dec 6, 2013

Adding the following code somewhere should prevent the auto-selection of jack.

registry = gst.registry_get_default()
jacksink = registry.find_feature('jackaudiosink', gst.TYPE_ELEMENT_FACTORY)
if jacksink:

@jodal jodal added this to the v0.20 - Audio and mixer cleanup milestone Jun 22, 2014

@jodal jodal added the Easy pickings label Jul 24, 2014


This comment has been minimized.


adamcik commented Jul 27, 2014

Essentially this code just needs to be run at startup, easiest way to achieve this is probably just to add it at the module level in


This comment has been minimized.


arjunrn commented Jul 27, 2014

I could reproduce the bug when I used a fresh vagrant ubuntu-precise box. This is the error message produced

Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
ERROR    GStreamer error: state change failed and some element failed to post a proper error message with the reason for the failure. Debug message: gstplaysink.c(1899): gen_audio_chain (): /GstPlayBin2:playbin20/GstPlaySink:playsink0

@jodal jodal modified the milestones: v0.20 - Audio cleanup, v0.19.3 Jul 29, 2014


This comment has been minimized.


jodal commented Jul 29, 2014

Fixed by #801.

@jodal jodal closed this Jul 29, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment