Re: [vdr] xbmc-pvr (was - HD clients for vdr)
Seppo Ingalsuo wrote: On Sun, 2009-08-23 at 09:05 -0700, VDR User wrote: Did you know that Klaus is giving VDR a new 24bit OSD? High resolution/high color will soon be in vanilla VDR, no expensive eHD card or otherwise required. ;) That's nice but my main problem with vdr is having two televisions + one computer that can be used for TV watching too. HD UI is not the main driver for me. There really should be a proper server/client(s) architecture with vdr. Possible HD UI development for vdr to be useful should be developed to operate as IP streaming client. I really do not understand the rage about HD OSD and/or skins. VDR is meant for watching TV-programs, like sports, movies, documents, and porno, not OSD. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xbmc-pvr (was - HD clients for vdr)
2009/8/24 Seppo Ingalsuo : > On Sun, 2009-08-23 at 09:05 -0700, VDR User wrote: > >> Did you know that Klaus is giving VDR a new 24bit OSD? High >> resolution/high color will soon be in vanilla VDR, no expensive eHD >> card or otherwise required. ;) > > That's nice but my main problem with vdr is having two televisions + one > computer that can be used for TV watching too. HD UI is not the main > driver for me. > > There really should be a proper server/client(s) architecture with vdr. > Possible HD UI development for vdr to be useful should be developed to > operate as IP streaming client. Maybe a streamosd plugin could provide what you need. -- -Tor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Turn off/relocate ts error logging
On 23.08.2009 22:44, Goga777 wrote: >>> Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (2) >>> Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (6) >>> Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (9) >>> Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (11) >>> Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (8) >> This doesn't come from VDR (any more), because it no longer uses >> cTS2PES. > > do you mean - since vdr 179 this warning should disappear ? > > with vdr 178 I have these warnings too > > Aug 23 20:21:14 arvdr logger: waiting for in_discontinuity update #214 > Aug 23 20:21:14 arvdr vdr: [3621] TS continuity error (2) > Aug 23 20:21:14 arvdr vdr: [3621] TS continuity error (1) > Aug 23 20:21:14 arvdr vdr: [3621] cAudioRepacker(0xC0): skipped 392 bytes to > sync on next audio frame > Aug 23 20:21:14 arvdr vdr: [3621] PES packet shortened to 3286 bytes > (expected: 3470 bytes) > Aug 23 20:21:14 arvdr vdr: [3621] TS continuity error (4) > Aug 23 20:21:14 arvdr vdr: [3621] PES packet shortened to 3286 bytes > (expected: 3470 bytes) > > > Aug 23 20:21:17 arvdr logger: video_out: throwing away image with pts > 55595230 because it's too old (diff : 58615). > Aug 23 20:21:17 arvdr vdr: [3168] cTS2PES got 0 TS errors, 2 TS continuity > errors > Aug 23 20:21:17 arvdr vdr: [3168] cTS2PES got 0 TS errors, 3 TS continuity > errors > Aug 23 20:21:17 arvdr logger: input_vdr: flush buffers (vb: 0, ab: 0, vf: 0, > af: 0) done. > Aug 23 20:21:17 arvdr vdr: [3622] TS buffer on device 1 thread ended > (pid=3168, tid=3622) > > > Aug 23 20:47:05 arvdr vdr: [3189] Sent DISEQC command: t V W15 [E0 10 38 F3] > W15 A W15 T > Aug 23 20:47:05 arvdr vdr: [4119] TS continuity error (7) > Aug 23 20:47:27 arvdr vdr: [3168] switching to channel 40 > > > Aug 23 20:47:27 arvdr vdr: [3168] cTS2PES got 0 TS errors, 1 TS continuity > errors VDR stopped using cTS2PES when it switched to TS recording format. I assume these messages are from the xine plugin, which I believe does still use cTS2PES. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Turn off/relocate ts error logging
> > Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (2) > > Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (6) > > Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (9) > > Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (11) > > Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (8) > > This doesn't come from VDR (any more), because it no longer uses > cTS2PES. do you mean - since vdr 179 this warning should disappear ? with vdr 178 I have these warnings too Aug 23 20:21:14 arvdr logger: waiting for in_discontinuity update #214 Aug 23 20:21:14 arvdr vdr: [3621] TS continuity error (2) Aug 23 20:21:14 arvdr vdr: [3621] TS continuity error (1) Aug 23 20:21:14 arvdr vdr: [3621] cAudioRepacker(0xC0): skipped 392 bytes to sync on next audio frame Aug 23 20:21:14 arvdr vdr: [3621] PES packet shortened to 3286 bytes (expected: 3470 bytes) Aug 23 20:21:14 arvdr vdr: [3621] TS continuity error (4) Aug 23 20:21:14 arvdr vdr: [3621] PES packet shortened to 3286 bytes (expected: 3470 bytes) Aug 23 20:21:17 arvdr logger: video_out: throwing away image with pts 55595230 because it's too old (diff : 58615). Aug 23 20:21:17 arvdr vdr: [3168] cTS2PES got 0 TS errors, 2 TS continuity errors Aug 23 20:21:17 arvdr vdr: [3168] cTS2PES got 0 TS errors, 3 TS continuity errors Aug 23 20:21:17 arvdr logger: input_vdr: flush buffers (vb: 0, ab: 0, vf: 0, af: 0) done. Aug 23 20:21:17 arvdr vdr: [3622] TS buffer on device 1 thread ended (pid=3168, tid=3622) Aug 23 20:47:05 arvdr vdr: [3189] Sent DISEQC command: t V W15 [E0 10 38 F3] W15 A W15 T Aug 23 20:47:05 arvdr vdr: [4119] TS continuity error (7) Aug 23 20:47:27 arvdr vdr: [3168] switching to channel 40 Aug 23 20:47:27 arvdr vdr: [3168] cTS2PES got 0 TS errors, 1 TS continuity errors ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.9
Anssi Hannula wrote: > Thank you. The bug is in libcap header file > /usr/include/sys/capability.h > > It does evil stuff like this: > > 25 /* > 26 * Make sure we can be included from userland by preventing > 27 * capability.h from including other kernel headers > 28 */ > 29 #define _LINUX_TYPES_H > 30 #define _LINUX_FS_H > 31 #define __LINUX_COMPILER_H > 32 #define __user > 33 > 34 typedef unsigned int __u32; > 35 typedef __u32 __le32; > > This completely prevents including /usr/include/linux/types.h, etc. > > It seems my distro has a patch that removes all the above lines to > resolve this issue. I'll try contacting libcap upstream on this issue. In the meantime, attached is a workaround that contains a clear comment describing the issue. -- Anssi Hannula Index: vdr-1.7.9/vdr.c === --- vdr-1.7.9/vdr.c +++ vdr-1.7.9/vdr.c 2009-08-23 23:26:15.935332431 +0300 @@ -32,7 +32,6 @@ #include #include #include -#include #include #include #include @@ -64,6 +63,9 @@ #include "tools.h" #include "transfer.h" #include "videodir.h" +// include this one last due to some versions of it being buggy: +// http://www.linuxtv.org/pipermail/vdr/2009-August/021194.html +#include #define MINCHANNELWAIT10 // seconds to wait between failed channel switchings #define ACTIVITYTIMEOUT 60 // seconds before starting housekeeping ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Turn off/relocate ts error logging
On 23.08.2009 20:03, Timothy D. Lenz wrote: > Form /var/log/user.log: > > Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (2) > Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (6) > Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (9) > Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (11) > Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (8) This doesn't come from VDR (any more), because it no longer uses cTS2PES. > But in looking at the log now with it having run a bit with good signal, I > find another log spam: > > Aug 23 10:44:18 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0 > Aug 23 10:44:39 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0 > Aug 23 10:44:39 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 65+65=2:0;68=eng,72=eng:0:0 > Aug 23 10:44:39 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0 > Aug 23 10:45:00 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0 > Aug 23 10:45:00 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 65+65=2:0;68=spa,72=spa:0:0 > Aug 23 10:45:00 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 81+81=2:0;84=eng,88=eng:0:0 > Aug 23 10:45:21 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0 > Aug 23 10:45:42 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 49+49=2:0;50=eng:0:0 > Aug 23 10:45:42 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 65+65=2:0;66=spa:0:0 > Aug 23 10:46:03 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0 > Aug 23 10:46:03 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 65+65=2:0;68=spa:0:0 > Aug 23 10:46:24 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0 > Aug 23 10:46:24 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 65+65=2:0;68=spa:0:0 > Aug 23 10:46:45 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0 > Aug 23 10:46:45 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 65+65=2:0;68=eng:0:0 > Aug 23 10:46:45 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0 > Aug 23 10:47:06 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 17+17=2:0;20=eng:0:0 > Aug 23 10:47:27 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0 > Aug 23 10:47:48 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0 > Aug 23 10:48:09 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0 > Aug 23 10:48:09 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 65+65=2:0;68=eng,72=eng:0:0 > Aug 23 10:48:09 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0 > Aug 23 10:48:30 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0 > Aug 23 10:48:30 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 65+65=2:0;68=spa,72=spa:0:0 > Aug 23 10:48:30 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 81+81=2:0;84=eng,88=eng:0:0 > Aug 23 10:48:51 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0 > Aug 23 10:49:12 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 49+49=2:0;50=eng:0:0 > Aug 23 10:49:12 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 65+65=2:0;66=spa:0:0 > Aug 23 10:49:33 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0 > Aug 23 10:49:33 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 65+65=2:0;68=spa:0:0 > Aug 23 10:49:54 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0 > Aug 23 10:49:54 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 65+65=2:0;68=spa:0:0 > Aug 23 10:50:16 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0 > Aug 23 10:50:16 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 65+65=2:0;68=eng:0:0 > Aug 23 10:50:16 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0 > Aug 23 10:50:36 LLLx64-32 vdr: [2230] changing pids of channel 0 from > 0+0=0:0:0:0 to 17+17=2:0;20=eng:0:0 > > > Don't know if that is VDR or something the atsc plugin is causing. I don't have any such messages with "channel 0" in any of my logs here. Klaus > - Original Message - > From: "Klaus Schmidinger" > To: > Sent: Sunday, August
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.9
Goga777 wrote: >> Which distribution and version are you using? > > debian sid kernel 2.6.30 > >> And package name where /usr/include/linux/types.h and related files >> would also help: >> rpm -qf /usr/include/linux/types.h (on rpm systems) >> dpkg -S /usr/include/linux/types.h (on deb systems, I think) > > arvdr:/usr/src/vdr-1.7.9# dpkg -S /usr/include/linux/types.h > linux-libc-dev: /usr/include/linux/types.h Thank you. The bug is in libcap header file /usr/include/sys/capability.h It does evil stuff like this: 25 /* 26 * Make sure we can be included from userland by preventing 27 * capability.h from including other kernel headers 28 */ 29 #define _LINUX_TYPES_H 30 #define _LINUX_FS_H 31 #define __LINUX_COMPILER_H 32 #define __user 33 34 typedef unsigned int __u32; 35 typedef __u32 __le32; This completely prevents including /usr/include/linux/types.h, etc. It seems my distro has a patch that removes all the above lines to resolve this issue. I'll try contacting libcap upstream on this issue. -- Anssi Hannula ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.9
> I have to use the following patch: > > --- vdr-1.7.5/vdr.c.orig2009-04-12 11:05:51.0 -0700 > +++ vdr-1.7.5/vdr.c 2009-04-12 11:07:08.0 -0700 > @@ -32,6 +32,7 @@ > #include > #include > #include > +#include > #include > #include > #include I checked and can confirm - vdr 179 compiled fine with this patch Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.9
On Sun, Aug 23, 2009 at 12:26 PM, Goga777 wrote: >> Have you tried the patch I posted? > > no, because I have already solved this problem (as I wrote in my previous > mail) > > > I could compile vdr 179 after of adding in dvbdevice.h string like > > typedef unsigned char __u8; It would be nice if you did so others with the same problem can see the result. Otherwise what's the point? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.9
> Which distribution and version are you using? debian sid kernel 2.6.30 > And package name where /usr/include/linux/types.h and related files > would also help: > rpm -qf /usr/include/linux/types.h (on rpm systems) > dpkg -S /usr/include/linux/types.h (on deb systems, I think) arvdr:/usr/src/vdr-1.7.9# dpkg -S /usr/include/linux/types.h linux-libc-dev: /usr/include/linux/types.h Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.9
Goga777 wrote: >> Run this: >> g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -E -DREMOTE_KBD >> -DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS0\" -D_GNU_SOURCE >> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE >> -DVIDEODIR=\"/video\" -DCONFDIR=\"/etc/vdr\" >> -DPLUGINDIR=\"./PLUGINS/lib\" -DLOCDIR=\"./locale\" >> -I/usr/include/freetype2 -I../s2-liplianin/linux/include -o >> vdr.processed.c vdr.c >> >> vdr.processed.c should contain the preprocessed C++ source code. Please >> attach it (provided it is not too large) or upload somewhere. > > vdr.processed.c.bz2 > http://slil.ru/27922128 Which distribution and version are you using? And package name where /usr/include/linux/types.h and related files would also help: rpm -qf /usr/include/linux/types.h (on rpm systems) dpkg -S /usr/include/linux/types.h (on deb systems, I think) -- Anssi Hannula ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.9
> > I did so exactly in my previous mail > > > > PS > > vdr 178 compiled fine with existing headers > > Have you tried the patch I posted? no, because I have already solved this problem (as I wrote in my previous mail) I could compile vdr 179 after of adding in dvbdevice.h string like typedef unsigned char __u8; http://vdrportal.de/board/thread.php?postid=806612&sid=21750376f0aea416e10c099a4a488686#post806612 Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.9
> Run this: > g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -E -DREMOTE_KBD > -DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS0\" -D_GNU_SOURCE > -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE > -DVIDEODIR=\"/video\" -DCONFDIR=\"/etc/vdr\" > -DPLUGINDIR=\"./PLUGINS/lib\" -DLOCDIR=\"./locale\" > -I/usr/include/freetype2 -I../s2-liplianin/linux/include -o > vdr.processed.c vdr.c > > vdr.processed.c should contain the preprocessed C++ source code. Please > attach it (provided it is not too large) or upload somewhere. vdr.processed.c.bz2 http://slil.ru/27922128 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.9
On Sun, Aug 23, 2009 at 12:07 PM, Goga777 wrote: > I did so exactly in my previous mail > > PS > vdr 178 compiled fine with existing headers Have you tried the patch I posted? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.9
> >> Maybe one of these includes in these files is missing? > > > > as you can see - no, everything is ok > > Confirm that you looked at the correct files: > > You should first look under ../s2-liplianin/linux/include/ in dir /usr/src/s2-liplianin/linux/include/linux there's not any mentioned you files you can have a look yourselves http://mercurial.intuxication.org/hg/s2-liplianin/file/ecdc9c389f8a/linux/include/ , and if the > file in question doesn't exist there, you should look under > /usr/include/ (note, not in /usr/src). I did so exactly in my previous mail PS vdr 178 compiled fine with existing headers Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.9
Goga777 wrote: Your headers seem broken. What should happen (i.e. in upstream kernel git) is: >>> let's have a look on my headers (debian sid kernel 2.6.30 s2-liplianin dvb) >> Did you look in /usr/include/linux/dvb/... or in /usr/src/linux/... ? > > /usr/src/s2-liplianin/linux > >> For compiling userspace stuff (which vdr for sure is), the versions >> in /usr/include are used. > > not so necessary > > it's possible to change this behaviour > > --> edit --> Make.config --> DVBDIR = /usr/src/s2-liplianin/linux Run this: g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -E -DREMOTE_KBD -DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS0\" -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DVIDEODIR=\"/video\" -DCONFDIR=\"/etc/vdr\" -DPLUGINDIR=\"./PLUGINS/lib\" -DLOCDIR=\"./locale\" -I/usr/include/freetype2 -I../s2-liplianin/linux/include -o vdr.processed.c vdr.c vdr.processed.c should contain the preprocessed C++ source code. Please attach it (provided it is not too large) or upload somewhere. -- Anssi Hannula ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.9
> > > Your headers seem broken. What should happen (i.e. in upstream kernel > > > git) is: > > > > let's have a look on my headers (debian sid kernel 2.6.30 s2-liplianin dvb) > > Did you look in /usr/include/linux/dvb/... or in /usr/src/linux/... ? /usr/src/s2-liplianin/linux > For compiling userspace stuff (which vdr for sure is), the versions > in /usr/include are used. not so necessary it's possible to change this behaviour --> edit --> Make.config --> DVBDIR = /usr/src/s2-liplianin/linux Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.9
I have to use the following patch: --- vdr-1.7.5/vdr.c.orig2009-04-12 11:05:51.0 -0700 +++ vdr-1.7.5/vdr.c 2009-04-12 11:07:08.0 -0700 @@ -32,6 +32,7 @@ #include #include #include +#include #include #include #include ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.9
Goga777 wrote: > Anssi Hannula wrote: >> Maybe one of these includes in these files is missing? > > as you can see - no, everything is ok Confirm that you looked at the correct files: You should first look under ../s2-liplianin/linux/include/, and if the file in question doesn't exist there, you should look under /usr/include/ (note, not in /usr/src). -- Anssi Hannula ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HD clients for vdr
On Sun, Aug 23, 2009 at 11:45 AM, Goga777 wrote: >> I use an 8400gs in two boxes and I don't get freezing video. > > do you mean 1080i video ? > which deinterlaicer are you using ? 1080i yes. It's falling back to temporal iirc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xbmc-pvr (was - HD clients for vdr)
On Sun, 2009-08-23 at 09:05 -0700, VDR User wrote: > Did you know that Klaus is giving VDR a new 24bit OSD? High > resolution/high color will soon be in vanilla VDR, no expensive eHD > card or otherwise required. ;) That's nice but my main problem with vdr is having two televisions + one computer that can be used for TV watching too. HD UI is not the main driver for me. There really should be a proper server/client(s) architecture with vdr. Possible HD UI development for vdr to be useful should be developed to operate as IP streaming client. Xbmc plus vdr as video streaming source & recorder seems to be a step into that direction. It could become a great option for vdr in the future. BR, Seppo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.9
On Sonntag, 23. August 2009, Goga777 wrote: > > Your headers seem broken. What should happen (i.e. in upstream kernel > > git) is: > > let's have a look on my headers (debian sid kernel 2.6.30 s2-liplianin dvb) Did you look in /usr/include/linux/dvb/... or in /usr/src/linux/... ? For compiling userspace stuff (which vdr for sure is), the versions in /usr/include are used. Regards Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HD clients for vdr
> I use an 8400gs in two boxes and I don't get freezing video. do you mean 1080i video ? which deinterlaicer are you using ? > my settings are different. I didn't have to change the values for the > following, they work by default: > > video.output.vdpau_enable_inverse_telecine:1 > video.output.vdpau_honor_progressive:0 > video.output.vdpau_skip_chroma_deinterlace:0 > engine.buffers.audio_num_buffers:230 > engine.buffers.video_num_buffers:500 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.9
> Your headers seem broken. What should happen (i.e. in upstream kernel > git) is: let's have a look on my headers (debian sid kernel 2.6.30 s2-liplianin dvb) > linux/dvb/frontend.h has: > #include I have it #ifndef _DVBFRONTEND_H_ #define _DVBFRONTEND_H_ #include > linux/types.h has: > #include my /usr/include/linux/types.h has it too #include #include > asm/types.h has: > #include my /usr/include/asm/types.h has it too #ifndef _ASM_X86_TYPES_H #define _ASM_X86_TYPES_H #include > asm-generic/int-ll64.h has: > typedef unsigned char __u8; no problem with asm-generic/int-ll64.h too * asm-generic/int-ll64.h * * Integer declarations for architectures which use "long long" * for 64-bit types. */ #ifndef _ASM_GENERIC_INT_LL64_H #define _ASM_GENERIC_INT_LL64_H #ifndef __ASSEMBLY__ /* * __xx is ok: it doesn't pollute the POSIX namespace. Use these in the * header files exported to user space */ typedef __signed__ char __s8; typedef unsigned char __u8; typedef __signed__ short __s16; typedef unsigned short __u16; typedef __signed__ int __s32; typedef unsigned int __u32; > Maybe one of these includes in these files is missing? as you can see - no, everything is ok I could compile vdr 179 after of adding in dvbdevice.h string like typedef unsigned char __u8; Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HD clients for vdr
On Sun, Aug 23, 2009 at 11:12 AM, Timothy D. Lenz wrote: > I've had a problem with seeminly under powered video card using a 8400gs > (g98) and little by little am finding out what settings are > needed: > > # vdpau: Try to recreate progressive frames from pulldown material > # bool, default: 1 > video.output.vdpau_enable_inverse_telecine:0 > > # vdpau: disable deinterlacing when progressive_frame flag is set > # bool, default: 0 > video.output.vdpau_honor_progressive:1 > > # vdpau: disable advanced deinterlacers chroma filter > # bool, default: 0 > video.output.vdpau_skip_chroma_deinterlace:1 > > # number of audio buffers > # numeric, default: 230 > engine.buffers.audio_num_buffers:500 > > # number of video buffers > # numeric, default: 500 > engine.buffers.video_num_buffers:1000 I use an 8400gs in two boxes and I don't get freezing video. However, my settings are different. I didn't have to change the values for the following, they work by default: video.output.vdpau_enable_inverse_telecine:1 video.output.vdpau_honor_progressive:0 video.output.vdpau_skip_chroma_deinterlace:0 engine.buffers.audio_num_buffers:230 engine.buffers.video_num_buffers:500 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.9
Goga777 wrote: > Hi > > I can't compile vdr 179 > > arvdr:/usr/src/vdr# LANG=C make > g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DREMOTE_KBD > -DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS0\" -D_GNU_SOURCE > -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE > -DVIDEODIR=\"/video\" -DCONFDIR=\"/etc/vdr\" -DPLUGINDIR=\"./PLUGINS/lib\" > -DLOCDIR=\"./locale\" -I/usr/include/freetype2 > -I../s2-liplianin/linux/include vdr.c > In file included from dvbdevice.h:14, > from vdr.c:45: > ../s2-liplianin/linux/include/linux/dvb/frontend.h:92: error: '__u8' does not > name a type > ../s2-liplianin/linux/include/linux/dvb/frontend.h:93: error: '__u8' does not > name a type > ../s2-liplianin/linux/include/linux/dvb/frontend.h:98: error: '__u8' does not > name a type > ../s2-liplianin/linux/include/linux/dvb/frontend.h:99: error: '__u8' does not > name a type > ../s2-liplianin/linux/include/linux/dvb/frontend.h:361: error: '__u8' does > not name a type > make: *** [vdr.o] Error 1 Your headers seem broken. What should happen (i.e. in upstream kernel git) is: linux/dvb/frontend.h has: #include linux/types.h has: #include asm/types.h has: #include asm-generic/int-ll64.h has: typedef unsigned char __u8; Maybe one of these includes in these files is missing? -- Anssi Hannula ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HD clients for vdr
I've had a problem with seeminly under powered video card using a 8400gs (g98)
and little by little am finding out what settings are
needed:
gui.dropped_frames_warning:0
# vdpau: HD deinterlace method
# { bob half temporal half temporal_spatial temporal temporal_spatial },
default: 3
#video.output.vdpau_deinterlace_method:temporal
# vdpau: Try to recreate progressive frames from pulldown material
# bool, default: 1
video.output.vdpau_enable_inverse_telecine:0
# vdpau: disable deinterlacing when progressive_frame flag is set
# bool, default: 0
video.output.vdpau_honor_progressive:1
# vdpau: disable advanced deinterlacers chroma filter
# bool, default: 0
video.output.vdpau_skip_chroma_deinterlace:1
# number of audio buffers
# numeric, default: 230
engine.buffers.audio_num_buffers:500
# number of video buffers
# numeric, default: 500
engine.buffers.video_num_buffers:1000
# default number of video frames
# numeric, default: 15
engine.buffers.video_num_frames:22
Turning off the droped frame warnings stops it from poping up the box with it
floods droped frames. Don't need a popup telling you
you are droping frames when you have freeze frame video
- Original Message -
From:
To:
Sent: Sunday, August 23, 2009 9:24 AM
Subject: Re: [vdr] HD clients for vdr
> >Yes, it has limitations but given the low power consumption it's still
> >impressive. The ION runs fine with advanced deinterlacer for 576i and
> >temporal for 1080i. A 9500GT can do advanced on 1080i but for me it's not
> >worth the extra heat and space. I have the computer on the back of my TV.
> >http://www.minhembio.com/magho
> >/Magnus
>
> Are you sure your ION can play 1080i with temporal? What is the source? I
> have tried a lot of HD-channels on Thor 0.8W without success and I have to
> use bob deinterlace filter or else the hardware drops frames.
>
> See:
> http://www.nvnews.net/vbulletin/showthread.php?t=136326&highlight=deinterlace
>
> I have installed Ubuntu 9.04 amd64 server with a minimum of services.
>
> /Svankan
>
>
> ___
> vdr mailing list
> vdr@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.9
Hi I can't compile vdr 179 arvdr:/usr/src/vdr# LANG=C make g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DREMOTE_KBD -DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS0\" -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DVIDEODIR=\"/video\" -DCONFDIR=\"/etc/vdr\" -DPLUGINDIR=\"./PLUGINS/lib\" -DLOCDIR=\"./locale\" -I/usr/include/freetype2 -I../s2-liplianin/linux/include vdr.c In file included from dvbdevice.h:14, from vdr.c:45: ../s2-liplianin/linux/include/linux/dvb/frontend.h:92: error: '__u8' does not name a type ../s2-liplianin/linux/include/linux/dvb/frontend.h:93: error: '__u8' does not name a type ../s2-liplianin/linux/include/linux/dvb/frontend.h:98: error: '__u8' does not name a type ../s2-liplianin/linux/include/linux/dvb/frontend.h:99: error: '__u8' does not name a type ../s2-liplianin/linux/include/linux/dvb/frontend.h:361: error: '__u8' does not name a type make: *** [vdr.o] Error 1 frontend.h │ 11035│Jun 6 01:12 │ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Turn off/relocate ts error logging
Form /var/log/user.log: Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (2) Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (6) Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (9) Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (11) Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (8) But in looking at the log now with it having run a bit with good signal, I find another log spam: Aug 23 10:44:18 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0 Aug 23 10:44:39 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0 Aug 23 10:44:39 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;68=eng,72=eng:0:0 Aug 23 10:44:39 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0 Aug 23 10:45:00 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0 Aug 23 10:45:00 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;68=spa,72=spa:0:0 Aug 23 10:45:00 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 81+81=2:0;84=eng,88=eng:0:0 Aug 23 10:45:21 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0 Aug 23 10:45:42 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;50=eng:0:0 Aug 23 10:45:42 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;66=spa:0:0 Aug 23 10:46:03 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0 Aug 23 10:46:03 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;68=spa:0:0 Aug 23 10:46:24 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0 Aug 23 10:46:24 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;68=spa:0:0 Aug 23 10:46:45 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0 Aug 23 10:46:45 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;68=eng:0:0 Aug 23 10:46:45 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0 Aug 23 10:47:06 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 17+17=2:0;20=eng:0:0 Aug 23 10:47:27 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0 Aug 23 10:47:48 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0 Aug 23 10:48:09 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0 Aug 23 10:48:09 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;68=eng,72=eng:0:0 Aug 23 10:48:09 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0 Aug 23 10:48:30 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0 Aug 23 10:48:30 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;68=spa,72=spa:0:0 Aug 23 10:48:30 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 81+81=2:0;84=eng,88=eng:0:0 Aug 23 10:48:51 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0 Aug 23 10:49:12 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;50=eng:0:0 Aug 23 10:49:12 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;66=spa:0:0 Aug 23 10:49:33 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0 Aug 23 10:49:33 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;68=spa:0:0 Aug 23 10:49:54 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0 Aug 23 10:49:54 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;68=spa:0:0 Aug 23 10:50:16 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0 Aug 23 10:50:16 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;68=eng:0:0 Aug 23 10:50:16 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0 Aug 23 10:50:36 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 17+17=2:0;20=eng:0:0 Don't know if that is VDR or something the atsc plugin is causing. - Original Message - From: "Klaus Schmidinger" To: Sent: Sunday, August 23, 2009 2:15 AM Subject: Re: [vdr] Turn off/relocate ts error logging > On 22.08.2009 19:12, Timothy D. Lenz wrote: > > My log files get so big it,s very hard to check them because of the ts > > error messages that get flooded to it. I've had logs near 2gb > > in size. I have a problem with xine crashing when there is a weak signal > > and the ts loging bloating the log fi
Re: [vdr] HD clients for vdr
>Yes, it has limitations but given the low power consumption it's still >impressive. The ION runs fine with advanced deinterlacer for 576i and >temporal for 1080i. A 9500GT can do advanced on 1080i but for me it's not >worth the extra heat and space. I have the computer on the back of my TV. >http://www.minhembio.com/magho >/Magnus Are you sure your ION can play 1080i with temporal? What is the source? I have tried a lot of HD-channels on Thor 0.8W without success and I have to use bob deinterlace filter or else the hardware drops frames. See: http://www.nvnews.net/vbulletin/showthread.php?t=136326&highlight=deinterlace I have installed Ubuntu 9.04 amd64 server with a minimum of services. /Svankan ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xbmc-pvr (was - HD clients for vdr)
On Sun, Aug 23, 2009 at 1:46 AM, Seppo Ingalsuo wrote: > Othervise xbmc-vdr looks very promising with totally new high definition > UI. Did you know that Klaus is giving VDR a new 24bit OSD? High resolution/high color will soon be in vanilla VDR, no expensive eHD card or otherwise required. ;) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] VDR developer version 1.7.9
VDR developer version 1.7.9 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.7.9.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.7.8-1.7.9.diff WARNING: This is a *developer* version. Even though *I* use it in my productive environment. I strongly recommend that you only use it under controlled conditions and for testing and debugging. The changes since version 1.7.8: - Fixed storing the current OSD size in case the device has changed it in its setup menu (reported by Reinhard Nissl). - Fixed cDevice::PlayTsVideo() and cDevice::PlayTsAudio() in case only part of the buffer has been accepted by the device (reported by Udo Richter). - Changed the EIT filter setup to save a few handles on devices that do hardware filtering. - Fixed deleting expired timers if they have the VPS flag set, but the event they are assigned to doesn't have a VPS tag. - Fixed handling file name length on VFAT systems in case they contain UTF-8 characters (thanks to Rolf Ahrenberg). - Fixed generating CaPmts in case audio and video are encrypted using different ECM pids. - Updated vdr.1 to use the new file names in recording directories. - Fixed cRecordings::DelByName() to avoid compilation errors with gcc 4.4 (thanks to Matthias Schwarzott). - Increased the value of MAXFRAMESIZE to better suit HD recordings (thanks to Reinhard Nissl). - Implemented full handling of subtitling descriptors (thanks to Mikko Tuumanen). Have fun! Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Turn off/relocate ts error logging
On 22.08.2009 19:12, Timothy D. Lenz wrote: > My log files get so big it,s very hard to check them because of the ts error > messages that get flooded to it. I've had logs near 2gb > in size. I have a problem with xine crashing when there is a weak signal and > the ts loging bloating the log files is creating a lot > of problems. Need a way to turn off ts error loging or relocate to another > file. Are these reports coming from the core VDR or from xine? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xbmc-pvr (was - HD clients for vdr)
On Sat, 2009-08-22 at 22:43 +0300, Seppo Ingalsuo wrote: > Now xbmc connects to vdr server and gets first radio channels, then tv > channels and then nothing happens. Now after PC and xbmc restart live tv works. Even DVB subtitles are shown! How should I access vdr recordings from xbmc? Should I somehow import vdr directory (NFS share) to xbmc video library? I'm also wondering when vdr channnels and particularly EPG are updated. Is it only when xbmc is restarted? Now I don't see EPG for satellite channels that provide only now & next or very short some hours EPG. Othervise xbmc-vdr looks very promising with totally new high definition UI. BR, Seppo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
