Re: [vdr] #error VDR requires Linux DVB driver API version 3.3! (was - VDR developer version 1.5.14)
On Jan 29, 2008 9:27 AM, VDR User [EMAIL PROTECTED] wrote: The only thing I did was edit the following line in Make.config: DVBDIR = /usr/local/src/multiproto/linux Everything worked fine without any modifying Makefile and so on. One of the most common problems with this is people not using the right path in that line. Ps. I'm using a copy of the Make.config example packaged with VDR. At the end of the file you can clearly see: ### You don't need to touch the following: ifdef DVBDIR INCLUDES += -I$(DVBDIR)/include endif ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] #error VDR requires Linux DVB driver API version 3.3! (was - VDR developer version 1.5.14)
Hi Tony, Tony Grant wrote: Sorry it doesn't. I RTFM and modified Make.config and I have the error so there is something wrong. I have the same here but if I modify the Makefile like described before the problem is fixed. It seems to me that the Makefile does not use DVBDIR. Best regards, Matthias -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning. -- Rich Cook ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] #error VDR requires Linux DVB driver API version3.3! (was - VDR developer version 1.5.14)
-Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Tony Grant Verzonden: dinsdag 29 januari 2008 13:55 Aan: [EMAIL PROTECTED]; VDR Mailing List Onderwerp: Re: [vdr] #error VDR requires Linux DVB driver API version3.3! (was - VDR developer version 1.5.14) Le mardi 29 janvier 2008 à 13:00 +0100, Ales Jurik a écrit : On Tuesday 29 January 2008, Matthias Fechner wrote: I modified now the Makefile and added the following lines after the include of the conf file: ifdef DVBDIR INCLUDES += -I$(DVBDIR)/include endif For plugins which are using the headerfiles from the new driver I had to add the three lines too. Is that a bug in the VDR Makefile? No, for such purposes there is Make.config.template which should be copied to Make.config (see doc). After line ### You don't need to touch the following: add something like (depends on your configuration) DVBDIR = /usr/local/src/dvb/linux and all will ok. This file is included by all Makefiles (also by plugins). Sorry it doesn't. I RTFM and modified Make.config and I have the error so there is something wrong. Tony [serge pecher] Take care that the lines ifdef DVBDIR ... are under the line INCLUDES =-I ... something with freetype (sorry I don't have a machine in front of me serge -- ___ 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] #error VDR requires Linux DVB driver API version 3.3! (was - VDR developer version 1.5.14)
The only thing I did was edit the following line in Make.config: DVBDIR = /usr/local/src/multiproto/linux Everything worked fine without any modifying Makefile and so on. One of the most common problems with this is people not using the right path in that line. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] statistic (was - Multiproto updated Re: [ANNOUNCE] VDR developer version1.5 .14)
Manu will be possibility to receive from driver the raw statistic, too ? Igor -Original Message- From: Manu Abraham [EMAIL PROTECTED] To: VDR Mailing List vdr@linuxtv.org Date: Mon, 28 Jan 2008 22:22:58 +0400 Subject: Re: [vdr] Multiproto updated Re: [ANNOUNCE] VDR developer version1.5.14 Morfsta wrote: Manu, Firstly, thanks for all your work - it's appreciated. Is the interface working properly for reading the signal strength, BER and status? Currently, there is a small confusion. Most drivers in kernel, just report some crap as signal strength, snr etc. For the STB0899, STM helped so much, alongwith i had some help from one of the Newtec guys, we were able to get the statistics in some proper form, currently a dBm/10 scale is used. Since this scale is different from the in kernel existing scale of randomness to a standardized one, currently this change might look a bit nonsense to you as it will report different signal statistics as reported by the API. There will be a need to add one more ioctl, where the user can request the driver to provide the statistics in a relative scale or an absolute scale which can be used for measurements too. The result would be that and end application can display the statistics like any other commercial STB, in a nice and beautiful way, while being quite accurate (depending on the driver) without any hacks or workarounds to be \ done in the application (The statistics that you get is very much device specific and not device independant and hence is not very easy for a user application to get proper statistics as of now) With the change, all statistics related operations can be implemented within the driver such that the user is presented with standard and uniform statistics across multiple devices without the need to do device specific code as done by MythTV etc, where it looks for specific device drivers (really ugly) The rotor plugin doesnt return anything and I can't get anything out of VDR-Femon. Is it working OK with the TT 3200? The statistics is working with the STB0899, maybe i didn't follow what exactly you are looking at. If you can detail a bit, it would be much more helpful. The STB0899 supports TT S2 3200, KNC1 DVB-S2+, KNC1 DVB-S2, Pinnacle PCTV 450e and the VP-1041 as of now and the same signal related stuff is applicable to all. BTW I have a TT3200 on order so I can compare the difference between the two cards soon. Currently, the STB0899 is _not_ calibrated for actual statistics. I have requested Azurewave for some sample devices to be sent to STM for proper calibration of the LUT's for the statistics. (Most probably, tomorrow or so STM will receive the samples at Grenoble) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] #error VDR requires Linux DVB driver API version 3.3! (was - VDR developer version 1.5.14)
Hi, Igor wrote: please, try to copy the files from /multiproto/linux/include/linux/dvb/version.h /multiproto/linux/include/linux/dvb/frontend.h to /usr/include/linux/dvb and recompile the VDR ok it was really a -I Problem with the compile process. I edited the Make.config but vdr doesn't seems to use it: DVBDIR = /usr/local/src/multiproto/multiproto/linux/ I modified now the Makefile and added the following lines after the include of the conf file: ifdef DVBDIR INCLUDES += -I$(DVBDIR)/include endif For plugins which are using the headerfiles from the new driver I had to add the three lines too. Is that a bug in the VDR Makefile? Best regards, Matthias -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning. -- Rich Cook ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Disabling Xineliboutput video mode switching
Samuli Seppänen [EMAIL PROTECTED] writes: Hi all, I have a problem with Xineliboutput's OSD. In low resolution videos it look doesn't fit the screen. It seems as if Xineliboutput actually switches the resolution of the (VGA) monitor. So how do I force Xineliboutput to first scale the _video_ to screen (not vice versa) and then put OSD (unscaled) on top of that? Same problem here. I'd prefer it to scale the osd the same way vdr-xine does. (i'm using xine as a remote frontend) -- ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] #error VDR requires Linux DVB driver API version 3.3! (was - VDR developer version 1.5.14)
Le mardi 29 janvier 2008 à 13:00 +0100, Ales Jurik a écrit : On Tuesday 29 January 2008, Matthias Fechner wrote: I modified now the Makefile and added the following lines after the include of the conf file: ifdef DVBDIR INCLUDES += -I$(DVBDIR)/include endif For plugins which are using the headerfiles from the new driver I had to add the three lines too. Is that a bug in the VDR Makefile? No, for such purposes there is Make.config.template which should be copied to Make.config (see doc). After line ### You don't need to touch the following: add something like (depends on your configuration) DVBDIR = /usr/local/src/dvb/linux and all will ok. This file is included by all Makefiles (also by plugins). Sorry it doesn't. I RTFM and modified Make.config and I have the error so there is something wrong. Tony -- ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] #error VDR requires Linux DVB driver API version 3.3! (was - VDR developer version 1.5.14)
On Tuesday 29 January 2008, Matthias Fechner wrote: I modified now the Makefile and added the following lines after the include of the conf file: ifdef DVBDIR INCLUDES += -I$(DVBDIR)/include endif For plugins which are using the headerfiles from the new driver I had to add the three lines too. Is that a bug in the VDR Makefile? No, for such purposes there is Make.config.template which should be copied to Make.config (see doc). After line ### You don't need to touch the following: add something like (depends on your configuration) DVBDIR = /usr/local/src/dvb/linux and all will ok. This file is included by all Makefiles (also by plugins). Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] wrong time in tv program
hello! the time in the vdr (right bottom) is displayed correctly but the time for the tv movies are displayed with a 7 hour displacement. e.g. the local time is 20:11 but the start time of the tv movie is displayed as 13:00. but the correct tv movie name is displayed. 'date' in the shell displays the correct time and also the correct timezone is set up in /etc/timezone as 'Europe/Berlin'. has anyone a solution? thx, martin -- Martin Schreiber http://www.martin-schreiber.net | Im Muehltal 48 | 91171 Greding | GERMANY ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] HVR4000(lite) support for multiproto
Hello! Does this patch support DVB-S2? I cant get it working with DVB-S2, it doesn't happen anything in VDR when I tries to zap to an S2 channel. I have been succesfully running with a older multiproto tree and the HVR4000 patch from Dec 07 earlier. Reagrds, Lars Fredriksson On Mon, Jan 28, 2008 at 06:06:37PM +0100, Holger Steinhaus wrote: Great thanks to Manu and Klaus for their latest updates. The attached patch adds HVR4000 support to it. It has been tested successfully together with kernel 2.6.24 on i686 using VDR 1.4.7 (DVB-S only) and VDR 1.5.14. Regards, Holger ___ 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] statistic (was - Multiproto updated Re: [ANNOUNCE] VDR developer version1.5.14)
Igor wrote: Manu will be possibility to receive from driver the raw statistic, too ? As of now, the STB0899 get's the raw statistics does processing and the processed details are sent to the application. It's possible to get the same, what you mentioned, just that the mentioned ioctl needs to be in there. The relative scale would be just raw statistics (unprocessed) Regards, Manu Igor -Original Message- From: Manu Abraham [EMAIL PROTECTED] To: VDR Mailing List vdr@linuxtv.org Date: Mon, 28 Jan 2008 22:22:58 +0400 Subject: Re: [vdr] Multiproto updated Re: [ANNOUNCE] VDR developer version1.5.14 Morfsta wrote: Manu, Firstly, thanks for all your work - it's appreciated. Is the interface working properly for reading the signal strength, BER and status? Currently, there is a small confusion. Most drivers in kernel, just report some crap as signal strength, snr etc. For the STB0899, STM helped so much, alongwith i had some help from one of the Newtec guys, we were able to get the statistics in some proper form, currently a dBm/10 scale is used. Since this scale is different from the in kernel existing scale of randomness to a standardized one, currently this change might look a bit nonsense to you as it will report different signal statistics as reported by the API. There will be a need to add one more ioctl, where the user can request the driver to provide the statistics in a relative scale or an absolute scale which can be used for measurements too. The result would be that and end application can display the statistics like any other commercial STB, in a nice and beautiful way, while being quite accurate (depending on the driver) without any hacks or workarounds to be \ done in the application (The statistics that you get is very much device specific and not device independant and hence is not very easy for a user application to get proper statistics as of now) With the change, all statistics related operations can be implemented within the driver such that the user is presented with standard and uniform statistics across multiple devices without the need to do device specific code as done by MythTV etc, where it looks for specific device drivers (really ugly) The rotor plugin doesnt return anything and I can't get anything out of VDR-Femon. Is it working OK with the TT 3200? The statistics is working with the STB0899, maybe i didn't follow what exactly you are looking at. If you can detail a bit, it would be much more helpful. The STB0899 supports TT S2 3200, KNC1 DVB-S2+, KNC1 DVB-S2, Pinnacle PCTV 450e and the VP-1041 as of now and the same signal related stuff is applicable to all. BTW I have a TT3200 on order so I can compare the difference between the two cards soon. Currently, the STB0899 is _not_ calibrated for actual statistics. I have requested Azurewave for some sample devices to be sent to STM for proper calibration of the LUT's for the statistics. (Most probably, tomorrow or so STM will receive the samples at Grenoble) ___ 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] #error VDR requires Linux DVB driver API version 3.3! (was - VDR developer version 1.5.14)
Hi, VDR User schrieb: Ps. I'm using a copy of the Make.config example packaged with VDR. At the end of the file you can clearly see: ### You don't need to touch the following: ifdef DVBDIR INCLUDES += -I$(DVBDIR)/include endif yes you are right. My buildscript copies the file from a fixed position to the VDR builddir. But I missed to upgrade my own config file. So it is fixed now thx. Bye, Matthias -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning. -- Rich Cook ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-rotor support patches for VDR-1.5.14
I forgot afther that patches 3 Patch vdr-1.5.14-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff and compile ok, if i change order 3 first then 2 i get errors above compiling vdr. Luc. Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-rotor support patches for VDR-1.5.14
Hy I say that i will be tester, so rotor patcheches aply fine and compile only in this order. 1. Rotor patch vdr-1.5.14-h264-other-rotor.diff to vdr-rotor-0.1.4-vdr-1.5 2. Rotor patch vdr-1.5.14-h264-other-rotor.diff to vdr. and compile ok but I could not testit because i meseed up my xine-lib tryng with core-avc that for me image is worst diferent then ffmpeg. I will post soon news, how i can see from patches now supports dvbs-2 or not? Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
