Maybe it would be an idea to explore running vdr-fbfe with the rpihddevice plugin, using the v4l api to send data to it? I guess the current code now implements itself a lot of the stuff needed to use xinelib, which could just be delegated to the v4l device. On 21 April 2015 at 12:06, Petri Hintukainen <phi@xxxxxxxxxx> wrote: > On ma, 2015-04-20 at 11:33 +0200, Torgeir Veimo wrote: >> Have you tried rpihddevice plugin with VDR on the rpi? It might work >> even smoother than using xinelinboutput, but you'd have to find a >> different setup for cec i suppose. >> >> http://projects.vdr-developer.org/git/vdr-plugin-rpihddevice.git/ > > Maybe when I get tired maintaining current xine-lib based solution :) > > Based on quick look at README it should have more solid HW support than > vdr-fbfe. The only thing I'd like to improve in vdr-fbfe is dynamically > changing video mode (interlacing, refresh rate, clock tweaking for live > mode). CEC shouldn't be a problem, it should be quite easy to add libcec > support with a separate VDR plugin. > > I think it requires some solution to delegate timers to server ? > > With vdr-fbfe I haven't noticed any delay caused by network or OSD > rendering (OSD is rendered at "powerful" server and the box is in wired > ethernet). But, I don't use ARGB osd or complex animated skins. > > > - Petri > > > _______________________________________________ > vdr mailing list > vdr@xxxxxxxxxxx > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- -Tor _______________________________________________ vdr mailing list vdr@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
