<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 9pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
You can use "make menuconfig" in /usr/src/multiproto and find the following information:<BR>
<BR>
Empia EM2800/2820/2840 USB video capture support (VIDEO_EM28XX) [N/m/?]<BR>
<BR>
Key the "N".<BR>
<BR>
Last,repeat "make".<BR><BR>> From: vdr-request@linuxtv.org<BR>> Subject: vdr Digest, Vol 42, Issue 11<BR>> To: vdr@linuxtv.org<BR>> Date: Sat, 12 Jul 2008 12:00:02 +0200<BR>> <BR>> Send vdr mailing list submissions to<BR>> vdr@linuxtv.org<BR>> <BR>> To subscribe or unsubscribe via the World Wide Web, visit<BR>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr<BR>> or, via email, send a message with subject or body 'help' to<BR>> vdr-request@linuxtv.org<BR>> <BR>> You can reach the person managing the list at<BR>> vdr-owner@linuxtv.org<BR>> <BR>> When replying, please edit your Subject line so it is more specific<BR>> than "Re: Contents of vdr digest..."<BR>> <BR>> <BR>> Today's Topics:<BR>> <BR>> 1. Re: multiproto_plus is ancient (Lauri Tischler)<BR>> 2. Re: multiproto_plus is ancient (Lauri Tischler)<BR>> 3. Re: multiproto_plus is ancient (Artem Makhutov)<BR>> 4. Control VDR with RF remote (Michael Stepanov)<BR>> 5. Vdr-xine OSD question (Todd Luliak)<BR>> 6. Re: Control VDR with RF remote (Peer Oliver Schmidt)<BR>> 7. Re: Vdr-xine OSD question ( Antti Sepp?l? )<BR>> 8. xine tvtime parameters explained (Lauri Tischler)<BR>> <BR>> <BR>> ----------------------------------------------------------------------<BR>> <BR>> Message: 1<BR>> Date: Fri, 11 Jul 2008 13:14:56 +0300<BR>> From: Lauri Tischler <lwgt@iki.fi><BR>> Subject: Re: [vdr] multiproto_plus is ancient<BR>> To: VDR Mailing List <vdr@linuxtv.org><BR>> Message-ID: <487732A0.6060904@iki.fi><BR>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed<BR>> <BR>> VDR User wrote:<BR>> > On Thu, Jul 10, 2008 at 4:13 AM, Lauri Tischler <lwgt@iki.fi> wrote:<BR>> >> What 'FF mod card' are you referring to ?<BR>> > <BR>> > There's a hardware hack to allow the full transport stream to be<BR>> > passed by the Nexus. By default it doesn't so when there's heavy<BR>> > load, a lot of packets are dropped.<BR>> > <BR>> >> I have basic Hauppauge NEXUS-S FF card and a pair of Hauppauge NOVA-T<BR>> >> cards, in near future I will get some S2 capable card.<BR>> >> So, what tree should I use for VDR 1.7.xx ?<BR>> > <BR>> > For a stock Nexus-s, you can use any tree. V4L with the vdr api<BR>> > wrapper patch, or *multiproto*.<BR>> <BR>> Hmmm.. compile error....<BR>> ----<BR>> CC [M] /usr/src/multiproto/v4l/em28xx-audio.o<BR>> In file included from /usr/src/multiproto/v4l/em28xx-audio.c:39:<BR>> include/sound/core.h:281: error: 'SNDRV_CARDS' undeclared here (not in a <BR>> function)<BR>> /usr/src/multiproto/v4l/em28xx-audio.c:58: error: array index in <BR>> initializer not of integer type<BR>> /usr/src/multiproto/v4l/em28xx-audio.c:58: error: (near initialization <BR>> for 'index')<BR>> make[3]: *** [/usr/src/multiproto/v4l/em28xx-audio.o] Error 1<BR>> make[2]: *** [_module_/usr/src/multiproto/v4l] Error 2<BR>> make[2]: Leaving directory `/usr/src/linux-headers-2.6.24-19-generic'<BR>> make[1]: *** [default] Error 2<BR>> make[1]: Leaving directory `/usr/src/multiproto/v4l'<BR>> ----<BR>> <BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 2<BR>> Date: Fri, 11 Jul 2008 16:13:05 +0300<BR>> From: Lauri Tischler <lwgt@iki.fi><BR>> Subject: Re: [vdr] multiproto_plus is ancient<BR>> To: VDR Mailing List <vdr@linuxtv.org><BR>> Message-ID: <48775C61.3050908@iki.fi><BR>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed<BR>> <BR>> Lauri Tischler wrote:<BR>> > VDR User wrote:<BR>> >> On Thu, Jul 10, 2008 at 4:13 AM, Lauri Tischler <lwgt@iki.fi> wrote:<BR>> >>> What 'FF mod card' are you referring to ?<BR>> >> There's a hardware hack to allow the full transport stream to be<BR>> >> passed by the Nexus. By default it doesn't so when there's heavy<BR>> >> load, a lot of packets are dropped.<BR>> >><BR>> >>> I have basic Hauppauge NEXUS-S FF card and a pair of Hauppauge NOVA-T<BR>> >>> cards, in near future I will get some S2 capable card.<BR>> >>> So, what tree should I use for VDR 1.7.xx ?<BR>> >> For a stock Nexus-s, you can use any tree. V4L with the vdr api<BR>> >> wrapper patch, or *multiproto*.<BR>> > <BR>> > Hmmm.. compile error....<BR>> > ----<BR>> > CC [M] /usr/src/multiproto/v4l/em28xx-audio.o<BR>> > In file included from /usr/src/multiproto/v4l/em28xx-audio.c:39:<BR>> > include/sound/core.h:281: error: 'SNDRV_CARDS' undeclared here (not in a <BR>> > function)<BR>> > /usr/src/multiproto/v4l/em28xx-audio.c:58: error: array index in <BR>> > initializer not of integer type<BR>> > /usr/src/multiproto/v4l/em28xx-audio.c:58: error: (near initialization <BR>> > for 'index')<BR>> > make[3]: *** [/usr/src/multiproto/v4l/em28xx-audio.o] Error 1<BR>> > make[2]: *** [_module_/usr/src/multiproto/v4l] Error 2<BR>> > make[2]: Leaving directory `/usr/src/linux-headers-2.6.24-19-generic'<BR>> > make[1]: *** [default] Error 2<BR>> > make[1]: Leaving directory `/usr/src/multiproto/v4l'<BR>> > ----<BR>> <BR>> otoh the v4l-dvb tree compiles just fine but multiproto does not.<BR>> <BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 3<BR>> Date: Fri, 11 Jul 2008 15:30:25 +0200<BR>> From: Artem Makhutov <artem@makhutov.org><BR>> Subject: Re: [vdr] multiproto_plus is ancient<BR>> To: VDR Mailing List <vdr@linuxtv.org><BR>> Message-ID: <20080711133025.GA23628@moelleritberatung.de><BR>> Content-Type: text/plain; charset=us-ascii<BR>> <BR>> Hi,<BR>> <BR>> On Fri, Jul 11, 2008 at 01:14:56PM +0300, Lauri Tischler wrote:<BR>> > VDR User wrote:<BR>> > > On Thu, Jul 10, 2008 at 4:13 AM, Lauri Tischler <lwgt@iki.fi> wrote:<BR>> > >> What 'FF mod card' are you referring to ?<BR>> > > <BR>> > > There's a hardware hack to allow the full transport stream to be<BR>> > > passed by the Nexus. By default it doesn't so when there's heavy<BR>> > > load, a lot of packets are dropped.<BR>> > > <BR>> > >> I have basic Hauppauge NEXUS-S FF card and a pair of Hauppauge NOVA-T<BR>> > >> cards, in near future I will get some S2 capable card.<BR>> > >> So, what tree should I use for VDR 1.7.xx ?<BR>> > > <BR>> > > For a stock Nexus-s, you can use any tree. V4L with the vdr api<BR>> > > wrapper patch, or *multiproto*.<BR>> > <BR>> > Hmmm.. compile error....<BR>> > ----<BR>> > CC [M] /usr/src/multiproto/v4l/em28xx-audio.o<BR>> > In file included from /usr/src/multiproto/v4l/em28xx-audio.c:39:<BR>> > include/sound/core.h:281: error: 'SNDRV_CARDS' undeclared here (not in a <BR>> > function)<BR>> > /usr/src/multiproto/v4l/em28xx-audio.c:58: error: array index in <BR>> > initializer not of integer type<BR>> > /usr/src/multiproto/v4l/em28xx-audio.c:58: error: (near initialization <BR>> > for 'index')<BR>> > make[3]: *** [/usr/src/multiproto/v4l/em28xx-audio.o] Error 1<BR>> > make[2]: *** [_module_/usr/src/multiproto/v4l] Error 2<BR>> > make[2]: Leaving directory `/usr/src/linux-headers-2.6.24-19-generic'<BR>> > make[1]: *** [default] Error 2<BR>> > make[1]: Leaving directory `/usr/src/multiproto/v4l'<BR>> > ----<BR>> <BR>> You need this patch:<BR>> <BR>> http://linuxtv.org/hg/v4l-dvb/raw-diff/b0815101889d/v4l/compat.h<BR>> <BR>> Please take a look at<BR>> http://www.linuxtv.org/pipermail/linux-dvb/2008-February/023819.html<BR>> <BR>> <BR>> Maybe the patch should be directly merged into the multiproto tree...<BR>> <BR>> Regards, Artem<BR>> <BR>> -- <BR>> Artem Makhutov<BR>> Unterort Str. 36<BR>> D-65760 Eschborn<BR>> <BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 4<BR>> Date: Fri, 11 Jul 2008 17:35:36 +0300<BR>> From: "Michael Stepanov" <michael@stepanoff.org><BR>> Subject: [vdr] Control VDR with RF remote<BR>> To: vdr@linuxtv.org<BR>> Message-ID:<BR>> <65922d730807110735o765771f4id685cdd7b6345a9@mail.gmail.com><BR>> Content-Type: text/plain; charset="iso-8859-1"<BR>> <BR>> Hi,<BR>> <BR>> Does anybody use RF remote control with VDR instead of IR? How to configure<BR>> such remotes?<BR>> <BR>> Thanks in advance.<BR>> <BR>> -- <BR>> Cheers,<BR>> Michael<BR>> -------------- next part --------------<BR>> An HTML attachment was scrubbed...<BR>> URL: http://www.linuxtv.org/pipermail/vdr/attachments/20080711/0ecc1aee/attachment-0001.htm <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 5<BR>> Date: Fri, 11 Jul 2008 10:10:14 -0700 (PDT)<BR>> From: Todd Luliak <javatodd32@yahoo.com><BR>> Subject: [vdr] Vdr-xine OSD question<BR>> To: vdr@linuxtv.org<BR>> Message-ID: <580290.30275.qm@web39807.mail.mud.yahoo.com><BR>> Content-Type: text/plain; charset="us-ascii"<BR>> <BR>> I am running vdr + vdr-xine plugin + coreavc + xine being output at<BR>> 1080i to an HDTV as the only display. Is there a simple way to lock the<BR>> OSD to the resolution of the output device such that the OSD is not<BR>> rescaled when switching between SD and HD sources? I played with<BR>> X-overlay, but that was not what I was after. If not, could it be done<BR>> in the source somewhere or is the OSD anti-aliased and overlayed on the<BR>> video before being sent to the output device (xine, in my case)? I've<BR>> looked around quite a bit on the net but I guess my google-foo is<BR>> failing me on this one. I just miss the rock-solid OSD of the FF card<BR>> setup...<BR>> <BR>> Thanks!<BR>> <BR>> <BR>> <BR>> <BR>> <BR>> -------------- next part --------------<BR>> An HTML attachment was scrubbed...<BR>> URL: http://www.linuxtv.org/pipermail/vdr/attachments/20080711/f6f5c05d/attachment-0001.htm <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 6<BR>> Date: Fri, 11 Jul 2008 21:04:07 +0200<BR>> From: Peer Oliver Schmidt <pos@theinternet.de><BR>> Subject: Re: [vdr] Control VDR with RF remote<BR>> To: VDR Mailing List <vdr@linuxtv.org><BR>> Message-ID: <4877AEA7.1070704@theinternet.de><BR>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed<BR>> <BR>> Hello Michael,<BR>> <BR>> > Does anybody use RF remote control with VDR instead of IR? How to <BR>> > configure such remotes?<BR>> <BR>> I used the ATI RemoteWonder with it. LIRC has support for it.<BR>> <BR>> ps: But you should stay with lmce ;)<BR>> -- <BR>> Best regards<BR>> <BR>> Peer Oliver Schmidt<BR>> the internet company<BR>> PGP Key ID: 0x83E1C2EA<BR>> <BR>> <BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 7<BR>> Date: Fri, 11 Jul 2008 22:14:01 +0300<BR>> From: " Antti Sepp?l? " <a.seppala+vdr@gmail.com><BR>> Subject: Re: [vdr] Vdr-xine OSD question<BR>> To: "VDR Mailing List" <vdr@linuxtv.org><BR>> Message-ID:<BR>> <5e1d45280807111214x5254127cu3f1f5533e5c23aa4@mail.gmail.com><BR>> Content-Type: text/plain; charset=ISO-8859-1<BR>> <BR>> 2008/7/11 Todd Luliak <javatodd32@yahoo.com>:<BR>> > I am running vdr + vdr-xine plugin + coreavc + xine being output at 1080i to<BR>> > an HDTV as the only display. Is there a simple way to lock the OSD to the<BR>> > resolution of the output device such that the OSD is not rescaled when<BR>> > switching between SD and HD sources? I played with X-overlay, but that was<BR>> > not what I was after. If not, could it be done in the source somewhere or is<BR>> > the OSD anti-aliased and overlayed on the video before being sent to the<BR>> > output device (xine, in my case)? I've looked around quite a bit on the net<BR>> > but I guess my google-foo is failing me on this one. I just miss the<BR>> > rock-solid OSD of the FF card setup...<BR>> > Thanks!<BR>> ><BR>> <BR>> In an effort to create something to solve such issues with<BR>> xineliboutput plugin I came up with an idea of this HUD type OSD.<BR>> Basically it means that OSD is rendered to a separate transparent<BR>> surface on top of video and then these are blended together by the<BR>> display hardware. This way the size of the OSD is bound to the size of<BR>> the used window rather than the size of the video stream. In other<BR>> words no OSD scaling will be necessary even though the video size<BR>> changes.<BR>> <BR>> The HUD implementation has been integrated into the CVS of<BR>> xineliboutput plugin. To operate it requires support for xorg render<BR>> extension and presence of composite display manager such as xcompmgr.<BR>> It also requires powerful display adapter and drivers with support for<BR>> these modern extensions. Maybe you can try it to see if it produces<BR>> results that you are hoping for?<BR>> <BR>> Regards,<BR>> <BR>> -- <BR>> Antti Sepp?l?<BR>> <a.seppala@gmail.com><BR>> <BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 8<BR>> Date: Sat, 12 Jul 2008 11:23:49 +0300<BR>> From: Lauri Tischler <lwgt@iki.fi><BR>> Subject: [vdr] xine tvtime parameters explained<BR>> To: VDR Mailing List <vdr@linuxtv.org><BR>> Message-ID: <48786A15.30804@iki.fi><BR>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed<BR>> <BR>> Trying to google for manual, info or article where all parameters for<BR>> xine tvtime command are explained, what they do, why, etc.<BR>> No luck yet, any pointers ??<BR>> <BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> _______________________________________________<BR>> vdr mailing list<BR>> vdr@linuxtv.org<BR>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr<BR>> <BR>> <BR>> End of vdr Digest, Vol 42, Issue 11<BR>> ***********************************<BR><BR><br /><hr />MSN上小游戏，工作休闲两不误！ <a href='http://im.live.cn/minigame' target='_new'>马上就开始玩！</a></body>
</html>