Re: [vdr] [ANNOUNCE] VDR developer version 1.7.23
Hi, Am 23.01.2012 05:43, schrieb Hawes, Mark: I have updated my current build taken from the Media Build Tree last Tuesday with the contents of the linux media tarball dated 22/01/2012 and rebuilt my drivers. I still get the same results. As the system initialises the following lines appear in the syslog: Jan 23 12:16:44 Nutrigrain kernel: [9.338720] tuner-simple 16-0061: couldn't set type to 63. Using 78 (Philips FMD1216MEX MK3 Hybrid Tuner) instead Jan 23 12:16:44 Nutrigrain kernel: [9.346240] DVB: registering adapter 1 frontend 0 (Conexant CX24116/CX24118)... Jan 23 12:16:44 Nutrigrain kernel: [9.349110] DVB: registering adapter 1 frontend 1 (Conexant CX22702 DVB-T)... Subsequently when starting VDR the following is logged: Jan 23 13:10:13 Nutrigrain vdr: [2704] registered source parameters for 'A - ATSC' Jan 23 13:10:13 Nutrigrain vdr: [2704] registered source parameters for 'C - DVB-C' Jan 23 13:10:13 Nutrigrain vdr: [2704] registered source parameters for 'S - DVB-S' Jan 23 13:10:13 Nutrigrain vdr: [2704] registered source parameters for 'T - DVB-T' Jan 23 13:10:13 Nutrigrain vdr: [2704] probing /dev/dvb/adapter0/frontend0 Jan 23 13:10:13 Nutrigrain vdr: [2704] new device number 1 Jan 23 13:10:13 Nutrigrain vdr: [2704] frontend 0/0 provides DVB-S with QPSK (ST STV0299 DVB-S) Jan 23 13:10:13 Nutrigrain vdr: [2708] tuner on frontend 0/0 thread started (pid=2704, tid=2708) Jan 23 13:10:13 Nutrigrain vdr: [2709] section handler thread started (pid=2704, tid=2709) Jan 23 13:10:13 Nutrigrain vdr: [2704] probing /dev/dvb/adapter1/frontend0 Jan 23 13:10:13 Nutrigrain vdr: [2704] new device number 2 Jan 23 13:10:14 Nutrigrain vdr: [2706] video directory scanner thread ended (pid=2704, tid=2706) Jan 23 13:10:14 Nutrigrain vdr: [2705] video directory scanner thread ended (pid=2704, tid=2705) Jan 23 13:10:19 Nutrigrain vdr: [2704] frontend 1/0 provides DVB-S,DVB-S2 with QPSK (Conexant CX24116/CX24118) Jan 23 13:10:19 Nutrigrain vdr: [2712] tuner on frontend 1/0 thread started (pid=2704, tid=2712) Jan 23 13:10:19 Nutrigrain vdr: [2713] section handler thread started (pid=2704, tid=2713) Jan 23 13:10:24 Nutrigrain vdr: [2704] ERROR (dvbdevice.c,1087): /dev/dvb/adapter1/frontend1: Device or resource busy Jan 23 13:10:24 Nutrigrain vdr: [2704] found 2 DVB devices I'm sure that I have the latest drivers loaded now, but still the same issue. The only conclusion that I can come to is that the necessary changes to the drivers have not (yet) been made. Has anyone else tried VDR 1.7.23 with a HVR 4000 hybrid card and if so, do you get the same results? Yes, I would get to the same conclusion. There should only be one frontend. You should point the guys on the linux-media mailing list to this bug. Lars. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.23
Hi, The media_build repo contains only backported drivers. Are you sure that the new api changes were backported? The mainstream development happens in media_tree only, which contains a complete kernel snapshot. HTH. Halim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.23
On Mon, Jan 23, 2012 at 9:46 AM, Halim Sahin halim.sa...@t-online.de wrote: Hi, The media_build repo contains only backported drivers. Are you sure that the new api changes were backported? The media_build repo is a daily snapshot of what you'd get with media_tree (minus the kernel source itself). ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.23
Hi I have updated my DVB drivers using: git clone git://linuxtv.org/media_build.git cd media_build ./build make install Yet VDR complains of the wrong DVB API version number: dvbdevice.h:18:2: error: #error VDR requires Linux DVB driver API version 5.3 or higher! /usr/include/linux/dvb/version.h reports version 5.2 and the date of the file is old, meaning it was not updated when the drivers were updated. Can anybody explain what has gone wrong here? Thanks --- On Sun, 15/1/12, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: From: Klaus Schmidinger klaus.schmidin...@tvdr.de Subject: [vdr] [ANNOUNCE] VDR developer version 1.7.23 To: vdr@linuxtv.org Date: Sunday, 15 January, 2012, 15:10 VDR developer version 1.7.23 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.23.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.22-1.7.23.diff MD5 checksums: de136f7be28c4b6f1fa0e2218b4acc11 vdr-1.7.23.tar.bz2 2977b75cd8dacad187d11c10b867d56a vdr-1.7.22-1.7.23.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.22: - Removed the '.pl' suffix from svdrpsend.pl (sorry, I missed that one). - Fixed bonding more than two devices. - Fixed handling symbolic links in cRecordings::ScanVideoDir() (reported by Sundararaj Reel). - Fixed a memory leak in cRecordings::ScanVideoDir() in case there are too many link levels (reported by Sundararaj Reel). - Removed redundant memset() in the ctor of cSatCableNumbers (triggered by Ville Skyttä pointing out that the argument sequence in the call was wrong). - Removed a redundant NULL check in cDvbSpuDecoder::setTime() (thanks to Ville Skyttä). - Added HasSnr to the DEBUG_SIGNALQUALITY output in cDvbTuner::GetSignalQuality() (triggered by Ville Skyttä pointing out that the variable HasSnr was unused). - Updated the Finnish OSD texts (thanks to Rolf Ahrenberg). - Added support for HbbTV to libsi (thanks to Christoph Haubrich). - Added support for devices with more than one delivery system per frontend. This requires a DVB driver with version 5.5 or higher that can handle the DTV_ENUM_DELSYS call. With older drivers it will fall back to one delivery system per frontend. - Updated the Hungarian language texts (thanks to István Füley). - cDvbTuner::ExecuteDiseqc() now makes sure only one tuner sends SCR commands at any given time (reported by Frank Neumann). - cEvent::FixEpgBugs() now replaces any newline characters in stream component descriptions with blanks (thanks to Torsten Lang for reporting a problem with EPG data from BSkyB's MTV MUSIC, S28.2E-2-2010-7012). - Fixed cDvbSubtitleConverter::SetOsdData() (thanks to Rolf Ahrenberg). - Fixed cListBase::Move() in case From and To are equal (reported by Sundararaj Reel). - Added support for DVB-T2 to libsi (thanks to Rolf Ahrenberg). - Added support for handling DVB-T2 transponders. This requires a DVB driver with version 5.3 or higher that can handle the DTV_DVBT2_PLP_ID call (thanks to Rolf Ahrenberg). - Fixed cConfig::Load() for g++ version 4.7.0 (thanks to Ville Skyttä). - Fixed a possible memory corruption in cTsToPes::GetPes() in case of broken TS packets, e.g. when switching channels. - Fixed the SVDRP command CLRE for a single channel in case there are events that have a timer (thanks to Timo Eskola). - BIDI support now checks at runtime whether the system runs with UTF-8 (suggested by Torsten Lang). - Added member functions Adapter() and Frontend() to cDvbDevice (suggested by Rolf Ahrenberg). - The parameters that are only used by second generation delivery systems (DVB-S2 and DVB-T2) are no longer written into channels.conf for first generation delivery systems (DVB-S and DVB-T). - Changed IndexToHMSF() so that it can handle negative Index values. - Added option -N to the msgmerge call in the Makefile, because fuzzy translation mostly resulted in useless strings. - The new setup option Replay/Show remaining time can be used to switch between showing the total length or the remaining time of the recording that is currently replayed. - Fixed wrongfully displaying the length of a recording in the title of the replay progress display. - Fixed frozen live view with device bonding in case the bonded master is used for live viewing (reported by Uwe Scheffler). Have fun! Klaus ___ 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.23
Thanks I pointed Make.config to the media_build/linux directory and built that way. I'm surprised because I fully expected the media_build script to install the headers to. --- On Sun, 22/1/12, Ian Bates ian_and_joa...@talktalk.net wrote: From: Ian Bates ian_and_joa...@talktalk.net Subject: Re: [vdr] [ANNOUNCE] VDR developer version 1.7.23 To: VDR Mailing List vdr@linuxtv.org Date: Sunday, 22 January, 2012, 12:40 Hi, Something to try: *Short answer* Make sure VDR Make.config points to the appropriate media_build directory (DVBDIR variable) *Longer answer* I'm not sure a simple 'install' of the DVB drivers changes any system headers. So VDR needs to point the headers relevant to the available modules. 1. Ensure you really have built and installed the media_build DVB stack. 2. Point VDR Make.config to your git media_build directory NOTE '/linux' suffix: ... # From my vdr Make.config: #DVBDIR = /usr/local/src/v4l-dvb/current/linux #DVBDIR = /usr/local/src/linux-tbs-drivers/current/linux DVBDIR = /usr/local/src/linux-tbs-drivers/testing/linux # Change to where you have downloaded and built your DVB stuff DVBDIR = /usr/local/src/dvb/media_build-git/linux ... 3. make VDR and install If you have followed these steps already then I'm sorry not to add anything new. Regards, Ian. On 22 Jan 2012, at 11:03, Stuart Morris wrote: Hi I have updated my DVB drivers using: git clone git://linuxtv.org/media_build.git cd media_build ./build make install Yet VDR complains of the wrong DVB API version number: dvbdevice.h:18:2: error: #error VDR requires Linux DVB driver API version 5.3 or higher! /usr/include/linux/dvb/version.h reports version 5.2 and the date of the file is old, meaning it was not updated when the drivers were updated. Can anybody explain what has gone wrong here? Thanks --- On Sun, 15/1/12, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: From: Klaus Schmidinger klaus.schmidin...@tvdr.de Subject: [vdr] [ANNOUNCE] VDR developer version 1.7.23 To: vdr@linuxtv.org Date: Sunday, 15 January, 2012, 15:10 VDR developer version 1.7.23 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.23.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.22-1.7.23.diff MD5 checksums: de136f7be28c4b6f1fa0e2218b4acc11 vdr-1.7.23.tar.bz2 2977b75cd8dacad187d11c10b867d56a vdr-1.7.22-1.7.23.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.22: - Removed the '.pl' suffix from svdrpsend.pl (sorry, I missed that one). - Fixed bonding more than two devices. - Fixed handling symbolic links in cRecordings::ScanVideoDir() (reported by Sundararaj Reel). - Fixed a memory leak in cRecordings::ScanVideoDir() in case there are too many link levels (reported by Sundararaj Reel). - Removed redundant memset() in the ctor of cSatCableNumbers (triggered by Ville Skyttä pointing out that the argument sequence in the call was wrong). - Removed a redundant NULL check in cDvbSpuDecoder::setTime() (thanks to Ville Skyttä). - Added HasSnr to the DEBUG_SIGNALQUALITY output in cDvbTuner::GetSignalQuality() (triggered by Ville Skyttä pointing out that the variable HasSnr was unused). - Updated the Finnish OSD texts (thanks to Rolf Ahrenberg). - Added support for HbbTV to libsi (thanks to Christoph Haubrich). - Added support for devices with more than one delivery system per frontend. This requires a DVB driver with version 5.5 or higher that can handle the DTV_ENUM_DELSYS call. With older drivers it will fall back to one delivery system per frontend. - Updated the Hungarian language texts (thanks to István Füley). - cDvbTuner::ExecuteDiseqc() now makes sure only one tuner sends SCR commands at any given time (reported by Frank Neumann). - cEvent::FixEpgBugs() now replaces any newline characters in stream component descriptions with blanks (thanks to Torsten Lang for reporting a problem with EPG data from BSkyB's MTV MUSIC, S28.2E-2-2010-7012). - Fixed cDvbSubtitleConverter::SetOsdData() (thanks to Rolf Ahrenberg). - Fixed cListBase::Move() in case From and To are equal (reported by Sundararaj Reel). - Added support for DVB-T2 to libsi (thanks to Rolf Ahrenberg). - Added support for handling DVB-T2 transponders. This requires a DVB driver with version 5.3 or higher that can handle the DTV_DVBT2_PLP_ID call (thanks to Rolf Ahrenberg). - Fixed cConfig::Load() for g++ version 4.7.0 (thanks to Ville Skyttä). - Fixed a possible memory
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.23
I also had to copy compiler.h from my kernel sources to the media_build directory otherwise various plugins would not compile. cp /usr/src/kernels/2.6.35.14-96.fc14.i686.PAE/include/linux/compiler.h /usr/local/src/media_build/linux/include/linux/ --- On Sun, 22/1/12, Stuart Morris stuart_mor...@talk21.com wrote: From: Stuart Morris stuart_mor...@talk21.com Subject: Re: [vdr] [ANNOUNCE] VDR developer version 1.7.23 To: VDR Mailing List vdr@linuxtv.org Date: Sunday, 22 January, 2012, 14:50 Thanks I pointed Make.config to the media_build/linux directory and built that way. I'm surprised because I fully expected the media_build script to install the headers to. --- On Sun, 22/1/12, Ian Bates ian_and_joa...@talktalk.net wrote: From: Ian Bates ian_and_joa...@talktalk.net Subject: Re: [vdr] [ANNOUNCE] VDR developer version 1.7.23 To: VDR Mailing List vdr@linuxtv.org Date: Sunday, 22 January, 2012, 12:40 Hi, Something to try: *Short answer* Make sure VDR Make.config points to the appropriate media_build directory (DVBDIR variable) *Longer answer* I'm not sure a simple 'install' of the DVB drivers changes any system headers. So VDR needs to point the headers relevant to the available modules. 1. Ensure you really have built and installed the media_build DVB stack. 2. Point VDR Make.config to your git media_build directory NOTE '/linux' suffix: ... # From my vdr Make.config: #DVBDIR = /usr/local/src/v4l-dvb/current/linux #DVBDIR = /usr/local/src/linux-tbs-drivers/current/linux DVBDIR = /usr/local/src/linux-tbs-drivers/testing/linux # Change to where you have downloaded and built your DVB stuff DVBDIR = /usr/local/src/dvb/media_build-git/linux ... 3. make VDR and install If you have followed these steps already then I'm sorry not to add anything new. Regards, Ian. On 22 Jan 2012, at 11:03, Stuart Morris wrote: Hi I have updated my DVB drivers using: git clone git://linuxtv.org/media_build.git cd media_build ./build make install Yet VDR complains of the wrong DVB API version number: dvbdevice.h:18:2: error: #error VDR requires Linux DVB driver API version 5.3 or higher! /usr/include/linux/dvb/version.h reports version 5.2 and the date of the file is old, meaning it was not updated when the drivers were updated. Can anybody explain what has gone wrong here? Thanks --- On Sun, 15/1/12, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: From: Klaus Schmidinger klaus.schmidin...@tvdr.de Subject: [vdr] [ANNOUNCE] VDR developer version 1.7.23 To: vdr@linuxtv.org Date: Sunday, 15 January, 2012, 15:10 VDR developer version 1.7.23 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.23.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.22-1.7.23.diff MD5 checksums: de136f7be28c4b6f1fa0e2218b4acc11 vdr-1.7.23.tar.bz2 2977b75cd8dacad187d11c10b867d56a vdr-1.7.22-1.7.23.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.22: - Removed the '.pl' suffix from svdrpsend.pl (sorry, I missed that one). - Fixed bonding more than two devices. - Fixed handling symbolic links in cRecordings::ScanVideoDir() (reported by Sundararaj Reel). - Fixed a memory leak in cRecordings::ScanVideoDir() in case there are too many link levels (reported by Sundararaj Reel). - Removed redundant memset() in the ctor of cSatCableNumbers (triggered by Ville Skyttä pointing out that the argument sequence in the call was wrong). - Removed a redundant NULL check in cDvbSpuDecoder::setTime() (thanks to Ville Skyttä). - Added HasSnr to the DEBUG_SIGNALQUALITY output in cDvbTuner::GetSignalQuality() (triggered by Ville Skyttä pointing out that the variable HasSnr was unused). - Updated the Finnish OSD texts (thanks to Rolf Ahrenberg). - Added support for HbbTV to libsi (thanks to Christoph Haubrich). - Added support for devices with more than one delivery system per frontend. This requires a DVB driver with version 5.5 or higher that can handle the DTV_ENUM_DELSYS call. With older drivers it will fall back to one delivery system per frontend. - Updated the Hungarian language texts (thanks to István Füley). - cDvbTuner::ExecuteDiseqc() now makes sure only one tuner sends SCR commands at any given time (reported by Frank Neumann). - cEvent::FixEpgBugs() now replaces any newline characters in stream
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.23
Hi, I have updated my current build taken from the Media Build Tree last Tuesday with the contents of the linux media tarball dated 22/01/2012 and rebuilt my drivers. I still get the same results. As the system initialises the following lines appear in the syslog: Jan 23 12:16:44 Nutrigrain kernel: [9.338720] tuner-simple 16-0061: couldn't set type to 63. Using 78 (Philips FMD1216MEX MK3 Hybrid Tuner) instead Jan 23 12:16:44 Nutrigrain kernel: [9.346240] DVB: registering adapter 1 frontend 0 (Conexant CX24116/CX24118)... Jan 23 12:16:44 Nutrigrain kernel: [9.349110] DVB: registering adapter 1 frontend 1 (Conexant CX22702 DVB-T)... Subsequently when starting VDR the following is logged: Jan 23 13:10:13 Nutrigrain vdr: [2704] registered source parameters for 'A - ATSC' Jan 23 13:10:13 Nutrigrain vdr: [2704] registered source parameters for 'C - DVB-C' Jan 23 13:10:13 Nutrigrain vdr: [2704] registered source parameters for 'S - DVB-S' Jan 23 13:10:13 Nutrigrain vdr: [2704] registered source parameters for 'T - DVB-T' Jan 23 13:10:13 Nutrigrain vdr: [2704] probing /dev/dvb/adapter0/frontend0 Jan 23 13:10:13 Nutrigrain vdr: [2704] new device number 1 Jan 23 13:10:13 Nutrigrain vdr: [2704] frontend 0/0 provides DVB-S with QPSK (ST STV0299 DVB-S) Jan 23 13:10:13 Nutrigrain vdr: [2708] tuner on frontend 0/0 thread started (pid=2704, tid=2708) Jan 23 13:10:13 Nutrigrain vdr: [2709] section handler thread started (pid=2704, tid=2709) Jan 23 13:10:13 Nutrigrain vdr: [2704] probing /dev/dvb/adapter1/frontend0 Jan 23 13:10:13 Nutrigrain vdr: [2704] new device number 2 Jan 23 13:10:14 Nutrigrain vdr: [2706] video directory scanner thread ended (pid=2704, tid=2706) Jan 23 13:10:14 Nutrigrain vdr: [2705] video directory scanner thread ended (pid=2704, tid=2705) Jan 23 13:10:19 Nutrigrain vdr: [2704] frontend 1/0 provides DVB-S,DVB-S2 with QPSK (Conexant CX24116/CX24118) Jan 23 13:10:19 Nutrigrain vdr: [2712] tuner on frontend 1/0 thread started (pid=2704, tid=2712) Jan 23 13:10:19 Nutrigrain vdr: [2713] section handler thread started (pid=2704, tid=2713) Jan 23 13:10:24 Nutrigrain vdr: [2704] ERROR (dvbdevice.c,1087): /dev/dvb/adapter1/frontend1: Device or resource busy Jan 23 13:10:24 Nutrigrain vdr: [2704] found 2 DVB devices I'm sure that I have the latest drivers loaded now, but still the same issue. The only conclusion that I can come to is that the necessary changes to the drivers have not (yet) been made. Has anyone else tried VDR 1.7.23 with a HVR 4000 hybrid card and if so, do you get the same results? Thanks, Mark. -Original Message- From: vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] On Behalf Of Steffen Barszus Sent: Wednesday, 18 January 2012 5:47 PM To: vdr@linuxtv.org Subject: Re: [vdr] [ANNOUNCE] VDR developer version 1.7.23 On Wed, 18 Jan 2012 09:58:16 +1100 Hawes, Mark mark.ha...@au.fujitsu.com wrote: Hi, I have tried using my hybrid HVR 4000 card ( DVB-S2 and DVB-T frontends on one adapter ) against 1.7.23 and a new set of V4L-DVB drivers built on Monday. DVB-S channels work fine. However, any attempt to select a DVB-T channel results in channel not available. The Syslog trace during VDR initialisation follows: It looks like VDR is not picking up the second frontend on the hybrid card as a result of the 'Device or resource busy' result which is due to frontend 0 being open on it. If you are using new dvb driver you should only have 1 frontend which has all of the delivery systems. The DVBv3 message also looks suspicious. Can you double check that new drivers are loaded and you have indeed only 1 frontend for that card ? (Not saying that there is not a bug) Regards, -Original Message- From: vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] On Behalf Of Klaus Schmidinger Sent: Monday, 16 January 2012 2:11 AM To: vdr@linuxtv.org Subject: [vdr] [ANNOUNCE] VDR developer version 1.7.23 VDR developer version 1.7.23 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.23.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.22-1.7.23.diff MD5 checksums: de136f7be28c4b6f1fa0e2218b4acc11 vdr-1.7.23.tar.bz2 2977b75cd8dacad187d11c10b867d56a vdr-1.7.22-1.7.23.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.22: - Removed the '.pl' suffix from svdrpsend.pl (sorry, I missed that one). - Fixed bonding more than two devices. - Fixed handling symbolic links in cRecordings::ScanVideoDir() (reported by Sundararaj Reel). - Fixed a memory leak in cRecordings::ScanVideoDir() in case there are too many link levels (reported by Sundararaj Reel). - Removed redundant memset() in the ctor of cSatCableNumbers
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.23
Hi, The drivers I am using I downloaded from the media build tree using git clone git://linuxtv.org/media_build.git as suggested on the Linuxtv.org site. However, these appear to be 'old' drivers as I am still getting 2 frontend devices created for my card when I load them. Can anyone suggest how I can get the latest set of Manu Abraham's drivers which I believe may contain some later patches. Thanks, Mark. -Original Message- From: vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] On Behalf Of Steffen Barszus Sent: Wednesday, 18 January 2012 5:47 PM To: vdr@linuxtv.org Subject: Re: [vdr] [ANNOUNCE] VDR developer version 1.7.23 On Wed, 18 Jan 2012 09:58:16 +1100 Hawes, Mark mark.ha...@au.fujitsu.com wrote: Hi, I have tried using my hybrid HVR 4000 card ( DVB-S2 and DVB-T frontends on one adapter ) against 1.7.23 and a new set of V4L-DVB drivers built on Monday. DVB-S channels work fine. However, any attempt to select a DVB-T channel results in channel not available. The Syslog trace during VDR initialisation follows: It looks like VDR is not picking up the second frontend on the hybrid card as a result of the 'Device or resource busy' result which is due to frontend 0 being open on it. If you are using new dvb driver you should only have 1 frontend which has all of the delivery systems. The DVBv3 message also looks suspicious. Can you double check that new drivers are loaded and you have indeed only 1 frontend for that card ? (Not saying that there is not a bug) Regards, -Original Message- From: vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] On Behalf Of Klaus Schmidinger Sent: Monday, 16 January 2012 2:11 AM To: vdr@linuxtv.org Subject: [vdr] [ANNOUNCE] VDR developer version 1.7.23 VDR developer version 1.7.23 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.23.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.22-1.7.23.diff MD5 checksums: de136f7be28c4b6f1fa0e2218b4acc11 vdr-1.7.23.tar.bz2 2977b75cd8dacad187d11c10b867d56a vdr-1.7.22-1.7.23.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.22: - Removed the '.pl' suffix from svdrpsend.pl (sorry, I missed that one). - Fixed bonding more than two devices. - Fixed handling symbolic links in cRecordings::ScanVideoDir() (reported by Sundararaj Reel). - Fixed a memory leak in cRecordings::ScanVideoDir() in case there are too many link levels (reported by Sundararaj Reel). - Removed redundant memset() in the ctor of cSatCableNumbers (triggered by Ville Skyttä pointing out that the argument sequence in the call was wrong). - Removed a redundant NULL check in cDvbSpuDecoder::setTime() (thanks to Ville Skyttä). - Added HasSnr to the DEBUG_SIGNALQUALITY output in cDvbTuner::GetSignalQuality() (triggered by Ville Skyttä pointing out that the variable HasSnr was unused). - Updated the Finnish OSD texts (thanks to Rolf Ahrenberg). - Added support for HbbTV to libsi (thanks to Christoph Haubrich). - Added support for devices with more than one delivery system per frontend. This requires a DVB driver with version 5.5 or higher that can handle the DTV_ENUM_DELSYS call. With older drivers it will fall back to one delivery system per frontend. - Updated the Hungarian language texts (thanks to István Füley). - cDvbTuner::ExecuteDiseqc() now makes sure only one tuner sends SCR commands at any given time (reported by Frank Neumann). - cEvent::FixEpgBugs() now replaces any newline characters in stream component descriptions with blanks (thanks to Torsten Lang for reporting a problem with EPG data from BSkyB's MTV MUSIC, S28.2E-2-2010-7012). - Fixed cDvbSubtitleConverter::SetOsdData() (thanks to Rolf Ahrenberg). - Fixed cListBase::Move() in case From and To are equal (reported by Sundararaj Reel). - Added support for DVB-T2 to libsi (thanks to Rolf Ahrenberg). - Added support for handling DVB-T2 transponders. This requires a DVB driver with version 5.3 or higher that can handle the DTV_DVBT2_PLP_ID call (thanks to Rolf Ahrenberg). - Fixed cConfig::Load() for g++ version 4.7.0 (thanks to Ville Skyttä). - Fixed a possible memory corruption in cTsToPes::GetPes() in case of broken TS packets, e.g. when switching channels. - Fixed the SVDRP command CLRE for a single channel in case there are events that have a timer (thanks to Timo Eskola). - BIDI support now checks at runtime whether the system runs with UTF-8 (suggested by Torsten Lang). - Added member functions Adapter() and Frontend() to cDvbDevice (suggested by Rolf Ahrenberg). - The parameters that are only used by second generation delivery systems (DVB-S2 and DVB-T2
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.23
Hi, I have tried using my hybrid HVR 4000 card ( DVB-S2 and DVB-T frontends on one adapter ) against 1.7.23 and a new set of V4L-DVB drivers built on Monday. DVB-S channels work fine. However, any attempt to select a DVB-T channel results in channel not available. The Syslog trace during VDR initialisation follows: Jan 17 18:44:05 Nutrigrain vdr: [2587] video directory scanner thread started (pid=2586, tid=2587) Jan 17 18:44:05 Nutrigrain vdr: [2588] video directory scanner thread started (pid=2586, tid=2588) Jan 17 18:44:05 Nutrigrain vdr: [2586] reading EPG data from /home/digitalTV/video/epg.data Jan 17 18:44:05 Nutrigrain vdr: [2586] registered source parameters for 'A - ATSC' Jan 17 18:44:05 Nutrigrain vdr: [2586] registered source parameters for 'C - DVB-C' Jan 17 18:44:05 Nutrigrain vdr: [2586] registered source parameters for 'S - DVB-S' Jan 17 18:44:05 Nutrigrain vdr: [2586] registered source parameters for 'T - DVB-T' Jan 17 18:44:05 Nutrigrain vdr: [2586] probing /dev/dvb/adapter0/frontend0 Jan 17 18:44:05 Nutrigrain vdr: [2586] new device number 1 Jan 17 18:44:05 Nutrigrain kernel: [ 150.671847] dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 0 Jan 17 18:44:05 Nutrigrain vdr: [2586] frontend 0/0 provides DVB-S with QPSK (ST STV0299 DVB-S) Jan 17 18:44:05 Nutrigrain vdr: [2591] section handler thread started (pid=2586, tid=2591) Jan 17 18:44:05 Nutrigrain vdr: [2590] tuner on frontend 0/0 thread started (pid=2586, tid=2590) Jan 17 18:44:05 Nutrigrain vdr: [2586] probing /dev/dvb/adapter1/frontend0 Jan 17 18:44:05 Nutrigrain vdr: [2586] new device number 2 Jan 17 18:44:06 Nutrigrain vdr: [2588] video directory scanner thread ended (pid=2586, tid=2588) Jan 17 18:44:06 Nutrigrain vdr: [2587] video directory scanner thread ended (pid=2586, tid=2587) Jan 17 18:44:10 Nutrigrain kernel: [ 155.838763] dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 0 Jan 17 18:44:10 Nutrigrain vdr: [2586] frontend 1/0 provides DVB-S,DVB-S2 with QPSK (Conexant CX24116/CX24118) Jan 17 18:44:10 Nutrigrain vdr: [2594] tuner on frontend 1/0 thread started (pid=2586, tid=2594) Jan 17 18:44:10 Nutrigrain vdr: [2595] section handler thread started (pid=2586, tid=2595) Jan 17 18:44:15 Nutrigrain vdr: [2586] ERROR (dvbdevice.c,1051): /dev/dvb/adapter1/frontend1: Device or resource busy Jan 17 18:44:15 Nutrigrain vdr: [2586] found 2 DVB devices Note that there is also a DVB-S premium card in the mix which works OK. It looks like VDR is not picking up the second frontend on the hybrid card as a result of the 'Device or resource busy' result which is due to frontend 0 being open on it. Any suggestions: Regards, -Original Message- From: vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] On Behalf Of Klaus Schmidinger Sent: Monday, 16 January 2012 2:11 AM To: vdr@linuxtv.org Subject: [vdr] [ANNOUNCE] VDR developer version 1.7.23 VDR developer version 1.7.23 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.23.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.22-1.7.23.diff MD5 checksums: de136f7be28c4b6f1fa0e2218b4acc11 vdr-1.7.23.tar.bz2 2977b75cd8dacad187d11c10b867d56a vdr-1.7.22-1.7.23.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.22: - Removed the '.pl' suffix from svdrpsend.pl (sorry, I missed that one). - Fixed bonding more than two devices. - Fixed handling symbolic links in cRecordings::ScanVideoDir() (reported by Sundararaj Reel). - Fixed a memory leak in cRecordings::ScanVideoDir() in case there are too many link levels (reported by Sundararaj Reel). - Removed redundant memset() in the ctor of cSatCableNumbers (triggered by Ville Skyttä pointing out that the argument sequence in the call was wrong). - Removed a redundant NULL check in cDvbSpuDecoder::setTime() (thanks to Ville Skyttä). - Added HasSnr to the DEBUG_SIGNALQUALITY output in cDvbTuner::GetSignalQuality() (triggered by Ville Skyttä pointing out that the variable HasSnr was unused). - Updated the Finnish OSD texts (thanks to Rolf Ahrenberg). - Added support for HbbTV to libsi (thanks to Christoph Haubrich). - Added support for devices with more than one delivery system per frontend. This requires a DVB driver with version 5.5 or higher that can handle the DTV_ENUM_DELSYS call. With older drivers it will fall back to one delivery system per frontend. - Updated the Hungarian language texts (thanks to István Füley). - cDvbTuner::ExecuteDiseqc() now makes sure only one tuner sends SCR commands at any given time (reported by Frank Neumann). - cEvent::FixEpgBugs() now replaces any newline characters in stream component descriptions with
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.23
On Wed, 18 Jan 2012 09:58:16 +1100 Hawes, Mark mark.ha...@au.fujitsu.com wrote: Hi, I have tried using my hybrid HVR 4000 card ( DVB-S2 and DVB-T frontends on one adapter ) against 1.7.23 and a new set of V4L-DVB drivers built on Monday. DVB-S channels work fine. However, any attempt to select a DVB-T channel results in channel not available. The Syslog trace during VDR initialisation follows: It looks like VDR is not picking up the second frontend on the hybrid card as a result of the 'Device or resource busy' result which is due to frontend 0 being open on it. If you are using new dvb driver you should only have 1 frontend which has all of the delivery systems. The DVBv3 message also looks suspicious. Can you double check that new drivers are loaded and you have indeed only 1 frontend for that card ? (Not saying that there is not a bug) Regards, -Original Message- From: vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] On Behalf Of Klaus Schmidinger Sent: Monday, 16 January 2012 2:11 AM To: vdr@linuxtv.org Subject: [vdr] [ANNOUNCE] VDR developer version 1.7.23 VDR developer version 1.7.23 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.23.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.22-1.7.23.diff MD5 checksums: de136f7be28c4b6f1fa0e2218b4acc11 vdr-1.7.23.tar.bz2 2977b75cd8dacad187d11c10b867d56a vdr-1.7.22-1.7.23.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.22: - Removed the '.pl' suffix from svdrpsend.pl (sorry, I missed that one). - Fixed bonding more than two devices. - Fixed handling symbolic links in cRecordings::ScanVideoDir() (reported by Sundararaj Reel). - Fixed a memory leak in cRecordings::ScanVideoDir() in case there are too many link levels (reported by Sundararaj Reel). - Removed redundant memset() in the ctor of cSatCableNumbers (triggered by Ville Skyttä pointing out that the argument sequence in the call was wrong). - Removed a redundant NULL check in cDvbSpuDecoder::setTime() (thanks to Ville Skyttä). - Added HasSnr to the DEBUG_SIGNALQUALITY output in cDvbTuner::GetSignalQuality() (triggered by Ville Skyttä pointing out that the variable HasSnr was unused). - Updated the Finnish OSD texts (thanks to Rolf Ahrenberg). - Added support for HbbTV to libsi (thanks to Christoph Haubrich). - Added support for devices with more than one delivery system per frontend. This requires a DVB driver with version 5.5 or higher that can handle the DTV_ENUM_DELSYS call. With older drivers it will fall back to one delivery system per frontend. - Updated the Hungarian language texts (thanks to István Füley). - cDvbTuner::ExecuteDiseqc() now makes sure only one tuner sends SCR commands at any given time (reported by Frank Neumann). - cEvent::FixEpgBugs() now replaces any newline characters in stream component descriptions with blanks (thanks to Torsten Lang for reporting a problem with EPG data from BSkyB's MTV MUSIC, S28.2E-2-2010-7012). - Fixed cDvbSubtitleConverter::SetOsdData() (thanks to Rolf Ahrenberg). - Fixed cListBase::Move() in case From and To are equal (reported by Sundararaj Reel). - Added support for DVB-T2 to libsi (thanks to Rolf Ahrenberg). - Added support for handling DVB-T2 transponders. This requires a DVB driver with version 5.3 or higher that can handle the DTV_DVBT2_PLP_ID call (thanks to Rolf Ahrenberg). - Fixed cConfig::Load() for g++ version 4.7.0 (thanks to Ville Skyttä). - Fixed a possible memory corruption in cTsToPes::GetPes() in case of broken TS packets, e.g. when switching channels. - Fixed the SVDRP command CLRE for a single channel in case there are events that have a timer (thanks to Timo Eskola). - BIDI support now checks at runtime whether the system runs with UTF-8 (suggested by Torsten Lang). - Added member functions Adapter() and Frontend() to cDvbDevice (suggested by Rolf Ahrenberg). - The parameters that are only used by second generation delivery systems (DVB-S2 and DVB-T2) are no longer written into channels.conf for first generation delivery systems (DVB-S and DVB-T). - Changed IndexToHMSF() so that it can handle negative Index values. - Added option -N to the msgmerge call in the Makefile, because fuzzy translation mostly resulted in useless strings. - The new setup option Replay/Show remaining time can be used to switch between showing the total length or the remaining time of the recording that is currently replayed. - Fixed wrongfully displaying the length of a recording in the title of the replay progress display. - Fixed frozen live view with device bonding in case the bonded master is used for live viewing (reported by Uwe Scheffler). Have
