GNOME Bugzilla – Bug 609409
jackaudio sink cannot create ports
Last modified: 2010-09-02 13:29:46 UTC
This works: jez@X31:~$ gst-launch audiotestsrc ! jackaudiosink Setting pipeline to PAUSED ... Pipeline is PREROLLING ... Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstAudioSinkClock ^CCaught interrupt -- handling interrupt. Interrupt: Stopping pipeline ... Execution ended after 1470244240 ns. Setting pipeline to PAUSED ... Setting pipeline to READY ... Setting pipeline to NULL ... Freeing pipeline ... jez@X31:~$ But this does not: jez@X31:~$ gst-launch audiotestsrc ! jackaudiosink audiotestsrc ! jackaudiosink Setting pipeline to PAUSED ... Pipeline is PREROLLING ... ERROR: from element /GstPipeline:pipeline0/GstJackAudioSink:jackaudiosink0: Could not get/set settings from/on resource. Additional debug info: gstjackaudiosink.c(524): gst_jack_ring_buffer_acquire (): /GstPipeline:pipeline0/GstJackAudioSink:jackaudiosink0: Cannot allocate more Jack ports ERROR: pipeline doesn't want to preroll. Setting pipeline to NULL ... Freeing pipeline ... jez@X31:~/code/birdsong$ I'm using the latest git version of jackaudiosink. The problem occurs with older versions, too. I'm not sure what other information to post, but please ask and I'll endeavour to provide what I can ...
Not sure what to do with this. I think you are saying that all instances of jackaudiosink in the same process should share the same jack ports and all pull in the same jack callback.
simply that the second command: gst-launch audiotestsrc freq=200 ! jackaudiosink audiotestsrc freq=400 ! jackaudiosink should WORK, instead of throwing an error. with jack 1.9.5 and latest git version of gst-plugins-bad, it does not work - as shown above.
This works fine for me on gst-plugins-bad from git head and jackd version 0.116.2 (that is ~ 1.9.3). Jeremiah, can you get a debug log from gstreamer and attach here? GST_DEBUG="*:2,*jack*:4" GST_DEBUG_NO_COLOR=1 gst-launch-0.10 2>debug.log audiotestsrc ...
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!