On Wed, Jan 12, 2011 at 11:15 AM, Tony Houghton <h...@realh.co.uk> wrote:
>>> 1. A stream server plugin.
>>> 2. An integrated player plugin based on xine.
>>> 3. Standalone xine-based players for connecting to the server.
>>> I propose using 1, ignoring 2 (you can disable it with CLI options, I do
>>> this anyway because it's more convenient for me to use a client-server
>>> setup) and replacing 3 with something based on ffmpeg and/or gstreamer.
>>> From xineliboutput's README:
>>> : (xine-lib is not required for server in network-only usage)
>>> network usage can include localhost.
>> And you get VDR's full osd doing this?
> Yes, if you use a libxine-based player which supports it (the support is
> now in libxine). So to replace xine with something else someone needs to
> work out how xineliboutput serves up the OSD and write something to read
> it. If it's embedded as private data packets or whatever in the TS I
> think it should be possible to hook into ffmpeg's or gstreamer's
> demuxers to get access to it.
So there's no vdr output plugin option available that uses ffmpeg for
vdpau decoding and also provides the user with VDR's osd.
Hopefully someone capable of writing an output plugin will take
interest after reading all the recent posts on the subject.
vdr mailing list