schirrms wrote: > Phil Raymond a écrit : > >> I use the Hauppauge HD PVR, which captures HD from the cable box using >> component cables, then converts it to h.264 AVCHD in a .mpg container. I >> posted a local_conf example in the Freevo wiki, it's just a simple stream >> dump, since this is a hardware encoder. Component out from an SD box would >> work, albeit not HD. It is a bit expensive, Amazon has it for $204 U.S., it >> lists for $249. The beauty of this device is that it will record anything >> from your cable box, even premium movie channels and on-demand content. >> >> >> >> > Hi Phil, > > Thanks for your answer. Unfortunately, the HD PVR is very expensive in > Europe, and I wasn't so confident to buy one in te United States. > So I finally bougth a 'not so cheap' Hauppauge PVR USB2. This thing is > really easy to setup, it's nearly a PCI PVR replacment, for freevo (and > for xin, too) ! > > So as you can guess, here I am with some questions ;-) > > First the setup : I setu the PVR USB3 like a PCI PVR card, so I use the > ivtv_xine_tv plugin to drive the beast. > * I was a little bit astonished when I did download the svn version of > freevo, as freevo states that the current version is still 1.8.4 ? So I > finally installed the tags/REL-1_9_1 version (and the current kaa svn > version). > Hi Pascal,
Can you let me know where and I'll change that? John > * When I started the tv plugin, I got a crash : > (I didn't recordthe exact message, but the trouble was when the ivtv.py > prog try first to read the 'Stream VBI Format', the just after to set > the same'Stream VBI Format'.) > To pass over, I just change in tv/ivtv.py, line 325 and 338 : > The original line was: > if self.version >= 0x800: > and I rplaced by > if self.version >= 0xF00: > > so this part of the test is false and the prog go further, with only a > short message : > 2009-11-07 18:48:52,193 WARNING ivtv.py (333): getvbiembed: failed > 2009-11-07 18:48:52,194 WARNING ivtv.py (345): setvbiembed: failed > > But I suppose that this is not the correct solution ! > > * Last (for now !), my system set the PVR box as /dev/video1. I setup > freevo according, but xine didn't like it. In fact, xine in the pvr/// > forms seems to connect only on /dev/viedo0, and google dind't help much, > this time. To be sure, I remove the webvcam driver (I currently use my > laptop for the test, so no, I cannot disconnect the webcam !), then the > pvrusb2 driver, and loaded then in the reverse order : pvrusb2 got the > /dev/video0 and I can watch TV (didn't do a lot of test for now !) > Is there a way to tell xine to use another device than /dev/video0, an > if so, is freevo 'aware' of that ? > > > Many many thanks, > Pascal > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Freevo-users mailing list > Freevo-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freevo-users > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
