Re: [vdr] multiproto_plus is ancient of vdr Digest, Vol 42, Issue 11
You can use "make menuconfig" in /usr/src/multiproto and find the following information: Empia EM2800/2820/2840 USB video capture support (VIDEO_EM28XX) [N/m/?] Key the "N". Last,repeat "make".> From: [EMAIL PROTECTED]> Subject: vdr Digest, Vol 42, Issue 11> To: vdr@linuxtv.org> Date: Sat, 12 Jul 2008 12:00:02 +0200> > Send vdr mailing list submissions to> vdr@linuxtv.org> > To subscribe or unsubscribe via the World Wide Web, visit> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr> or, via email, send a message with subject or body 'help' to> [EMAIL PROTECTED]> > You can reach the person managing the list at> [EMAIL PROTECTED]> > When replying, please edit your Subject line so it is more specific> than "Re: Contents of vdr digest..."> > > Today's Topics:> > 1. Re: multiproto_plus is ancient (Lauri Tischler)> 2. Re: multiproto_plus is ancient (Lauri Tischler)> 3. Re: multiproto_plus is ancient (Artem Makhutov)> 4. Control VDR with RF remote (Michael Stepanov)> 5. Vdr-xine OSD question (Todd Luliak)> 6. Re: Control VDR with RF remote (Peer Oliver Schmidt)> 7. Re: Vdr-xine OSD question ( Antti Sepp?l? )> 8. xine tvtime parameters explained (Lauri Tischler)> > > ----------------------> > Message: 1> Date: Fri, 11 Jul 2008 13:14:56 +0300> From: Lauri Tischler <[EMAIL PROTECTED]>> Subject: Re: [vdr] multiproto_plus is ancient> To: VDR Mailing List > Message-ID: <[EMAIL PROTECTED]>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed> > VDR User wrote:> > On Thu, Jul 10, 2008 at 4:13 AM, Lauri Tischler <[EMAIL PROTECTED]> wrote:> >> What 'FF mod card' are you referring to ?> > > > There's a hardware hack to allow the full transport stream to be> > passed by the Nexus. By default it doesn't so when there's heavy> > load, a lot of packets are dropped.> > > >> I have basic Hauppauge NEXUS-S FF card and a pair of Hauppauge NOVA-T> >> cards, in near future I will get some S2 capable card.> >> So, what tree should I use for VDR 1.7.xx ?> > > > For a stock Nexus-s, you can use any tree. V4L with the vdr api> > wrapper patch, or *multiproto*.> > Hmmm.. compile error> > CC [M] /usr/src/multiproto/v4l/em28xx-audio.o> In file included from /usr/src/multiproto/v4l/em28xx-audio.c:39:> include/sound/core.h:281: error: 'SNDRV_CARDS' undeclared here (not in a > function)> /usr/src/multiproto/v4l/em28xx-audio.c:58: error: array index in > initializer not of integer type> /usr/src/multiproto/v4l/em28xx-audio.c:58: error: (near initialization > for 'index')> make[3]: *** [/usr/src/multiproto/v4l/em28xx-audio.o] Error 1> make[2]: *** [_module_/usr/src/multiproto/v4l] Error 2> make[2]: Leaving directory `/usr/src/linux-headers-2.6.24-19-generic'> make[1]: *** [default] Error 2> make[1]: Leaving directory `/usr/src/multiproto/v4l'> > > > > --> > Message: 2> Date: Fri, 11 Jul 2008 16:13:05 +0300> From: Lauri Tischler <[EMAIL PROTECTED]>> Subject: Re: [vdr] multiproto_plus is ancient> To: VDR Mailing List > Message-ID: <[EMAIL PROTECTED]>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed> > Lauri Tischler wrote:> > VDR User wrote:> >> On Thu, Jul 10, 2008 at 4:13 AM, Lauri Tischler <[EMAIL PROTECTED]> wrote:> >>> What 'FF mod card' are you referring to ?> >> There's a hardware hack to allow the full transport stream to be> >> passed by the Nexus. By default it doesn't so when there's heavy> >> load, a lot of packets are dropped.> >>> >>> I have basic Hauppauge NEXUS-S FF card and a pair of Hauppauge NOVA-T> >>> cards, in near future I will get some S2 capable card.> >>> So, what tree should I use for VDR 1.7.xx ?> >> For a stock Nexus-s, you can use any tree. V4L with the vdr api> >> wrapper patch, or *multiproto*.> > > > Hmmm.. compile error> > > > CC [M] /usr/src/multiproto/v4l/em28xx-audio.o> > In file included from /usr/src/multiproto/v4l/em28xx-audio.c:39:> > include/sound/core.h:281: error: 'SNDRV_CARDS' undeclared here (not in a > > function)> > /usr/src/multiproto/v4l/em28xx-audio.c:58: error: array index in > > initializer not of integer type> > /usr/src/multiproto/v4l/em28xx-audio.c:58: error: (near initialization > > for 'index')> > make[3]: *** [/usr/src/multip
Re: [vdr] multiproto_plus is ancient
Hi, On Fri, Jul 11, 2008 at 01:14:56PM +0300, Lauri Tischler wrote: > VDR User wrote: > > On Thu, Jul 10, 2008 at 4:13 AM, Lauri Tischler <[EMAIL PROTECTED]> wrote: > >> What 'FF mod card' are you referring to ? > > > > There's a hardware hack to allow the full transport stream to be > > passed by the Nexus. By default it doesn't so when there's heavy > > load, a lot of packets are dropped. > > > >> I have basic Hauppauge NEXUS-S FF card and a pair of Hauppauge NOVA-T > >> cards, in near future I will get some S2 capable card. > >> So, what tree should I use for VDR 1.7.xx ? > > > > For a stock Nexus-s, you can use any tree. V4L with the vdr api > > wrapper patch, or *multiproto*. > > Hmmm.. compile error > > CC [M] /usr/src/multiproto/v4l/em28xx-audio.o > In file included from /usr/src/multiproto/v4l/em28xx-audio.c:39: > include/sound/core.h:281: error: 'SNDRV_CARDS' undeclared here (not in a > function) > /usr/src/multiproto/v4l/em28xx-audio.c:58: error: array index in > initializer not of integer type > /usr/src/multiproto/v4l/em28xx-audio.c:58: error: (near initialization > for 'index') > make[3]: *** [/usr/src/multiproto/v4l/em28xx-audio.o] Error 1 > make[2]: *** [_module_/usr/src/multiproto/v4l] Error 2 > make[2]: Leaving directory `/usr/src/linux-headers-2.6.24-19-generic' > make[1]: *** [default] Error 2 > make[1]: Leaving directory `/usr/src/multiproto/v4l' > You need this patch: http://linuxtv.org/hg/v4l-dvb/raw-diff/b0815101889d/v4l/compat.h Please take a look at http://www.linuxtv.org/pipermail/linux-dvb/2008-February/023819.html Maybe the patch should be directly merged into the multiproto tree... Regards, Artem -- Artem Makhutov Unterort Str. 36 D-65760 Eschborn ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] multiproto_plus is ancient
Lauri Tischler wrote: > VDR User wrote: >> On Thu, Jul 10, 2008 at 4:13 AM, Lauri Tischler <[EMAIL PROTECTED]> wrote: >>> What 'FF mod card' are you referring to ? >> There's a hardware hack to allow the full transport stream to be >> passed by the Nexus. By default it doesn't so when there's heavy >> load, a lot of packets are dropped. >> >>> I have basic Hauppauge NEXUS-S FF card and a pair of Hauppauge NOVA-T >>> cards, in near future I will get some S2 capable card. >>> So, what tree should I use for VDR 1.7.xx ? >> For a stock Nexus-s, you can use any tree. V4L with the vdr api >> wrapper patch, or *multiproto*. > > Hmmm.. compile error > > CC [M] /usr/src/multiproto/v4l/em28xx-audio.o > In file included from /usr/src/multiproto/v4l/em28xx-audio.c:39: > include/sound/core.h:281: error: 'SNDRV_CARDS' undeclared here (not in a > function) > /usr/src/multiproto/v4l/em28xx-audio.c:58: error: array index in > initializer not of integer type > /usr/src/multiproto/v4l/em28xx-audio.c:58: error: (near initialization > for 'index') > make[3]: *** [/usr/src/multiproto/v4l/em28xx-audio.o] Error 1 > make[2]: *** [_module_/usr/src/multiproto/v4l] Error 2 > make[2]: Leaving directory `/usr/src/linux-headers-2.6.24-19-generic' > make[1]: *** [default] Error 2 > make[1]: Leaving directory `/usr/src/multiproto/v4l' > otoh the v4l-dvb tree compiles just fine but multiproto does not. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] multiproto_plus is ancient
VDR User wrote: > On Thu, Jul 10, 2008 at 4:13 AM, Lauri Tischler <[EMAIL PROTECTED]> wrote: >> What 'FF mod card' are you referring to ? > > There's a hardware hack to allow the full transport stream to be > passed by the Nexus. By default it doesn't so when there's heavy > load, a lot of packets are dropped. > >> I have basic Hauppauge NEXUS-S FF card and a pair of Hauppauge NOVA-T >> cards, in near future I will get some S2 capable card. >> So, what tree should I use for VDR 1.7.xx ? > > For a stock Nexus-s, you can use any tree. V4L with the vdr api > wrapper patch, or *multiproto*. Hmmm.. compile error CC [M] /usr/src/multiproto/v4l/em28xx-audio.o In file included from /usr/src/multiproto/v4l/em28xx-audio.c:39: include/sound/core.h:281: error: 'SNDRV_CARDS' undeclared here (not in a function) /usr/src/multiproto/v4l/em28xx-audio.c:58: error: array index in initializer not of integer type /usr/src/multiproto/v4l/em28xx-audio.c:58: error: (near initialization for 'index') make[3]: *** [/usr/src/multiproto/v4l/em28xx-audio.o] Error 1 make[2]: *** [_module_/usr/src/multiproto/v4l] Error 2 make[2]: Leaving directory `/usr/src/linux-headers-2.6.24-19-generic' make[1]: *** [default] Error 2 make[1]: Leaving directory `/usr/src/multiproto/v4l' ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] multiproto_plus is ancient
On Thu, Jul 10, 2008 at 10:55 AM, Goga777 <[EMAIL PROTECTED]> wrote: >> > I have basic Hauppauge NEXUS-S FF card and a pair of Hauppauge NOVA-T >> > cards, in near future I will get some S2 capable card. >> > So, what tree should I use for VDR 1.7.xx ? >> >> For a stock Nexus-s, you can use any tree. V4L with the vdr api >> wrapper patch, or *multiproto*. > > vdr 170 supports only new API (3.3) - miltiproto api. That's why you have to > install the multiproto As stated, you can use the V4L tree with vdr-1.7.x if you apply the api wrapper patch to vdr. For more, look here: http://www.udo-richter.de/vdr/patches.en.html#dvb-api-wrapper ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] multiproto_plus is ancient
> > What 'FF mod card' are you referring to ? > > There's a hardware hack to allow the full transport stream to be > passed by the Nexus. By default it doesn't so when there's heavy > load, a lot of packets are dropped. yes, the details you can find here http://www.escape-edv.de/endriss/dvb-full-ts-mod/ http://linuxtv.org/hg/~endriss/v4l-dvb-av7110-full-ts-mod > > I have basic Hauppauge NEXUS-S FF card and a pair of Hauppauge NOVA-T > > cards, in near future I will get some S2 capable card. > > So, what tree should I use for VDR 1.7.xx ? > > For a stock Nexus-s, you can use any tree. V4L with the vdr api > wrapper patch, or *multiproto*. vdr 170 supports only new API (3.3) - miltiproto api. That's why you have to install the multiproto Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] multiproto_plus is ancient
On Thu, Jul 10, 2008 at 4:13 AM, Lauri Tischler <[EMAIL PROTECTED]> wrote: > What 'FF mod card' are you referring to ? There's a hardware hack to allow the full transport stream to be passed by the Nexus. By default it doesn't so when there's heavy load, a lot of packets are dropped. > I have basic Hauppauge NEXUS-S FF card and a pair of Hauppauge NOVA-T > cards, in near future I will get some S2 capable card. > So, what tree should I use for VDR 1.7.xx ? For a stock Nexus-s, you can use any tree. V4L with the vdr api wrapper patch, or *multiproto*. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] multiproto_plus is ancient
Goga777 wrote: >> Any chance of having an upgrade to multiproto_plus tree ? >> I understand that multiproto_plus is the _only_ tree >> sanctioned by Klaus. > > why ? The regular multiproto can work with vdr 1700 too. If you don't have > FF mod card it's no any sense to use > multiproto_plus Hmmm, would somebody plse explain those requirements for dumb old me. What 'FF mod card' are you referring to ? I have basic Hauppauge NEXUS-S FF card and a pair of Hauppauge NOVA-T cards, in near future I will get some S2 capable card. So, what tree should I use for VDR 1.7.xx ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] multiproto_plus is ancient
> Any chance of having an upgrade to multiproto_plus tree ? > I understand that multiproto_plus is the _only_ tree > sanctioned by Klaus. why ? The regular multiproto can work with vdr 1700 too. If you don't have FF mod card it's no any sense to use multiproto_plus Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr