Here's the full log of the failure when dbus-launch isn't available,
which also finishes with a segmentation fault.
mpd@gardner:/root$ rygel
Rygel-Message: New plugin 'GstLaunch' available
(rygel:2187): MediaExport-WARNING **: Failed to attach to D-Bus
session bus: Command line `dbus-launch
--autolaunch=3bc3212927ef79ca1c9e685300000b5d --binary-syntax
--close-stderr' exited with non-zero exit status 1: Autolaunch error:
X11 initialization failed.\n
(rygel:2187): GStreamer-CRITICAL **: gst_bus_create_watch: assertion
`GST_IS_BUS (bus)' failed
(rygel:2187): GLib-CRITICAL **: g_source_set_callback: assertion
`source != NULL' failed
Segmentation fault
On 27 May 2012 11:21, Cefn Hoile <> wrote:
> Hi all,
>
> I'm trying to launch Rygel to serve my MPD pulseaudio stream from a
> Pogoplug to the rest of my home network, running Debian Wheezy.
>
> Rygel versioning reports...
> Rygel 0.14.1
>
> This is a machine without XWindows. I was therefore disappointed to
> find that Rygel was throwing errors trying to invoke dbus-launch,
> which is now in the dbus-x11 package, and once it is installed as
> expected I get a nasty error about X11 initialisation, whether running
> as mpd or root (shown below). Without installing dbus-x11 rygel
> notifies a critical error : Failed to execute child process
> "dbus-launch" and shuts down.
>
> My current rygel.conf file is attached in case that is in any way
> relevant. You can see the pulseaudio configuration I'm attempting in
> there.
>
> How do I launch Rygel to relay Pulseaudio on a headless server without
> these Critical errors causing it to fail.
>
>>>>>>>>>>>
>
> mpd@gardner:/root$ rygel
> Rygel-Message: New plugin 'GstLaunch' available
>
> (rygel:2187): MediaExport-WARNING **: Failed to attach to D-Bus
> session bus: Command line `dbus-launch
> --autolaunch=3bc3212927ef79ca1c9e685300000b5d --binary-syntax
> --close-stderr' exited with non-zero exit status 1: Autolaunch error:
> X11 initialization failed.\n
>
> (rygel:2187): GStreamer-CRITICAL **: gst_bus_create_watch: assertion
> `GST_IS_BUS (bus)' failed
>
> (rygel:2187): GLib-CRITICAL **: g_source_set_callback: assertion
> `source != NULL' failed
> Segmentation fault
>
>
>
> Cefn
> http://cefn.com
_______________________________________________
rygel-list mailing list
rygel-
https://mail.gnome.org/mailman/listinfo/rygel-list
)
On Sun, May 27, 2012 at 2:04 PM, Cefn Hoile <> wrote:
> Here's the full log of the failure when dbus-launch isn't available,
> which also finishes with a segmentation fault.
>
> mpd@gardner:/root$ rygel
> Rygel-Message: New plugin 'GstLaunch' available
>
> (rygel:2187): MediaExport-WARNING **: Failed to attach to D-Bus
> session bus: Command line `dbus-launch
> --autolaunch=3bc3212927ef79ca1c9e685300000b5d --binary-syntax
> --close-stderr' exited with non-zero exit status 1: Autolaunch error:
> X11 initialization failed.\n
>
> (rygel:2187): GStreamer-CRITICAL **: gst_bus_create_watch: assertion
> `GST_IS_BUS (bus)' failed
>
> (rygel:2187): GLib-CRITICAL **: g_source_set_callback: assertion
> `source != NULL' failed
> Segmentation fault
>
> On 27 May 2012 11:21, Cefn Hoile <> wrote:
>> Hi all,
>>
>> I'm trying to launch Rygel to serve my MPD pulseaudio stream from a
>> Pogoplug to the rest of my home network, running Debian Wheezy.
>>
>> Rygel versioning reports...
>> Rygel 0.14.1
>>
>> This is a machine without XWindows. I was therefore disappointed to
>> find that Rygel was throwing errors trying to invoke dbus-launch,
>> which is now in the dbus-x11 package,
That would be a packaging/distribution problem I believe since rygel
and pulseaudio only need dbus to talk to each other and neither rygel,
pulseaudio nor dbus really require X.
--
Regards,
Zeeshan Ali (Khattak)
FSF member#5124
_______________________________________________
rygel-list mailing list
rygel-
https://mail.gnome.org/mailman/listinfo/rygel-list
)
I don't know if it can be strictly 'packaging' since an invocation of
dbus-launch somehow attempts to initiate X11 and fails. This is
consistent with its packaging, but not determined by it. The actual
logic of dbus-launch (direct from the debian wheezy armel repo) must
be somehow dependent on X as well.
Neither explains the segmentation fault reported some time after
dbus-launch fails.
I saw in another thread that these DBus warnings might be able to be
ignored, but it seems like the Segfault is what finally kills Rygel in
both cases, with or without dbus-launch.
I guess you are saying I'll need dbus-launch in order to successfully
serve wav data from pulseaudio via Rygel. However, I suspect the
segfault is worth figuring out anyway for the stability of the package
in general. Is there ARM support?
I'll see if I can find dbus-launch via some other route to satisfy
Rygel and workaround the segfault. Does that make sense?
Cefn
http://cefn.com
On 27 May 2012 15:28, Zeeshan Ali (Khattak) <> wrote:
> On Sun, May 27, 2012 at 2:04 PM, Cefn Hoile <> wrote:
>> Here's the full log of the failure when dbus-launch isn't available,
>> which also finishes with a segmentation fault.
>>
>> mpd@gardner:/root$ rygel
>> Rygel-Message: New plugin 'GstLaunch' available
>>
>> (rygel:2187): MediaExport-WARNING **: Failed to attach to D-Bus
>> session bus: Command line `dbus-launch
>> --autolaunch=3bc3212927ef79ca1c9e685300000b5d --binary-syntax
>> --close-stderr' exited with non-zero exit status 1: Autolaunch error:
>> X11 initialization failed.\n
>>
>> (rygel:2187): GStreamer-CRITICAL **: gst_bus_create_watch: assertion
>> `GST_IS_BUS (bus)' failed
>>
>> (rygel:2187): GLib-CRITICAL **: g_source_set_callback: assertion
>> `source != NULL' failed
>> Segmentation fault
>>
>> On 27 May 2012 11:21, Cefn Hoile <> wrote:
>>> Hi all,
>>>
>>> I'm trying to launch Rygel to serve my MPD pulseaudio stream from a
>>> Pogoplug to the rest of my home network, running Debian Wheezy.
>>>
>>> Rygel versioning reports...
>>> Rygel 0.14.1
>>>
>>> This is a machine without XWindows. I was therefore disappointed to
>>> find that Rygel was throwing errors trying to invoke dbus-launch,
>>> which is now in the dbus-x11 package,
>
> That would be a packaging/distribution problem I believe since rygel
> and pulseaudio only need dbus to talk to each other and neither rygel,
> pulseaudio nor dbus really require X.
>
> --
> Regards,
>
> Zeeshan Ali (Khattak)
> FSF member#5124
_______________________________________________
rygel-list mailing list
rygel-
https://mail.gnome.org/mailman/listinfo/rygel-list
)
On Mo, 2012-05-28 at 01:38 +0100, Cefn Hoile wrote:
Yes, these D-Bus criticals are not really criticals, they will be made
less violent in the next release.
You only need D-Bus for Pulseaudio's "native" integration, if you use
GstLauch like in your config then there's no need for D-Bus.
I don't think the segfault is related to D-Bus; I suspect it originates
from either the Playbin or the MediaExport plugin. Can you try to get a
backtrace for it?
Rygel works fine on ARM.
> I don't know if it can be strictly 'packaging' since an invocation of
> dbus-launch somehow attempts to initiate X11 and fails. This is
> consistent with its packaging, but not determined by it. The actual
> logic of dbus-launch (direct from the debian wheezy armel repo) must
> be somehow dependent on X as well.
>
> Neither explains the segmentation fault reported some time after
> dbus-launch fails.
>
> I saw in another thread that these DBus warnings might be able to be
> ignored, but it seems like the Segfault is what finally kills Rygel in
> both cases, with or without dbus-launch.
>
> I guess you are saying I'll need dbus-launch in order to successfully
> serve wav data from pulseaudio via Rygel. However, I suspect the
> segfault is worth figuring out anyway for the stability of the package
> in general. Is there ARM support?
>
> I'll see if I can find dbus-launch via some other route to satisfy
> Rygel and workaround the segfault. Does that make sense?
>
> Cefn
> http://cefn.com
>
> On 27 May 2012 15:28, Zeeshan Ali (Khattak) <> wrote:
> > On Sun, May 27, 2012 at 2:04 PM, Cefn Hoile <> wrote:
> >> Here's the full log of the failure when dbus-launch isn't available,
> >> which also finishes with a segmentation fault.
> >>
> >> mpd@gardner:/root$ rygel
> >> Rygel-Message: New plugin 'GstLaunch' available
> >>
> >> (rygel:2187): MediaExport-WARNING **: Failed to attach to D-Bus
> >> session bus: Command line `dbus-launch
> >> --autolaunch=3bc3212927ef79ca1c9e685300000b5d --binary-syntax
> >> --close-stderr' exited with non-zero exit status 1: Autolaunch error:
> >> X11 initialization failed.\n
> >>
> >> (rygel:2187): GStreamer-CRITICAL **: gst_bus_create_watch: assertion
> >> `GST_IS_BUS (bus)' failed
> >>
> >> (rygel:2187): GLib-CRITICAL **: g_source_set_callback: assertion
> >> `source != NULL' failed
> >> Segmentation fault
> >>
> >> On 27 May 2012 11:21, Cefn Hoile <> wrote:
> >>> Hi all,
> >>>
> >>> I'm trying to launch Rygel to serve my MPD pulseaudio stream from a
> >>> Pogoplug to the rest of my home network, running Debian Wheezy.
> >>>
> >>> Rygel versioning reports...
> >>> Rygel 0.14.1
> >>>
> >>> This is a machine without XWindows. I was therefore disappointed to
> >>> find that Rygel was throwing errors trying to invoke dbus-launch,
> >>> which is now in the dbus-x11 package,
> >
> > That would be a packaging/distribution problem I believe since rygel
> > and pulseaudio only need dbus to talk to each other and neither rygel,
> > pulseaudio nor dbus really require X.
> >
> > --
> > Regards,
> >
> > Zeeshan Ali (Khattak)
> > FSF member#5124
> _______________________________________________
> rygel-list mailing list
> rygel-
> https://mail.gnome.org/mailman/listinfo/rygel-list
>
_______________________________________________
rygel-list mailing list
rygel-
https://mail.gnome.org/mailman/listinfo/rygel-list
)
On Mo, 2012-05-28 at 10:20 +0100, Cefn Hoile wrote:
>
> I installed rygel-dbg and then followed the instructions at
> https://wiki.ubuntu.com/Backtrace to create the attached file
> (hopefully) detailing the crash.
Yes, that's in MediaExport or rather in GstDiscoverer. Can you install
libgstreamer0.10-0-dbg and gstreamer0.10-plugins-base-dbg and get
another backtrace?
And after that,
break g_logv
cond 1 log_level == G_LOG_LEVEL_CRITICAL
restart the process ("run") and get a backtrace when the condition
triggers with the format argument being "gst_bus_create_watch: assertion
`GST_IS_BUS (bus)' failed, otherwise using "cont" to continue execution?
thanks.
_______________________________________________
rygel-list mailing list
rygel-
https://mail.gnome.org/mailman/listinfo/rygel-list
)
Once I've installed all the debugging packages you mentioned, the
Segfault stops arising.
I was now able to see more meaningful errors when trying to attach to
the wav stream, which were associated with missing packages - needed
gstreamer0.10-pulseaudio to give me pulsesrc and
gstreamer0.10-plugins-good to give me wavpackenc
I've arrived at this error which I don't know how to handle when
attaching to the Gstreamer Wave stream using VLC's UPNP browser (which
detects a stream from Rygel at my local
http://192.168.1.128:57845/GstLaunch/i/bXlwdWxzZWF1ZGlvc2luaw%3D%3D.wav
)
(rygel:3140): Rygel-WARNING **: rygel-http-request.vala:97: Invalid seek request
(rygel:3140): Rygel-CRITICAL **: Error from pipeline
RygelHTTPGstResponse: pulsesrc.c(1480): gst_pulsesrc_prepare ():
/GstPipeline:RygelHTTPGstResponse/GstBin:bin0/GstPulseSrc:pulsesrc0
It does this whether I run Rygel as root or as mpd. I think according
to the configuration it ought to be sending over the wav samples,
without re-encoding them, but perhaps someone more specialist has an
idea if I've actually configured it correctly from the original conf
file I attached.
Cefn
http://cefn.com
On 28 May 2012 11:09, Jens Georg <> wrote:
> On Mo, 2012-05-28 at 10:20 +0100, Cefn Hoile wrote:
>
>>
>> I installed rygel-dbg and then followed the instructions at
>> https://wiki.ubuntu.com/Backtrace to create the attached file
>> (hopefully) detailing the crash.
>
> Yes, that's in MediaExport or rather in GstDiscoverer. Can you install
> libgstreamer0.10-0-dbg and gstreamer0.10-plugins-base-dbg and get
> another backtrace?
>
> And after that,
>
> break g_logv
> cond 1 log_level == G_LOG_LEVEL_CRITICAL
>
> restart the process ("run") and get a backtrace when the condition
> triggers with the format argument being "gst_bus_create_watch: assertion
> `GST_IS_BUS (bus)' failed, otherwise using "cont" to continue execution?
>
> thanks.
>
_______________________________________________
rygel-list mailing list
rygel-
https://mail.gnome.org/mailman/listinfo/rygel-list
)
On Mo, 2012-05-28 at 22:56 +0100, Cefn Hoile wrote:
> Once I've installed all the debugging packages you mentioned, the
> Segfault stops arising.
That means you managed to install the gst-plugins-base libraries without
installing the base plugins. Looks like some packaging dependendy
problems.
>
> I was now able to see more meaningful errors when trying to attach to
> the wav stream, which were associated with missing packages - needed
> gstreamer0.10-pulseaudio to give me pulsesrc and
> gstreamer0.10-plugins-good to give me wavpackenc
Btw. wavpack is not WAV. wavpack is a lossless but compressing audio
codec, similar to FLAC. WAV "encoding" is done by wavenc.
>
> I've arrived at this error which I don't know how to handle when
> attaching to the Gstreamer Wave stream using VLC's UPNP browser (which
> detects a stream from Rygel at my local
> http://192.168.1.128:57845/GstLaunch/i/bXlwdWxzZWF1ZGlvc2luaw%3D%3D.wav
> )
>
> (rygel:3140): Rygel-WARNING **: rygel-http-request.vala:97: Invalid seek request
This is a known bug we need to address at some point; unfortunately this
is a bit tricky (https://bugzilla.gnome.org/show_bug.cgi?id=659432 or
https://bugzilla.gnome.org/show_bug.cgi?id=674736) It's ok with VLC as
it does the right thing (retry without seeking).
> (rygel:3140): Rygel-CRITICAL **: Error from pipeline
> RygelHTTPGstResponse: pulsesrc.c(1480): gst_pulsesrc_prepare ():
> /GstPipeline:RygelHTTPGstResponse/GstBin:bin0/GstPulseSrc:pulsesrc0
Are you sure that the headphone thing is the correct pulse source?
I've got something like
mypulseaudiosink-title=Audio on @HOSTNAME@
mypulseaudiosink-mime=audio/L16;rate=44100;channels=2
mypulseaudiosink-launch=pulsesrc device=alsa_output.pci-0000_00_1b.0.analog-stereo.monitor
in my rygel.conf
_______________________________________________
rygel-list mailing list
rygel-
https://mail.gnome.org/mailman/listinfo/rygel-list
)
On 29 May 2012 12:48, Cefn Hoile <> wrote:
> On 29 May 2012 10:44, Jens Georg <> wrote:
>> On Mo, 2012-05-28 at 22:56 +0100, Cefn Hoile wrote:
>>> Once I've installed all the debugging packages you mentioned, the
>>> Segfault stops arising.
>>
>> That means you managed to install the gst-plugins-base libraries without
>> installing the base plugins. Looks like some packaging dependendy
>> problems.
>>
>>>
>>> I was now able to see more meaningful errors when trying to attach to
>>> the wav stream, which were associated with missing packages - needed
>>> gstreamer0.10-pulseaudio to give me pulsesrc and
>>> gstreamer0.10-plugins-good to give me wavpackenc
>>
>> Btw. wavpack is not WAV. wavpack is a lossless but compressing audio
>> codec, similar to FLAC. WAV "encoding" is done by wavenc.
>>
>>>
>>> I've arrived at this error which I don't know how to handle when
>>> attaching to the Gstreamer Wave stream using VLC's UPNP browser (which
>>> detects a stream from Rygel at my local
>>> http://192.168.1.128:57845/GstLaunch/i/bXlwdWxzZWF1ZGlvc2luaw%3D%3D.wav
>>> )
>>>
>>> (rygel:3140): Rygel-WARNING **: rygel-http-request.vala:97: Invalid seek request
>>
>> This is a known bug we need to address at some point; unfortunately this
>> is a bit tricky (https://bugzilla.gnome.org/show_bug.cgi?id=659432 or
>> https://bugzilla.gnome.org/show_bug.cgi?id=674736) It's ok with VLC as
>> it does the right thing (retry without seeking).
>>
>>> (rygel:3140): Rygel-CRITICAL **: Error from pipeline
>>> RygelHTTPGstResponse: pulsesrc.c(1480): gst_pulsesrc_prepare ():
>>> /GstPipeline:RygelHTTPGstResponse/GstBin:bin0/GstPulseSrc:pulsesrc0
>>
>> Are you sure that the headphone thing is the correct pulse source?
>>
>> I've got something like
>>
>> mypulseaudiosink-title=Audio on @HOSTNAME@
>> mypulseaudiosink-mime=audio/L16;rate=44100;channels=2
>> mypulseaudiosink-launch=pulsesrc device=alsa_output.pci-0000_00_1b.0.analog-stereo.monitor
>>
>> in my rygel.conf
>>
>>
>
> I'm still surprised it's a segfault, rather than a more elegantly
> handled error, but glad I'm not experiencing it anymore.
>
> I've duplicated your suggested lines, in the hope that this would
> relay the wave data from the soundcard without reencoding. I replaced
> the alsa device name with the first device name which shows up when I
> run
>
> pacmd list-sources
>
> ...as the mpd user, the name of this device being...
>
> alsa_output.usb-0d8c_C-Media_USB_Headphone_Set-00-Set.analog-stereo.monitor
>
> Inspecting the soundcard through Alsa tools suggests that the hardware
> shows up as...
> mpd@gardner:/root$ cat /proc/asound/card0/pcm0p/sub0/hw_params
> access: MMAP_INTERLEAVED
> format: S16_LE
> subformat: STD
> channels: 2
> rate: 44100 (44100/1)
> period_size: 44100
> buffer_size: 88200
> ...so I'm guessing the mime type information matches with the
> declaration you provided too.
>
> Having launched rygel (logged in as the mpd user) and when trying to
> stream using VLC on my desktop from the detected endpoint (which
> appears correctly), rygel reports the sync error as normal when the
> stream starts but doesn't report a critical Gstreamer error, so I
> guess it's doing something. In all the incorrect configurations so
> far, the stream died immediately, so this is something like progress.
>
> However, I get VLC reporting 00:00 seconds in the stream and no sound
> audible. Are you able to stream audible sound to VLC using the
> configuration you shared with me?
>
> Thanks for all your help. I would have given up long ago without
> confident guidance on this. I've attached my current rygel
> configuration and the pacmd report on my devices in case anything
> leaps out which needs to be differently configured.
>
> Cefn
> http://cefn.com
On further investigation I had some concerns that pulseaudio might not
be in use by MPD, (and I'm still not sure it is) but running...
cat /dev/urandom | pacat -d
"alsa_output.usb-0d8c_C-Media_USB_Headphone_Set-00-Set.analog-stereo"
...generates noise from the speakers, without any noise appearing via
the rygel-served stream, which remains at 00:00.
I think this proves that Pulseaudio is indeed in use, and I'd expect
noise via rygel in VLC, but instead it's silent. Hopefully this is a
better test case to pursue.
Cefn
http://cefn.com
_______________________________________________
rygel-list mailing list
rygel-
https://mail.gnome.org/mailman/listinfo/rygel-list
)
On 29 May 2012 16:24, Cefn Hoile <> wrote:
> On 29 May 2012 12:48, Cefn Hoile <> wrote:
>> On 29 May 2012 10:44, Jens Georg <> wrote:
>>> On Mo, 2012-05-28 at 22:56 +0100, Cefn Hoile wrote:
>>>> Once I've installed all the debugging packages you mentioned, the
>>>> Segfault stops arising.
>>>
>>> That means you managed to install the gst-plugins-base libraries without
>>> installing the base plugins. Looks like some packaging dependendy
>>> problems.
>>>
>>>>
>>>> I was now able to see more meaningful errors when trying to attach to
>>>> the wav stream, which were associated with missing packages - needed
>>>> gstreamer0.10-pulseaudio to give me pulsesrc and
>>>> gstreamer0.10-plugins-good to give me wavpackenc
>>>
>>> Btw. wavpack is not WAV. wavpack is a lossless but compressing audio
>>> codec, similar to FLAC. WAV "encoding" is done by wavenc.
>>>
>>>>
>>>> I've arrived at this error which I don't know how to handle when
>>>> attaching to the Gstreamer Wave stream using VLC's UPNP browser (which
>>>> detects a stream from Rygel at my local
>>>> http://192.168.1.128:57845/GstLaunch/i/bXlwdWxzZWF1ZGlvc2luaw%3D%3D.wav
>>>> )
>>>>
>>>> (rygel:3140): Rygel-WARNING **: rygel-http-request.vala:97: Invalid seek request
>>>
>>> This is a known bug we need to address at some point; unfortunately this
>>> is a bit tricky (https://bugzilla.gnome.org/show_bug.cgi?id=659432 or
>>> https://bugzilla.gnome.org/show_bug.cgi?id=674736) It's ok with VLC as
>>> it does the right thing (retry without seeking).
>>>
>>>> (rygel:3140): Rygel-CRITICAL **: Error from pipeline
>>>> RygelHTTPGstResponse: pulsesrc.c(1480): gst_pulsesrc_prepare ():
>>>> /GstPipeline:RygelHTTPGstResponse/GstBin:bin0/GstPulseSrc:pulsesrc0
>>>
>>> Are you sure that the headphone thing is the correct pulse source?
>>>
>>> I've got something like
>>>
>>> mypulseaudiosink-title=Audio on @HOSTNAME@
>>> mypulseaudiosink-mime=audio/L16;rate=44100;channels=2
>>> mypulseaudiosink-launch=pulsesrc device=alsa_output.pci-0000_00_1b.0.analog-stereo.monitor
>>>
>>> in my rygel.conf
>>>
>>>
>>
>> I'm still surprised it's a segfault, rather than a more elegantly
>> handled error, but glad I'm not experiencing it anymore.
>>
>> I've duplicated your suggested lines, in the hope that this would
>> relay the wave data from the soundcard without reencoding. I replaced
>> the alsa device name with the first device name which shows up when I
>> run
>>
>> pacmd list-sources
>>
>> ...as the mpd user, the name of this device being...
>>
>> alsa_output.usb-0d8c_C-Media_USB_Headphone_Set-00-Set.analog-stereo.monitor
>>
>> Inspecting the soundcard through Alsa tools suggests that the hardware
>> shows up as...
>> mpd@gardner:/root$ cat /proc/asound/card0/pcm0p/sub0/hw_params
>> access: MMAP_INTERLEAVED
>> format: S16_LE
>> subformat: STD
>> channels: 2
>> rate: 44100 (44100/1)
>> period_size: 44100
>> buffer_size: 88200
>> ...so I'm guessing the mime type information matches with the
>> declaration you provided too.
>>
>> Having launched rygel (logged in as the mpd user) and when trying to
>> stream using VLC on my desktop from the detected endpoint (which
>> appears correctly), rygel reports the sync error as normal when the
>> stream starts but doesn't report a critical Gstreamer error, so I
>> guess it's doing something. In all the incorrect configurations so
>> far, the stream died immediately, so this is something like progress.
>>
>> However, I get VLC reporting 00:00 seconds in the stream and no sound
>> audible. Are you able to stream audible sound to VLC using the
>> configuration you shared with me?
>>
>> Thanks for all your help. I would have given up long ago without
>> confident guidance on this. I've attached my current rygel
>> configuration and the pacmd report on my devices in case anything
>> leaps out which needs to be differently configured.
>>
>> Cefn
>> http://cefn.com
>
> On further investigation I had some concerns that pulseaudio might not
> be in use by MPD, (and I'm still not sure it is) but running...
> cat /dev/urandom | pacat -d
> "alsa_output.usb-0d8c_C-Media_USB_Headphone_Set-00-Set.analog-stereo"
> ...generates noise from the speakers, without any noise appearing via
> the rygel-served stream, which remains at 00:00.
>
> I think this proves that Pulseaudio is indeed in use, and I'd expect
> noise via rygel in VLC, but instead it's silent. Hopefully this is a
> better test case to pursue.
>
> Cefn
> http://cefn.com
Finally I have success. The following command line proves that there's
an issue with VLC, since the following direct request to the
introspected UPnP-published stream...
curl http://192.168.1.128:36483/GstLaunch/i/bXlwdWxzZWF1ZGlvc2luaw%3D%3D
| pacat -p
...plays audio fine with no breaks, though a big delay. In VLC the
same stream apparently plays, but stalls at 00:00 and no audio comes
out.
I'll investigate other UPnP client options, or figure out a mime type
configuration which media clients will accept in order to decode this
format. This direct call to Pulseaudio is not a bad way to use Rygel
actually, although I was hoping for family and other home network
users to be able to do UPnP browsing through some kind of nice
interface, like VLC or Rhythmbox, perhaps I can just write a simple
GUI to connect desktops/etc to various systems around the house using
curl and pacat, assuming I can figure out how to get the corresponding
HTTP URLs for each source via some kind of UPnP library. Suggestions
for a simple (console?) tool to query available UPnP trees to find the
"Gst Launch" node?
I might be able to use this for audio connectivity from microphones
too, now I've figured it out, save buying a new baby alarm! Can I get
any control through Rygel to minimise buffering and hence reduce audio
delay?
Congratulations on the release!
_______________________________________________
rygel-list mailing list
rygel-
https://mail.gnome.org/mailman/listinfo/rygel-list
)
> Finally I have success. The following command line proves that there's
> an issue with VLC, since the following direct request to the
> introspected UPnP-published stream...
>
> curl http://192.168.1.128:36483/GstLaunch/i/bXlwdWxzZWF1ZGlvc2luaw%3D%3D
> | pacat -p
>
> ...plays audio fine with no breaks, though a big delay. In VLC the
> same stream apparently plays, but stalls at 00:00 and no audio comes
> out.
If you don't define an encoder and use raw PCM data, you have to code the
parameters of the stream in the mime type. For a "normal" PC audio stream that
would be "audio/L16;rate=44100;channels=2". If you don't have much encoding
power, try adding wavenc which just wraps the raw data in a container. If you
have the encoding power I'd try FLAC. That also reduces latency a bit. IIRC using
MP3 or Vorbis will increase the latency even more.
> I'll investigate other UPnP client options, or figure out a mime type
> configuration which media clients will accept in order to decode this
> format. This direct call to Pulseaudio is not a bad way to use Rygel
> actually, although I was hoping for family and other home network
> users to be able to do UPnP browsing through some kind of nice
> interface, like VLC or Rhythmbox, perhaps I can just write a simple
UPnP Browsing in VLC 2.x should work with Rygel. VLC 1.x has a semi-broken
UPnP implementation.
> GUI to connect desktops/etc to various systems around the house using
> curl and pacat, assuming I can figure out how to get the corresponding
> HTTP URLs for each source via some kind of UPnP library. Suggestions
> for a simple (console?) tool to query available UPnP trees to find the
> "Gst Launch" node?
I've a half-finished implementation of something like that on github:
https://github.com/phako/upnp-browse/
But I don't claim that there aren't better tools.
>
> I might be able to use this for audio connectivity from microphones
> too, now I've figured it out, save buying a new baby alarm! Can I get
> any control through Rygel to minimise buffering and hence reduce audio
> delay?
I've not yet investigated what causes the delay there. Could you file an
enhancement bug about that against the GstLaunch plugin? Thanks.
> Congratulations on the release!
Thanks.
_______________________________________________
rygel-list mailing list
rygel-
https://mail.gnome.org/mailman/listinfo/rygel-list
)
