mike lewis wrote: > On 4/5/07, Juha Pahkala <[EMAIL PROTECTED]> wrote: >> mike lewis wrote: [...] >> Found this thread while fighting to get freevo 1.7 with vdr plugin >> going. It seems the current vdr plugin isn't working for anyone with 1.7 >> (below is the traceback from my trial). In the above mail thread Mike >> indicated that he might have a working version of it. Has anybody got it >> or another solution? Are you Mike reading this? >> > > Hi. How did you go? > > I have the vdr plugin working locally. I submitted patches but they > were never accepted as they need to go through sourceforge and I don't > have an account. They should be on the list though if you can find > them... > > I'm interested in this other plugin.. Does vdr still run in the > background when the the xinelib-out plugin is no longer being used? > Very interesting. This could be massaged directly for freevo 2.0 > support. I chose vdr-xine as i wanted vdr to record while I wa not > connected to it..
For Freevo 2.0, when the underlying kaa module will finally support xine-lib as a display engine also over DirectFB, this would enable a really smooth VDR integration via the xineliboutput plugin, as displaying the VDR interface would be almost just like rendering some media type supported by xine-lib (in this case, "VDR"). I imagine that a VDR skin tailored at Freevo's look & feel and a proper event handling management when displaying VDR via this route, could integrate VDR in a really transparent way, without having to duplicate and re-invent everything VDR can do sooo well (DVB-* and ivtv, I'm not saying it does good "normal" analogue TV, that's more a hack), in Python code (sorry Freevo dev folks, it's just my opinion, maybe other users also not centered only on one media project, but wanting to have the best of more than one project might also think similar). That's why there still are users who prefer using both VDR and Freevo, and I'm sorry I did not have time myself to maintain the vdr plugin for freevo, it's not even useful for me right now in any Freevo-1.x, as I'm no longer seeing VDR's OSD in df_xine or fbxine over DFB and did not have time to try to fix that. As I said, vdr-xineliboutput might be another good aproach, but for Freevo 2. I want to check if vdr-xineliboutput's DirectFB experience can reach to that of vdr-softdevice on my G400. If that's the case, and kaa.xine will soon work well under DirectFB, I might try again to get some time for this. Cheers, Lucian ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
