[vdr] Best practices for running vdr-xine

Jan Ekholm jan.ekholm at smultron.net
Fri May 1 10:28:02 CEST 2009


On Wednesday 29 April 2009 17:47:46 Petri Helin wrote:
> On Wed, Apr 29, 2009 at 5:22 PM, Jan Ekholm <jan.ekholm at smultron.net> wrote:
> > I use the following:
> >
> > PLUGINS="-P\"xineliboutput --primary --local=none --remote=37890 --
> > post=tvtime:method=Linear,cheap_mode=1,pulldown=0,use_progressive_frame_f
> >lag=1\""
> >
> > So yeah, it's primary all right.
>
> You said earlier that you use HTTP to connect with your frontend. The
> xineliboutput README states the following:
>
> Using with other media players (mplayer, vlc, ...)
>
>    Primary device video and audio (without OSD or subtitles)
>    can be streamed from plugin control port to almost any media
>    player using http or rtsp.
>
> So, you might want to use a xine-based frontend (for example vdr-sxfe
> or xine-ui) with xvdr.

Ok, I tried vdr-sxfe and it indeed is a much better solution and the OSD works 
exactly as it should. It's really looking nice.

However, I still can see only a small subset of the channels that "normal" VDR 
can see. I somehow suspect it's due to my hw setup:

* 1 Hauppuage FF DVB-c 
* 1 Hauppuage FF DVB-c + CI 

The second card is the old primary card where the s-video is connected. I can 
only actually see channels that the second card *only* can tune into, i.e. a 
few encrypted channels for which the CI is used. All other normal open 
channels can not be seen using vdr-sxfe, I just get a "No signal" image. I 
suspect that the first DVB card is normally used for tuning into these 
channels, but that shouldn't matter, should it? 

If I could just get all channels shown this solution would totally rock my 
setup. :)

-- 
    Pets are always a great help in times of stress. And in times of 
    starvation too, o'course.
                                        -- Terry Pratchett, Small Gods




More information about the vdr mailing list