Re: Compatibility issues with GstLaunch and 2 different players



Thanks.

I managed to find the same source version of rygel (0.22.1), applied the patch, compiled and installed.  Nothing changed.

I'm guessing that since the renderer is not a common one there won't be much interest in pursuing this.  So unless you think it worthwhile for the future of rygel I won't pursue it further.  If you want me to try to provide a tcp trace I'll look into it (I managed once before but to be honest can't recall how to do it).

Regards

Tim

On 31/05/14 16:45, Jens Georg wrote:

          
Hi,

I running rygel 0.22 on ubuntu 14.04.  I have 2 renderers, one a
Musical Fidelity M1CLiC (MF) and the other a Marantz CR603.  These
both successfully play my media library using rygel.  

However, what I want to do is us the GstLaunch plugin and the
pulseaudio upnp audio device to stream sound to them from other
sources.  This works with the Marantz but not the MF.

Having failed to read the FAQ properly (sorry!) it took me rather a
long time to find out how to get a debug log.  However I finally
managed to read the FAQ and do what it said!

With the Marantz the relevant section of the log is:

(rygel:30796): Rygel-DEBUG: rygel-http-server.vala:151: HTTP GET
request for URI
'http://192.168.1.2:39538/GstLaunch/i/YXVkaW90ZXN0c3Jj/tr/LPCM.lpcm'.
Headers:
(rygel:30796): Rygel-DEBUG: rygel-http-server.vala:155: Host :
192.168.1.2:39538
(rygel:30796): Rygel-DEBUG: rygel-http-server.vala:155: Icy-MetaData :
1
(rygel:30796): Rygel-DEBUG: rygel-http-server.vala:155: Connection :
close
(rygel:30796): Rygel-DEBUG: rygel-http-server.vala:155:
transferMode.dlna.org : Streaming
(rygel:30796): Rygel-DEBUG: rygel-http-server.vala:155: User-Agent :
WinampMPEG/2.8
(rygel:30796): Rygel-DEBUG: rygel-http-server.vala:155: Accept : */*
(rygel:30796): Rygel-DEBUG: rygel-http-get.vala:184: Following HTTP
headers appended to response:
(rygel:30796): Rygel-DEBUG: rygel-http-get.vala:186: Date : Fri, 30
May 2014 21:57:32 GMT
(rygel:30796): Rygel-DEBUG: rygel-http-get.vala:186: Content-Type :
audio/L16;rate=44100;channels=2
(rygel:30796): Rygel-DEBUG: rygel-http-get.vala:186:
transferMode.dlna.org : Streaming
(rygel:30796): Rygel-DEBUG: rygel-http-get.vala:186:
contentFeatures.dlna.org :
DLNA.ORG_PN=LPCM;DLNA.ORG_CI=1;DLNA.ORG_FLAGS=01700000000000000000000000000000
(rygel:30796): Rygel-DEBUG: rygel-http-get.vala:186: Connection :
close
(rygel:30796): MediaEngine-GStreamer-DEBUG:
rygel-gst-transcoder.vala:93: RygelL16Transcoder using the following
encoding profile:
(rygel:30796): MediaEngine-GStreamer-DEBUG:   audio:
(rygel:30796): MediaEngine-GStreamer-DEBUG:     Format: audio/x-raw,
format=(string)S16BE, channels=(int)2, rate=(int)44100



For the MF that doesn't work, the user agent is, strangely, the same,
but the initial dialogue shows a problem, and the console log reports:


(rygel:18388): Rygel-WARNING **: rygel-http-request.vala:105: Invalid
seek request 

The MF displays 'Track not found'
Yeah, that's a slight issue with GstLaunch, might be fixable through
code. See attached patch

If I need to get a full tcp dump I'll attempt that.

I have further queries, manly about how I can get a higher quality
stream (which I know is supported by the renderers because I have used
another streamer (foobar2000 upnp plugin) at up to 24/96000 quality.
However, the main problem is getting it to work at all.
a) Configure the pipeline so that it picks up the original one not
something transcoded; that should be done using something like


myaudiolpcm-title=LPCM audio on @HOSTNAME@
myaudiolpcm-dlnaprofile=LPCM
myaudiolpcm-mime=audio/L16;rate=44100;channels=2
myaudiolpcm-launch=pulsesrc device=upnp.monitor

and set enable-transcoding to false.

b) If that is picked up (receiver does not request an URI with /tr/ in
it), you can configure pulse to output an 24/96000 audio stream (no idea
how that works) and modify the section to

myaudiolpcm-title=LPCM audio on @HOSTNAME@
myaudiolpcm-dlnaprofile=LPCM
myaudiolpcm-mime=audio/L24;rate=96000;channels=2
myaudiolpcm-launch=pulsesrc device=upnp.monitor

That _could_ work. audio/L24 is not really supported by DLNA, so your
mileage may vary.

This is all for uncompressed audio.


_______________________________________________
rygel-list mailing list
rygel-list gnome org
https://mail.gnome.org/mailman/listinfo/rygel-list

-- 
email:    tim tim-passingham co uk
Home:     +44 1582 769668
Mobile:   +44 7736 371970
Skype:    timpassingham
facebook: Tim Passingham


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]