Re: Question about rygel transcoding ogg

[Jens Georg <mail jensge org>]

> Am Dienstag, den 01.09.2015, 13:04 +0200 schrieb Jens Georg:
> > >
> > > I have switched on transcoding,
> > > switched on transcoder to all (default) and (second try) only to mp3.
> > > switched off tracker, but switched on MediaExport.
> > >
> > > No error at rygel logging (but only missing users rygel.conf (have a
> > > global one)
> >
> > You can improve the logging by using export GST_MESSAGES_DEBUG=all and
> > run rygel with -g 5 cmmandline parameter. This will switch on 
> > debugging
> > output.
>
> ~$ export GST_MESSAGES_DEBUG=all
Sorry, mz bad, it's of course G_MESSAGES_DEBUG.


> ~$ rygel --log-level *:5
>
> (rygel:5214): Rygel-WARNING **: Benutzerkonfiguration konnte nicht von
> der Datei »/home/wolfgang/.config/rygel.conf« geladen werden: Datei 
> oder
> Verzeichnis nicht gefunden
> Rygel-Message: Rygel v0.24.2 wird ausgeführt …
> Rygel-Message: Neues Plugin »Playbin« ist verfügbar
> Rygel-Message: Neues Plugin »ZDFMediathek« ist verfügbar
> Rygel-Message: Neues Plugin »MediaExport« ist verfügbar
> MediaExport-Message: »file:///home/wolfgang/Musik« wurde abgesucht
>
> (rygel:5214): Rygel-WARNING **: rygel-http-request.vala:101: Invalid
> seek request

Crap. For that I need the User-Agent as well :(

> > This sounds a bit as if the Technisat is one of the devices that only
> > pays attention to the first resource it can find.
> > If you can provide me the User-Agent, I can try to add it to the hacks
> > that are needed for those devices. User-Agent should be printed when
> > using the debug output.
>
> What a pitty, it doesn't. there seem to be something wrong with the
> debuglevels. I set it to *:5 in .conf and in commandline, but no more
> debugmessages.
> Version is 0.24.2 from stable launchpad repos.

See above. my bad, I gave you the wrong environment variable.

> I activated mp3 and lpcm transcoder and tested with gmplayer and VLC
>
> ogg stream works perfectly, can play and seek, no debugmessages at the
> server.
>
> mp3 stream works, but no information about the title length,

Expected as we don't know the size beforehand and those clients don't
know anyhting about DLNA.

> Sometimes: (rygel:5214): Rygel-WARNING **: rygel-http-request.vala:101:
> Invalid seek request
>
> lpcm stream doesnt play at all:
> when starting there is only one of this
> (rygel:5214): Rygel-WARNING **: rygel-http-request.vala:101: Invalid
> seek request
> messages in rygel

Yeah, they try to do byte seeking which they shouldn't but they can't 
know.

> Should I switch to unstable releases (I read there is a new one)?

No, please stick with 0.24 for debugging purpose for now.