[vdr] VDR 1.7.0 S2API - Channels not Available
Hello vdr list I recently bought two Twinhan DVB-T receiver sticks: TwinhanDTV USB-Ter USB1.1 / Magic Box I Magic Box II They both seem to work well in linux, but for some reason I can only get a picture in stable c't vdr (1.6.0-2) and not in my self compiled vdr 1.7.0. I use s2-liplianin drivers with another Twinhan DVB-S2 card (1041), this one works fine on both vdr versions. Patchlevel on vdr 1.7.0 is: + h264-syncearly-framespersec-audioindexer-fielddetection-speedup +vdr-1.7.0-s2api-07102008-h264-clean.patch From what I see in the 1.7.0 syslog I can make out a possible reason why it doesn't work in there: vdr: [6675] [general.debug] capturing device 0 vdr: [6678] video directory scanner thread ended (pid=6675, tid=6678) vdr: [6677] video directory scanner thread ended (pid=6675, tid=6677) vdr: [6675] device 1 provides: DVBS DSS vdr: [6680] tuner on device 1 thread started (pid=6675, tid=6680) vdr: [6681] section handler thread started (pid=6675, tid=6681) vdr: [6675] [general.info] captured 1 video device This DVB-T stick is clearly *NOT* DVB-S capable - so this might be part of the problem. I don't get this message in 1.6.0 at all. Is this related to the problem Morfsta had in [1] ? - it is the same QAM 16 modulation I am trying to connect to - but mine is (QAM 16, 8K, 5/6, 1/4). Thanks in advance for any help. I'd like to stay with vdr 1.7.0 as well for plugin compatibility reasons. [1] http://www.linuxtv.org/pipermail/vdr/2009-February/019493.html _ http://redirect.gimas.net/?n=M0903xWLM2009 Neu: Messenger 2009! Hier kostenlos downloaden! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR 1.7.0 S2API - Channels not Available
Hello vdr list I recently bought two Twinhan DVB-T receiver sticks: TwinhanDTV USB-Ter USB1.1 / Magic Box I Magic Box II They both seem to work well in linux, but for some reason I can only get a picture in stable c't vdr (1.6.0-2) and not in my self compiled vdr 1.7.0. I use s2-liplianin drivers with another Twinhan DVB-S2 card (1041), this one works fine on both vdr versions. Patchlevel on vdr 1.7.0 is: + h264-syncearly-framespersec-audioindexer-fielddetection-speedup +vdr-1.7.0-s2api-07102008-h264-clean.patch From what I see in the 1.7.0 syslog I can make out a possible reason why it doesn't work in there: vdr: [6675] [general.debug] capturing device 0 vdr: [6678] video directory scanner thread ended (pid=6675, tid=6678) vdr: [6677] video directory scanner thread ended (pid=6675, tid=6677) vdr: [6675] device 1 provides: DVBS DSS vdr: [6680] tuner on device 1 thread started (pid=6675, tid=6680) vdr: [6681] section handler thread started (pid=6675, tid=6681) vdr: [6675] [general.info] captured 1 video device This DVB-T stick is clearly *NOT* DVB-S capable - so this might be part of the problem. I don't get this message in 1.6.0 at all. Is this related to the problem Morfsta had in [1] ? - it is the same QAM 16 modulation I am trying to connect to - but mine is (QAM 16, 8K, 5/6, 1/4). Thanks in advance for any help. I'd like to stay with vdr 1.7.0 as well for plugin compatibility reasons. [1] http://www.linuxtv.org/pipermail/vdr/2009-February/019493.html _ http://redirect.gimas.net/?n=M0903xIMTicTacToe Kostenlose Spannung? Spiel jetzt mit Freunden TIC TAC TOE in 3D! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
For vdr-1.7.0+ You must change your channels.conf to reflect below: :12326:HM2O0S0:S110.0W :12457:VM2O0S0:S119.0W 8psk :12457:VC23M5O0S0:S110.0W: - Original Message - From: LinuX Oholic tuxoho...@hotmail.de To: vdr@linuxtv.org Sent: Wednesday, March 25, 2009 5:22 AM Subject: [vdr] VDR 1.7.0 S2API - Channels not Available Hello vdr list I recently bought two Twinhan DVB-T receiver sticks: TwinhanDTV USB-Ter USB1.1 / Magic Box I Magic Box II They both seem to work well in linux, but for some reason I can only get a picture in stable c't vdr (1.6.0-2) and not in my self compiled vdr 1.7.0. I use s2-liplianin drivers with another Twinhan DVB-S2 card (1041), this one works fine on both vdr versions. Patchlevel on vdr 1.7.0 is: + h264-syncearly-framespersec-audioindexer-fielddetection-speedup +vdr-1.7.0-s2api-07102008-h264-clean.patch From what I see in the 1.7.0 syslog I can make out a possible reason why it doesn't work in there: vdr: [6675] [general.debug] capturing device 0 vdr: [6678] video directory scanner thread ended (pid=6675, tid=6678) vdr: [6677] video directory scanner thread ended (pid=6675, tid=6677) vdr: [6675] device 1 provides: DVBS DSS vdr: [6680] tuner on device 1 thread started (pid=6675, tid=6680) vdr: [6681] section handler thread started (pid=6675, tid=6681) vdr: [6675] [general.info] captured 1 video device This DVB-T stick is clearly *NOT* DVB-S capable - so this might be part of the problem. I don't get this message in 1.6.0 at all. Is this related to the problem Morfsta had in [1] ? - it is the same QAM 16 modulation I am trying to connect to - but mine is (QAM 16, 8K, 5/6, 1/4). Thanks in advance for any help. I'd like to stay with vdr 1.7.0 as well for plugin compatibility reasons. [1] http://www.linuxtv.org/pipermail/vdr/2009-February/019493.html _ http://redirect.gimas.net/?n=M0903xIMTicTacToe Kostenlose Spannung? Spiel jetzt mit Freunden TIC TAC TOE in 3D! ___ 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] VDR 1.7.0 S2API - Channels not Available
Can you try with vdr-1.7.4, that's the first version from vdr 1.7x series that i got working with s2api and hvr-4000. I have testeed it with streamdev server plugin and mplayervlc. vdr-1.7.4 works fine with all my devices - but vomp isn't compatible with it yet for replaying its recordings and also the rotor plugin (which I use to move the dish and scan transponders) also won't compile at the moment (I didn't search for any updates, anyone know if it has been re-written for S2API or even if it is still being maintained?) so I will stick with 1.7.0 multiproto for now and wait for 1.7.4 / S2API to mature and become more widely supported with plugins etc. vdr-1.7.0 and the S2API patch doesn't work with DVB-T at all here, so I guess there's a bug in the patch there somewhere that affects reception of UK transmitters (perhaps handling of QAM 16 modulation?) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR 1.7.0 S2API - Channels not Available
Hi, Due to an attempt on OS upgrade and thus kernel upgrade I'm grudgingly (it worked for me for months with no issues so why would I want to change it for now?) trying to make the transition from multiproto to S2API. I have two DVB-T cards and a NOVA-S2-HD (HVR4000 lite). I have downloaded a vanilla vdr-1.7.0 applied the h264 patch and the s2api patch and install S2API from Steven Toth's mercurial repository. On booting the kernel loads all the modules and I see the various frontends and when I start VDR it loads all of the relevant firmware okay. When I start VDR it won't show any of the FTA channels on DVB-T or DVB-S (not even tried S2!) and all I get is Channel Not Available. I wish VDR were more descriptive in why the channels are not available! :-) Apologies if this has been asked before, but is there anything I'm missing? Is the problem that I took my channels.conf from my multiproto VDR and something has now changed in the format? It would be good to get this working as my old OS is now messy and really needs a clean build with a shiny new kernel and I can't patch up to date multiproto with the old HVR4000 patches (a few FAILS which I guess I could fix, but might take some time as they don't look that trivial) and an older version of multiproto from HG doesn't compile on the new kernel! Can anyone point me in the right direction on what might be going on? Thanks ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
On Wed, Feb 4, 2009 at 10:58 AM, Klaus Schmidinger klaus.schmidin...@cadsoft.de wrote: Well, even using *any* version 1.7.x in a productive environment is a risk ;-) [SNIP] S2API was necessary for HDTV channels, and recording HDTV channels only makes sense in TS. The PES recording of HDTV broadcasts was never officially supported by VDR. The other problem is that I don't think anyone has got VDR 1.7.4 working with the eHD yet, which is my output device... :-( So it seems everywhere I look at the moment I am stuck. :-( Should VDR-1.7.0 be reporting my DVB-T frontends as DVBT when it starts up? Is there perhaps a capability flag in the driver that has not been setup for the devices that I am using? I compared the channel settings of BBC ONE in VDR with multiproto version and s2api version that I am running and they are exactly the same. @Niels, which DVB-T devices are you using successfully with VDR-1.7.0 so that I can compare them with my own drivers? It seems strange though that scan-s2 successfully finds all the channels but VDR won't play them. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
Op Wo, 4 februari, 2009 13:38, schreef Ales Jurik: -- SNIP -- Hi, Hello! I have it working with some dirty hacks (reelvdr svn 10388 - the latest with hdplayer). But for the problem with sending AC3 sound to ac3dec (with -a ac3dec) I didn't have enough time to solve. With sound over HDMI it could be used. Would you be filling to upload the patch to the ML or send it to me directly? I use sound over HDMI anyway since I redirect the sound from my Plasma to my receiver. Ales Regards, Niels Wagenaar ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
On Wednesday 04 of February 2009, Morfsta wrote:
On Wed, Feb 4, 2009 at 10:58 AM, Klaus Schmidinger
klaus.schmidin...@cadsoft.de wrote:
Well, even using *any* version 1.7.x in a productive environment
is a risk ;-)
[SNIP]
S2API was necessary for HDTV channels, and recording HDTV channels
only makes sense in TS. The PES recording of HDTV broadcasts was never
officially supported by VDR.
The other problem is that I don't think anyone has got VDR 1.7.4
working with the eHD yet, which is my output device... :-( So it seems
everywhere I look at the moment I am stuck. :-(
Here are patches for eHD and vdr-1.7.4. I've tested it only for a little time
as I didn't have enough time (now I revert back to vdr-1.7.0 with
multiproto).
Included are two patches - first is for reelbox plugin. In file
ReelBoxDevice.c patch solves the audio problem (vdr is sending audio with
zero trackid and reelbox plugin cancel such streams). In setupmenu.c is
solved the problem with saving config and in VideoPlayerPipHd.c the include
solves for me compile problem in amd64 linux.
In the patch for vdr in part of device.c is patch from Klaus for subtitles and
rest is very quick and dirty patch for osd to compile with reelbox plugin. It
mostly revert the vdr osd to 1.7.0 version of files, but it seems to be
working at minimum with default STTNG skin, other skins are not tested.
Enjoy,
BR,
Ales
diff -ru vdr-1.7.4.orig/config.h vdr-1.7.4/config.h
--- vdr-1.7.4.orig/config.h 2009-01-06 17:56:27.0 +0100
+++ vdr-1.7.4/config.h 2009-02-01 20:47:21.611262480 +0100
@@ -192,11 +192,11 @@
void StoreLanguages(const char *Name, int *Values);
bool ParseLanguages(const char *Value, int *Values);
bool Parse(const char *Name, const char *Value);
- cSetupLine *Get(const char *Name, const char *Plugin = NULL);
void Store(const char *Name, const char *Value, const char *Plugin = NULL, bool AllowMultiple = false);
void Store(const char *Name, int Value, const char *Plugin = NULL);
public:
// Also adjust cMenuSetup (menu.c) when adding parameters here!
+ cSetupLine *Get(const char *Name, const char *Plugin = NULL);
int __BeginData__;
char OSDLanguage[I18N_MAX_LOCALE_LEN];
char OSDSkin[MaxSkinName];
diff -ru vdr-1.7.4.orig/device.c vdr-1.7.4/device.c
--- vdr-1.7.4.orig/device.c 2009-01-25 12:10:56.0 +0100
+++ vdr-1.7.4/device.c 2009-02-01 20:35:04.203264160 +0100
@@ -1304,8 +1304,9 @@
if (!dvbSubtitleConverter)
dvbSubtitleConverter = new cDvbSubtitleConverter;
tsToPesSubtitle.PutTs(Data, Length);
- if (const uchar *p = tsToPesSubtitle.GetPes(Length)) {
- dvbSubtitleConverter-Convert(p, Length);
+ int l;
+ if (const uchar *p = tsToPesSubtitle.GetPes(l)) {
+ dvbSubtitleConverter-Convert(p, l);
tsToPesSubtitle.Reset();
}
return Length;
diff -ru vdr-1.7.4.orig/font.h vdr-1.7.4/font.h
--- vdr-1.7.4.orig/font.h 2007-06-23 12:09:14.0 +0200
+++ vdr-1.7.4/font.h 2009-02-01 20:47:21.611262480 +0100
@@ -36,6 +36,12 @@
private:
static cFont *fonts[];
public:
+ enum { NUMCHARS = 256 };
+ typedef uint32_t tPixelData;
+ struct tCharData {
+ tPixelData width, height;
+ tPixelData lines[1];
+ };
virtual ~cFont() {}
virtual int Width(uint c) const = 0;
/// Returns the width of the given character in pixel.
diff -ru vdr-1.7.4.orig/osdbase.h vdr-1.7.4/osdbase.h
--- vdr-1.7.4.orig/osdbase.h 2007-11-03 15:50:52.0 +0100
+++ vdr-1.7.4/osdbase.h 2009-02-01 20:47:21.611262480 +0100
@@ -84,9 +84,7 @@
class cOsdMenu : public cOsdObject, public cListcOsdItem {
private:
- static cSkinDisplayMenu *displayMenu;
static int displayMenuCount;
- static int displayMenuItems;
char *title;
int cols[cSkinDisplayMenu::MaxTabs];
int first, current, marked;
@@ -97,6 +95,7 @@
bool hasHotkeys;
protected:
void SetDisplayMenu(void);
+ static int displayMenuItems;
cSkinDisplayMenu *DisplayMenu(void) { return displayMenu; }
const char *hk(const char *s);
void SetCols(int c0, int c1 = 0, int c2 = 0, int c3 = 0, int c4 = 0);
@@ -123,6 +122,7 @@
public:
cOsdMenu(const char *Title, int c0 = 0, int c1 = 0, int c2 = 0, int c3 = 0, int c4 = 0);
virtual ~cOsdMenu();
+ static cSkinDisplayMenu *displayMenu;
virtual bool NeedsFastResponse(void) { return subMenu ? subMenu-NeedsFastResponse() : cOsdObject::NeedsFastResponse(); }
int Current(void) const { return current; }
void Add(cOsdItem *Item, bool Current = false, cOsdItem *After = NULL);
diff -ru vdr-1.7.4.orig/osd.c vdr-1.7.4/osd.c
--- vdr-1.7.4.orig/osd.c 2009-01-16 15:34:32.0 +0100
+++ vdr-1.7.4/osd.c 2009-02-01 20:47:21.611262480 +0100
@@ -379,13 +379,14 @@
if (strncmp(Xpm[i + 1], s, c) == 0) {
if (i == NoneColorIndex)
NoneColorIndex = MAXNUMCOLORS;
- SetIndex(x, y, (IgnoreNone i NoneColorIndex) ? i - 1 : i);
+ SetIndexFast(x, y, (IgnoreNone i
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
On Wednesday 04 of February 2009, Morfsta wrote: On Wed, Feb 4, 2009 at 10:58 AM, Klaus Schmidinger klaus.schmidin...@cadsoft.de wrote: Well, even using *any* version 1.7.x in a productive environment is a risk ;-) [SNIP] S2API was necessary for HDTV channels, and recording HDTV channels only makes sense in TS. The PES recording of HDTV broadcasts was never officially supported by VDR. The other problem is that I don't think anyone has got VDR 1.7.4 working with the eHD yet, which is my output device... :-( So it seems everywhere I look at the moment I am stuck. :-( Hi, I have it working with some dirty hacks (reelvdr svn 10388 - the latest with hdplayer). But for the problem with sending AC3 sound to ac3dec (with -a ac3dec) I didn't have enough time to solve. With sound over HDMI it could be used. Ales Should VDR-1.7.0 be reporting my DVB-T frontends as DVBT when it starts up? Is there perhaps a capability flag in the driver that has not been setup for the devices that I am using? I compared the channel settings of BBC ONE in VDR with multiproto version and s2api version that I am running and they are exactly the same. @Niels, which DVB-T devices are you using successfully with VDR-1.7.0 so that I can compare them with my own drivers? It seems strange though that scan-s2 successfully finds all the channels but VDR won't play them. ___ 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] VDR 1.7.0 S2API - Channels not Available
Op Wo, 4 februari, 2009 13:22, schreef Morfsta: -- SNIP -- The other problem is that I don't think anyone has got VDR 1.7.4 working with the eHD yet, which is my output device... :-( So it seems everywhere I look at the moment I am stuck. :-( This is indeed correct. The eHD (which I have in use also) seems to be very stable in 1.7.0. The versions 1.7.3 and 1.7.4 didn't give me any audio. Hopefully this will be fixed soon. Because this is the only thing keeping me from using VDR 1.7.4 :) Should VDR-1.7.0 be reporting my DVB-T frontends as DVBT when it starts up? Is there perhaps a capability flag in the driver that has not been setup for the devices that I am using? I compared the channel settings of BBC ONE in VDR with multiproto version and s2api version that I am running and they are exactly the same. I have that too, nothing to get worried about it. The DVB-T device gives out wrong supported transports (like DVBS) but the code/patch will only lock DVB-T transports with DVB-T devices. At least, during my testing ;) @Niels, which DVB-T devices are you using successfully with VDR-1.7.0 so that I can compare them with my own drivers? It seems strange though that scan-s2 successfully finds all the channels but VDR won't play them. I still think it's a problem with the channel.conf. For fun, please try using the old and default scan for DVB-T. Because I used the old dvb-scan with the option to output for VDR on my Gigabyte GT-U7000-RH based DVB-T adapter to scan for KPN Digitenne bouquets (location Zwolle/Apeldoorn). Regards, Niels Wagenaar ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
The Multiproto channels.conf should be interchangeable with S2API. But *some* modulation types didn't exist in S2API when I wrote the patches and you need to check this for yourself. You need to check the settings (Red button to edit in the TV Channels overview) and see if they are indeed correct and change them accordinly. My best guess, is that the modulation types are wrong. Sorry to double post but as an update I removed all DVB-T channels and then rescanned them using scan-s2 from http://mercurial.intuxication.org/hg/scan-s2/. It found all the channels on my transmitter. Also DVB-S channels seem to be working fine, not tried S2 yet. The new format for DVB-T presented is: - BBC ONE;BBC:73:I999B8C34D34M16T2G32Y0:T:27500:600:601=eng,602=eng:0:0:4165:9018:4101:0 which is now accepted by VDR. However, I get a black screen when tuning to them. In user.log I see: - Feb 4 10:38:08 morfsta vdr: [18340] probing /dev/dvb/adapter0/frontend0 Feb 4 10:38:08 morfsta vdr: [18340] device 1 provides: DVBS DSS Feb 4 10:38:08 morfsta vdr: [18344] tuner on device 1 thread started (pid=18340, tid=18344) Feb 4 10:38:08 morfsta vdr: [18345] section handler thread started (pid=18340, tid=18345) Feb 4 10:38:08 morfsta vdr: [18340] probing /dev/dvb/adapter1/frontend0 Feb 4 10:38:08 morfsta vdr: [18340] device 2 provides: DVBS DSS Feb 4 10:38:08 morfsta vdr: [18347] tuner on device 2 thread started (pid=18340, tid=18347) Feb 4 10:38:08 morfsta vdr: [18348] section handler thread started (pid=18340, tid=18348) Feb 4 10:38:08 morfsta vdr: [18340] probing /dev/dvb/adapter2/frontend0 Feb 4 10:38:08 morfsta vdr: [18340] device 3 provides: DVBS DVBS2 Feb 4 10:38:08 morfsta vdr: [18340] device 3 forced to frontendType SYS_DVBS2 Feb 4 10:38:08 morfsta vdr: [18350] tuner on device 3 thread started (pid=18340, tid=18350) Feb 4 10:38:09 morfsta vdr: [18351] section handler thread started (pid=18340, tid=18351) which is funny because devices 0 and 1 are DVB-T: [ 12.497993] DVB: registering adapter 0 frontend -858993460 (Philips TDA10045H DVB-T)... [ 12.554597] DVB: registering adapter 1 frontend -858993460 (Conexant CX22702 DVB-T)... [ 12.594872] DVB: registering adapter 2 frontend 0 (Conexant CX24116/CX24118)... then when VDR starts tuning I see: Feb 4 10:38:18 morfsta vdr: [18344] frontend 0 timed out while tuning to channel 1, tp 642 Feb 4 10:39:18 morfsta vdr: [18347] frontend 1 timed out while tuning to channel 1, tp 642 Feb 4 10:39:21 morfsta vdr: [18344] frontend 0 timed out while tuning to channel 1, tp 642 Any suggestions? Thanks ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
Op Wo, 4 februari, 2009 10:16, schreef Morfsta: Hi, Goodmorning! Due to an attempt on OS upgrade and thus kernel upgrade I'm grudgingly (it worked for me for months with no issues so why would I want to change it for now?) trying to make the transition from multiproto to S2API. I have two DVB-T cards and a NOVA-S2-HD (HVR4000 lite). I have downloaded a vanilla vdr-1.7.0 applied the h264 patch and the s2api patch and install S2API from Steven Toth's mercurial repository. You might want to try Igor's repo http://mercurial.intuxication.org/hg/s2-liplianin) since Steve's hasn't been updated for over 3 months. This however won't fix your problem perse. On booting the kernel loads all the modules and I see the various frontends and when I start VDR it loads all of the relevant firmware okay. When I start VDR it won't show any of the FTA channels on DVB-T or DVB-S (not even tried S2!) and all I get is Channel Not Available. I wish VDR were more descriptive in why the channels are not available! :-) Did you install mine S2API patch from 7-10 for VDR 1.7.0? Because this is the latest version and this has been tested with DVB-T, DVB-S, DVB-S2 and DVB-C. And with succes! ;) BTW, you might want to increase the logging for VDR or check the logfiles in /var/log what VDR has thrown out (Ubuntu uses /var/log/user.log for instance). My best guess is an frontend timeout error. This means that a timeout (duh!) occured when tuning to the selected channel. This can mean a reception problem (not likely, but good to point out) or a problem in your channels.conf. Apologies if this has been asked before, but is there anything I'm missing? Is the problem that I took my channels.conf from my multiproto VDR and something has now changed in the format? The Multiproto channels.conf should be interchangeable with S2API. But *some* modulation types didn't exist in S2API when I wrote the patches and you need to check this for yourself. You need to check the settings (Red button to edit in the TV Channels overview) and see if they are indeed correct and change them accordinly. My best guess, is that the modulation types are wrong. It would be good to get this working as my old OS is now messy and really needs a clean build with a shiny new kernel and I can't patch up to date multiproto with the old HVR4000 patches (a few FAILS which I guess I could fix, but might take some time as they don't look that trivial) and an older version of multiproto from HG doesn't compile on the new kernel! Best to say, multiproto is not needed to get it al working. I've got the same kind of config as you ( NOVA-HD-S2 and a Gigabyte USB stick for DVB-T) and it works very good with S2API. Can anyone point me in the right direction on what might be going on? See the above ;) Thanks Regards, Niels Wagenaar ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
On Wed, Feb 4, 2009 at 9:39 AM, Niels Wagenaar n.wagen...@xs4all.nl wrote: Goodmorning! Morning Niels, thanks for getting back to me so quickly! You might want to try Igor's repo http://mercurial.intuxication.org/hg/s2-liplianin) since Steve's hasn't been updated for over 3 months. This however won't fix your problem perse. OK, done that. Did you install mine S2API patch from 7-10 for VDR 1.7.0? Because this is the latest version and this has been tested with DVB-T, DVB-S, DVB-S2 and DVB-C. And with succes! ;) Specifically I have installed: vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff vdr-1.7.0-s2api-07102008-h264-clean.patch the only other plugin I am using at this stage is the reelbox plugin output which seems to work fine. BTW, you might want to increase the logging for VDR or check the logfiles in /var/log what VDR has thrown out (Ubuntu uses /var/log/user.log for instance). My best guess is an frontend timeout error. This means that a timeout (duh!) occured when tuning to the selected channel. This can mean a reception problem (not likely, but good to point out) or a problem in your channels.conf. Now I have recompiled it all and when I run VDR I get: - vdr: error while reading '/video/config6/channels.conf' in /var/log/user.log I see: - Feb 4 10:06:01 morfsta vdr: [17791] loading /video/config6/channels.conf Feb 4 10:06:01 morfsta vdr: [17791] ERROR: unknown parameter key 'A' Feb 4 10:06:01 morfsta vdr: [17791] ERROR: error in /video/config6/channels.conf, line 2 Line 2 is a DVB-T channel: - BBC ONE;BBC:73000:A0B8C34D34G32I0M16P0T2Y0:T:27500:600:601=eng,602=eng:0:0:4 165:9018:4101:0 This channel works fine in vdr-1.7.0 with multiproto and there are definitely no reception problems as all DVB-T and DVB-S channels works fine with previous implementation (which I have kept in a seperate parition obviously!). The Multiproto channels.conf should be interchangeable with S2API. But *some* modulation types didn't exist in S2API when I wrote the patches and you need to check this for yourself. You need to check the settings (Red button to edit in the TV Channels overview) and see if they are indeed correct and change them accordinly. My best guess, is that the modulation types are wrong. It seems that the channels.conf isn't interchangeable as the multiproto channels.conf now seems to be rejected and I can't even start VDR now. Perhaps the leading A is now unsupported in the options, is there a way I could possibly modify the file to remove this stuff? See the above ;) Any more ideas? ;-) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
On 04.02.2009 11:41, Morfsta wrote: ...[ tunig problems ] Any suggestions? Have you considered trying VDR 1.7.4? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
I still think it's a problem with the channel.conf. For fun, please try using the old and default scan for DVB-T. Because I used the old dvb-scan with the option to output for VDR on my Gigabyte GT-U7000-RH based DVB-T adapter to scan for KPN Digitenne bouquets (location Zwolle/Apeldoorn). Tried this, again finds all the channels but when put into VDR no video appears (however I do see the programme listings in the EPG). Any more ideas? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
On Wed, Feb 4, 2009 at 10:58 AM, Klaus Schmidinger klaus.schmidin...@cadsoft.de wrote: Have you considered trying VDR 1.7.4? Klaus, 1.7.4 works fine with S2API and DVB-T here Looks like there might be a problem in your patch somewhere Niels, but not sure where? I would still prefer to use 1.7.0 if possible, as expected a ton of plugins don't compile with 1.7.4... :-( ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
Due to an attempt on OS upgrade and thus kernel upgrade I'm grudgingly (it worked for me for months with no issues so why would I want to change it for now?) trying to make the transition from multiproto to S2API. I have two DVB-T cards and a NOVA-S2-HD (HVR4000 lite). I have downloaded a vanilla vdr-1.7.0 applied the h264 patch and the s2api patch and install S2API from Steven Toth's mercurial repository. Can you try with vdr-1.7.4, that's the first version from vdr 1.7x series that i got working with s2api and hvr-4000. I have testeed it with streamdev server plugin and mplayervlc. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr 1.7.0 and lifeview pci trio(saa7134)
hi, i had tried many times to install vdr with no luck, but i found a tutorial on how to install vdr 1.7.0 on ubuntu-like systems, from source code. It was pretty straight forward, i didn't have any problem on compiling and installing everything. I've got a lifeview trio pci card, saa7134, and ubuntu detected the card and loaded itself the modules saa7134, saa7134_alsa and saa7134_dvb. It works great with kaffeine, out of the box However, i need your help trying to make vdr get to the card. This tutorial says that i must install multiproto drivers. So, i downloaded them and compiled vdr on that. I didn't run make install on the multiproto path. Should i use the multiproto drivers instead of the ones that come with the kernel? As far as i understand the tutorial said it was necessary for compiling, but not for running vdr. Correct me if i'm wrong. So... everything is compiled without any problem and i run vdr like this: * /usr/bin/vdr -c /etc/vdr -E /var/vdr -l 3 -P'xineliboutput -l none -r 37890 -p' -u root * on the other hand if i run scan, i can find all the possible channels i get from the satellite. I did this to get the channels.conf for vdr: * scan -o vdr /home/servidor/.kde/share/apps/kaffeine/dvb-s/Astra-19.2E channels.conf * which gave some results and then i put this file into the /etc/vdr path. If then i look into the logs, i see this: * Dec 14 01:08:49 jordimoles vdr: [1006] cTimeMs: using monotonic clock (resolution is 1 ns) Dec 14 01:08:49 jordimoles vdr: [1006] VDR version 1.7.0 started Dec 14 01:08:49 jordimoles vdr: [1006] switched to user 'root' Dec 14 01:08:49 jordimoles vdr: [1006] codeset is 'UTF-8' - known Dec 14 01:08:51 jordimoles vdr: [1006] found 23 locales in /usr/share/locale Dec 14 01:08:51 jordimoles vdr: [1006] loading plugin: /usr/lib/vdr/plugins/libvdr-xineliboutput.so.1.7.0 Dec 14 01:08:51 jordimoles vdr: [1006] loading /etc/vdr/setup.conf Dec 14 01:08:51 jordimoles vdr: [1006] loading /etc/vdr/sources.conf Dec 14 01:08:51 jordimoles vdr: [1006] loading /etc/vdr/diseqc.conf Dec 14 01:08:51 jordimoles vdr: [1006] loading /etc/vdr/channels.conf Dec 14 01:08:51 jordimoles vdr: [1006] loading /etc/vdr/svdrphosts.conf Dec 14 01:08:51 jordimoles vdr: [1006] loading /etc/vdr/keymacros.conf Dec 14 01:08:51 jordimoles vdr: [1007] video directory scanner thread started (pid=1006, tid=1007) Dec 14 01:08:51 jordimoles vdr: [1008] video directory scanner thread started (pid=1006, tid=1008) Dec 14 01:08:51 jordimoles vdr: [1006] reading EPG data from /var/vdr Dec 14 01:08:51 jordimoles vdr: [1006] probing /dev/dvb/adapter0/frontend0 Dec 14 01:08:51 jordimoles vdr: [1007] video directory scanner thread ended (pid=1006, tid=1007) Dec 14 01:08:51 jordimoles vdr: [1008] video directory scanner thread ended (pid=1006, tid=1008) Dec 14 01:08:52 jordimoles vdr: [1006] ERROR (dvbdevice.c,471): Operation not supported Dec 14 01:08:52 jordimoles vdr: [1010] section handler thread started (pid=1006, tid=1010) Dec 14 01:08:52 jordimoles vdr: [1006] found 1 video device Dec 14 01:08:52 jordimoles vdr: [1006] initializing plugin: xineliboutput (1.0.90-cvs): X11/xine-lib output plugin Dec 14 01:08:52 jordimoles vdr: [1006] [xine..put] cTimePts: clock_gettime(CLOCK_MONOTONIC): clock resolution 0 us Dec 14 01:08:52 jordimoles vdr: [1006] [xine..put] cTimePts: using monotonic clock Dec 14 01:08:52 jordimoles vdr: [1006] [xine..put] RTP SSRC: 0x24a224e1 Dec 14 01:08:52 jordimoles vdr: [1006] setting primary device to 2 Dec 14 01:08:52 jordimoles vdr: [1006] assuming manual start of VDR Dec 14 01:08:52 jordimoles vdr: [1006] SVDRP listening on port 2001 Dec 14 01:08:52 jordimoles vdr: [1006] setting current skin to sttng Dec 14 01:08:52 jordimoles vdr: [1006] loading /etc/vdr/themes/sttng-default.theme Dec 14 01:08:52 jordimoles vdr: [1006] starting plugin: xineliboutput Dec 14 01:08:52 jordimoles vdr: [1012] Remote decoder/display server (cXinelibServer) thread started (pid=1006, tid=1012) Dec 14 01:08:52 jordimoles vdr: [1012] [xine..put] cXinelibServer priority set successful SCHED_RR 2 [1,99] Dec 14 01:08:52 jordimoles vdr: [1012] [xine..put] Listening on port 37890 Dec 14 01:08:52 jordimoles vdr: [1012] [xine..put] Listening for UDP broadcasts on port 37890 Dec 14 01:08:52 jordimoles vdr: [1012] [discovery] BROADCAST: VDR xineliboutput DISCOVERY 1.0^M Server port: 37890^M Server version: xineliboutput-1.0.90-cvs^M ^M Dec 14 01:08:52 jordimoles vdr: [1006] [xine..put] cXinelibDevice::StartDevice(): Device started Dec 14 01:08:52 jordimoles vdr: [1013] KBD remote control thread started (pid=1006, tid=1013) Dec 14 01:08:52 jordimoles vdr: [1006] remote control KBD - learning keys Dec 14 01:09:02 jordimoles vdr: [1006] switching to channel 1 Dec 14 01:09:02 jordimoles vdr: [1006] info: Canal no disponible! Dec 14 01:09:04 jordimoles vdr: [1006] switching to channel 1 Dec 14 01:09:04 jordimoles vdr: [1006] info:
Re: [vdr] vdr 1.7.0 + reelbox plugin problem - solved
Well it turned out that for some reason Fedora 9 (kernel 2.6.25.14-108.fc9.i686) and VIA EX1EG motherboard and Reelbox eHD combination doesn't work. I re-installed Fedora twice to make sure. (And still it might be that I overlooked something...) Then I installed an identical Fedora 9 on a different motherboard and it worked immidiately. Big thanks to Niels Wagenaar and Georg Acher for helping me out. Would never have gotten it to work without your help! Josce ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr 1.7.0 + reelbox plugin preoblem
Could you define mosaic? Would you be able to post a picture of some kind?
To be honost, I haven't updated the hdplayer3 stuff for some while now.
So it could be related to a new update in the svn in the reelbox
plugin/hdplayer3.
I guess the correct term would be artifacts?
I can see the video but here and there across the screen are small boxes.
I also get in my log file:
video vdr: [2037] buffer usage: 100% (tid=2036)
video vdr: [2037] ERROR: 1181 ring buffer overflows (222017 bytes dropped)
The harddisk has DMA on.
To me it seems that the eHD can't get the stream quickly enough.
When I run lspci -b I get 3 devices sharing with IRQ 5:
02:01.0 Audio device: VIA Technologies, Inc. VIA High Definition Audio
Controller (rev 10)
Subsystem: VIA Technologies, Inc. Unknown device aa09
Flags: bus master, fast devsel, latency 0, IRQ 5
Memory at dfefc000 (64-bit, non-prefetchable)
Capabilities: [50] Power Management version 2
Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0
Enable-
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel ?
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1
Controller (rev 90) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. Unknown device aa09
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at f400
Capabilities: [80] Power Management version 2
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
03:0f.0 Multimedia controller: Micronas USA, Inc. Unknown device 8100
Subsystem: Micronas USA, Inc. Unknown device 8100
Flags: bus master, medium devsel, latency 32, IRQ 5
Memory at d7ffd000 (32-bit, non-prefetchable)
Memory at c800 (32-bit, non-prefetchable)
Capabilities: [40] Power Management version 2
[EMAIL PROTECTED] tv]# hdparm -i /dev/sda
/dev/sda:
Model=ST3320620AS , FwRev=3.AAK , SerialNo=
9QF6E4RS
Config={ HardSect NotMFM HdSw15uSec Fixed DTR10Mbs RotSpdTol.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=16384kB, MaxMultSect=16, MultSect=?16?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=625142448
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=no WriteCache=enabled
Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7
Regards,
Josce
_
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+worldmkt=en-USform=QBRE___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr 1.7.0 + reelbox plugin problem
I have also noted that sometimes when I boot my pc the eHD card gets an IRQ 255. [EMAIL PROTECTED] tv]#lcpci -v 03:0f.0 Multimedia controller: Micronas USA, Inc. Unknown device 8100 Subsystem: Micronas USA, Inc. Unknown device 8100 Flags: medium devsel, IRQ 255 Memory at dfc0 (32-bit, non-prefetchable) [disabled] [size=4K] Memory at 2000 (32-bit, non-prefetchable) [disabled] [size=128M] Capabilities: [40] Power Management version 2 When this happens I can't start the card: [EMAIL PROTECTED] tv]# modprobe hdshm [EMAIL PROTECTED] tv]# /usr/local/src/eHD/hdboot -i /usr/local/src/eHD/linux.bin Decypher PCI BAR1: 2000 Warm Reset Timeout: U-Boot not ready for PCI boot [EMAIL PROTECTED] tv]# Could my card be defect? Josce ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.0 + reelbox plugin problem
Noticed some other thing. When I playback a recording that worked well with vdr 1.6.0 the subtitles come 6-7 seconds before they should. The audio and video are in sync. I also get, (which I don't know what they are): virtual void Reel::HdOsd::SetActive(bool) On=1 virtual void Reel::HdOsd::SetActive(bool) On=0 virtual void Reel::HdOsd::SetActive(bool) On=1 virtual void Reel::HdOsd::SetActive(bool) On=0 GET STC 0 virtual void Reel::HdOsd::SetActive(bool) On=1 GET STC 0 GET STC 0 GET STC 0 GET STC 0 GET STC 0 vdr-1.7.0 +vdr-1.6.0-truecolor-compile_fixes.diff +vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff +vdr-1.7.0-multiproto-update.diff Reelbox plugin (SVN revision 8171) multiproto from http://mercurial.intuxication.org/hg/liplianindvb Josce ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.0 + reelbox plugin problem
On Sat, Sep 20, 2008 at 03:41:23PM +0300, Josce wrote: I have also noted that sometimes when I boot my pc the eHD card gets an IRQ 255. [EMAIL PROTECTED] tv]#lcpci -v 03:0f.0 Multimedia controller: Micronas USA, Inc. Unknown device 8100 Subsystem: Micronas USA, Inc. Unknown device 8100 Flags: medium devsel, IRQ 255 Memory at dfc0 (32-bit, non-prefetchable) [disabled] [size=4K] Memory at 2000 (32-bit, non-prefetchable) [disabled] [size=128M] Capabilities: [40] Power Management version 2 When this happens I can't start the card: [EMAIL PROTECTED] tv]# modprobe hdshm [EMAIL PROTECTED] tv]# /usr/local/src/eHD/hdboot -i /usr/local/src/eHD/linux.bin Decypher PCI BAR1: 2000 Warm Reset Timeout: U-Boot not ready for PCI boot [EMAIL PROTECTED] tv]# Could my card be defect? There is a reset circuit on the that controls the complicated power sequencing. It is possible that your BIOS is too fast and configures the PCI space during this powerup sequence. At that time, the HDE is not properly accessible. It is possible to shorten this sequence a bit, but for that you need to exchange a SMD capacitor on the HDE board. -- Georg Acher, [EMAIL PROTECTED] http://www.lrr.in.tum.de/~acher Oh no, not again ! The bowl of petunias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.0 + reelbox plugin preoblem
On Sat, Sep 20, 2008 at 11:44:34AM +, Josce wrote: Could you define mosaic? Would you be able to post a picture of some kind? To be honost, I haven't updated the hdplayer3 stuff for some while now. So it could be related to a new update in the svn in the reelbox plugin/hdplayer3. I guess the correct term would be artifacts? I can see the video but here and there across the screen are small boxes. I also get in my log file: video vdr: [2037] buffer usage: 100% (tid=2036) video vdr: [2037] ERROR: 1181 ring buffer overflows (222017 bytes dropped) The harddisk has DMA on. To me it seems that the eHD can't get the stream quickly enough. What is the CPU load during that time? The host CPU transfers the data into the shared memory on the card, so anything below 80-90% load indicates another problem. When I run lspci -b I get 3 devices sharing with IRQ 5: The card does not use the IRQ, so that is not relevant. -- Georg Acher, [EMAIL PROTECTED] http://www.lrr.in.tum.de/~acher Oh no, not again ! The bowl of petunias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.0 + reelbox plugin problem
On Sat, Sep 20, 2008 at 06:46:14PM +0300, Josce wrote: Noticed some other thing. When I playback a recording that worked well with vdr 1.6.0 the subtitles come 6-7 seconds before they should. The audio and video are in sync. Have a look at the hdtsplay-demo in the hdshm3-folder. It is a simple demo that plays back TS files over the DeCypher. If that works, your basic driver setup (+ the HW) is OK, and something in the vdr (or the patches) itself is wrong. -- Georg Acher, [EMAIL PROTECTED] http://www.lrr.in.tum.de/~acher Oh no, not again ! The bowl of petunias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.0 + reelbox plugin problem
There is a reset circuit on the that controls the complicated power sequencing. It is possible that your BIOS is too fast and configures the PCI space during this powerup sequence. At that time, the HDE is not properly accessible. It is possible to shorten this sequence a bit, but for that you need to exchange a SMD capacitor on the HDE board. OK, thanks. I have the Quick Power On Self Test enabled, so by disabling this I should have this problem fixed. Josce ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.0 + reelbox plugin problem
Have a look at the hdtsplay-demo in the hdshm3-folder. It is a simple demo that plays back TS files over the DeCypher. If that works, your basic driver setup (+ the HW) is OK, and something in the vdr (or the patches) itself is wrong. Playing back a ts file with hdtsplay is actually even worse. I am using a patched hdshm.c file that I downloaded. The one in the reelbox SVN testing used 'pci_get_device_reverse', which I think has been removed from the newer kernels. I will SVN a completely fresh reelbox tommorrow and see if maybe I have made some mistakes when installing the drivers. Josce ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 - Patched for S2-3200 - Diseqc.conf
Jelle De Loecker schreef: I've finally gotten VDR to work with my Technotrend S2-3200 card, but I just can't seem to get this diseqc.conf file right! S19.2E 11700 V 9750 [E0 10 38 F0] S19.2E 9 V 10600 [E0 10 38 F1] S19.2E 11700 H 9750 [E0 10 38 F2] S19.2E 9 H 10600 [E0 10 38 F3] S28.2E 11700 V 9750 [E0 10 38 F4] S28.2E 9 V 10600 [E0 10 38 F5] S28.2E 11700 H 9750 [E0 10 38 F6] S28.2E 9 H 10600 [E0 10 38 F7] I have a diseqc 2.0 switch, but since the S2-3200 card only supports Diseqc 1.2 I'm not really sure what to use! It's a regular 4x1 switch Apparantly a regular 4x1 switch doesn't need the F0 - F1 bits at the end, and this will do. As I see it, the first hex-code is used for the option and the second hex-code is used for the position. (A/A-A/B-B/A-B/B) 22 Position A 23 Option A 26 Position B 27 Option B # port 1 option a position a # port 2 option a position b # port 3 option b position a # port 4 option b position b So in your setup I assume that you have ports and LNBs like this: 1 - S19.2E 2 - S28.2E 3 - S23.5E 4 - S13.0E This diseqc.conf should do the trick: # port 1 S19.2E 11700 V 9750 t v W15 [E0 10 23] W15 [E0 10 22] W15 t S19.2E 9 V 10600 t v W15 [E0 10 23] W15 [E0 10 22] W15 T S19.2E 11700 H 9750 t V W15 [E0 10 23] W15 [E0 10 22] W15 t S19.2E 9 H 10600 t V W15 [E0 10 23] W15 [E0 10 22] W15 T # port 2 S28.2E 11700 V 9750 t v W15 [E0 10 23] W15 [E0 10 26] W15 t S28.2E 9 V 10600 t v W15 [E0 10 23] W15 [E0 10 26] W15 T S28.2E 11700 H 9750 t V W15 [E0 10 23] W15 [E0 10 26] W15 t S28.2E 9 H 10600 t V W15 [E0 10 23] W15 [E0 10 26] W15 T # port 3 S23.5E 11700 V 9750 t v W15 [E0 10 27] W15 [E0 10 22] W15 t S23.5E 9 V 10600 t v W15 [E0 10 27] W15 [E0 10 22] W15 T S23.5E 11700 H 9750 t V W15 [E0 10 27] W15 [E0 10 22] W15 t S23.5E 9 H 10600 t V W15 [E0 10 27] W15 [E0 10 22] W15 T # port 4 S13.0E 11700 V 9750 t v W15 [E0 10 27] W15 [E0 10 26] W15 t S13.0E 9 V 10600 t v W15 [E0 10 27] W15 [E0 10 26] W15 T S13.0E 11700 H 9750 t V W15 [E0 10 27] W15 [E0 10 26] W15 t S13.0E 9 H 10600 t V W15 [E0 10 27] W15 [E0 10 26] W15 T Should you need to edit the first port I got this solution from the archive from these very own mailing lists, but it was very hard to find so I thought I'd post it again. It works like a charm: http://www.linuxtv.org/pipermail/vdr/2005-October/005517.html (thank you *Sami J. Mäkinen)* ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.0 and reelchannelscan-1.6 plugin
On Tue, May 20, 2008 at 2:22 AM, Mike Booth [EMAIL PROTECTED] wrote:
I am unable to compile this plugin. It fails with csmenu.c:236:
error: 'class cDevice' has no member named 'ProvidesS2'.
cDevice::ProvidesS2() is not from orignal-vdr. You can add this
function to your cDevice class
bool cDevice::ProvidesS2() const
{
return false;
}
I'm using vdr-1.7.0, multiproto_plus and the reelchannelscan plugin is from
CVS
I am not sure if reelchannelscan works with multiproto.
--
Best,
Sundararaj
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.0 and reelchannelscan-1.6 plugin
On Tue, May 20, 2008 at 2:22 AM, Mike Booth [EMAIL PROTECTED] wrote:
I am unable to compile this plugin. It fails with csmenu.c:236:
error: 'class cDevice' has no member named 'ProvidesS2'.
cDevice::ProvidesS2() is not from orignal-vdr. You can add this
function to your cDevice class
bool cDevice::ProvidesS2() const
{
return false;
}
I'm using vdr-1.7.0, multiproto_plus and the reelchannelscan plugin is from
CVS
I am not sure if reelchannelscan works with multiproto.
on my vdr 170 with multiproto_plus the patched reelchannelscan 0.4.1 works well
I hope that someone can patch the reelchannelscan 0.6.1 for vdr 170 multiproto
Igor
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 ERROR (dvbdevice.c,302): Invalid argument
Here is my error: May 15 14:03:21 mbox2 vdr: [21729] ERROR (dvbdevice.c,302): Invalid argument May 15 14:03:21 mbox2 kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 May 15 14:03:32 mbox2 vdr: [21729] ERROR (dvbdevice.c,302): Invalid argument May 15 14:03:32 mbox2 kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 May 15 14:03:42 mbox2 vdr: [21729] frontend 0 timed out while tuning to channel 20, tp 111421 Im using a WinTV Nova HD S2. Im using multiproto_plus patched with HVR-4000-multiproto_plus-2008-05-02.diff. I got one error on the last part of the HVR patch, couldnt find the file modules.order, but i didnt think it was important. I dont know what you did that fixed this, but i sure cant get it working. Any ideas? Is it a driver problem or vdr? Regards Nilsn Hi, Looks like the latest HVR patch is broken(HVR-4000-multiproto_plus-2008-05-02.diff.bz2 ) Gregoire Favre released 2 patches the same day. The second one is missing the _set_delsys call. I will be testing this tonight. have you any results ? Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.0 and reelchannelscan-1.6 plugin
I am unable to compile this plugin. It fails with csmenu.c:236:
error: 'class cDevice' has no member named 'ProvidesS2'.
cDevice::ProvidesS2() is not from orignal-vdr. You can add this
function to your cDevice class
bool cDevice::ProvidesS2() const
{
return false;
}
I'm using vdr-1.7.0, multiproto_plus and the reelchannelscan plugin is
from
CVS
I am not sure if reelchannelscan works with multiproto.
on my vdr 170 with multiproto_plus the patched reelchannelscan 0.4.1 works
well
I hope that someone can patch the reelchannelscan 0.6.1 for vdr 170
multiproto
sorry, I should clarify. On vdr 1.7.0 the patched reelchannelscan 0.4.1 works
well only with dvb-s, it couldn't find the
dvb-s2 channels
Igor
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-1.7.0 and reelchannelscan-1.6 plugin
I am unable to compile this plugin. It fails with csmenu.c:236: error: 'class cDevice' has no member named 'ProvidesS2'. Can anyone provide any info that might help. I've scanned everywhere for mention of ProvidesS2 with no luck. I'm using vdr-1.7.0, multiproto_plus and the reelchannelscan plugin is from CVS Mike ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 ERROR (dvbdevice.c,302): Invalid argument
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bjørnar Nilsen Sent: 15. mai 2008 14:15 To: 'Igor'; 'VDR Mailing List' Subject: Re: [vdr] VDR 1.7.0 ERROR (dvbdevice.c,302): .. Snip .. Here is my error: May 15 14:03:21 mbox2 vdr: [21729] ERROR (dvbdevice.c,302): Invalid argument May 15 14:03:21 mbox2 kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 May 15 14:03:32 mbox2 vdr: [21729] ERROR (dvbdevice.c,302): Invalid argument May 15 14:03:32 mbox2 kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 May 15 14:03:42 mbox2 vdr: [21729] frontend 0 timed out while tuning to channel 20, tp 111421 Im using a WinTV Nova HD S2. Im using multiproto_plus patched with HVR-4000-multiproto_plus-2008-05-02.diff. I got one error on the last part of the HVR patch, couldnt find the file modules.order, but i didnt think it was important. I dont know what you did that fixed this, but i sure cant get it working. Any ideas? Is it a driver problem or vdr? Regards Nilsn Hi, Looks like the latest HVR patch is broken(HVR-4000-multiproto_plus-2008-05-02.diff.bz2 ) Gregoire Favre released 2 patches the same day. The second one is missing the _set_delsys call. I will be testing this tonight. Regards Nilsn ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 ERROR (dvbdevice.c,302): Invalid argument
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Igor Sent: 28. april 2008 07:29 To: VDR Mailing List Subject: [vdr] VDR 1.7.0 ERROR (dvbdevice.c,302): Invalid argument Hi when I want to switch on dvb-s2 channel ASTRA HD+;BetaDigital:11914:hC910I1M2O35S1:S19.2E:27500:1279:0;1283= deu:0:0:131:133:6:0 Her is the channel im trying: CANAL+ FILM HD;Telenor:11421:hC23M5O25S1:S1.0W:25000:513:644=eng;645=eng:0:B00:3306:70:1 4:0 I receive this error ..snip Apr 28 09:19:20 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:20 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:30 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:30 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:41 localhost vdr: [4197] frontend 0 timed out while tuning to channel 2782, tp 111914 Here is my error: May 15 14:03:21 mbox2 vdr: [21729] ERROR (dvbdevice.c,302): Invalid argument May 15 14:03:21 mbox2 kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 May 15 14:03:32 mbox2 vdr: [21729] ERROR (dvbdevice.c,302): Invalid argument May 15 14:03:32 mbox2 kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 May 15 14:03:42 mbox2 vdr: [21729] frontend 0 timed out while tuning to channel 20, tp 111421 Im using a WinTV Nova HD S2. Im using multiproto_plus patched with HVR-4000-multiproto_plus-2008-05-02.diff. I got one error on the last part of the HVR patch, couldnt find the file modules.order, but i didnt think it was important. I dont know what you did that fixed this, but i sure cant get it working. Any ideas? Is it a driver problem or vdr? Regards Nilsn ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 multiproto hvr4000 - multiproto_plus
Have you replaced linux/include/linux/compiler.h with the one from your kernel ? (in multiproto_plus dir) if that's going to be included, this shouldn't be in of course. your patch included the compiler.h, after replacing it with the right one the drivers are build your patch also created a .config.old in v4l and the cx88 modules are not build (the .config created during make does only contain inaktive lines for cx88 modules), i modified the .config manual and started make again OK, here's one without compiler.h and without .config.old (by the way, I don't understand why make distclean didn't remove it...). Good new, such way the patch is even smaller, so it would be really good to have it included finally into the repo :-) Any objection to the inclusion ? with this patch I have the error May 3 22:42:15 localhost vdr: [3471] ERROR (dvbdevice.c,302): Invalid argument when I try to tune on dvb-s2 channels on VDR But with HVR-4000-multiproto_plus-2008-04-25.diff + HVR-4000-multiproto_plus-2008-04-25_inversion is OK for me Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0
when I want to switch on dvb-s2 channels ( Apr 28 09:18:32 localhost vdr: [4188] switching to channel 2782 Apr 28 09:18:32 localhost vdr: [4535] transfer thread ended (pid=4188, tid=4535) Apr 28 09:18:32 localhost vdr: [4188] buffer stats: 0 (0%) used Apr 28 09:18:32 localhost vdr: [4756] transfer thread started (pid=4188, tid=4756) Apr 28 09:18:32 localhost vdr: [4537] TS buffer on device 1 thread ended (pid=4188, tid=4537) Apr 28 09:18:32 localhost vdr: [4536] buffer stats: 0 (0%) used Apr 28 09:18:32 localhost vdr: [4536] receiver on device 1 thread ended (pid=4188, tid=4536) Apr 28 09:18:32 localhost vdr: [4757] receiver on device 1 thread started (pid=4188, tid=4757) Apr 28 09:18:32 localhost vdr: [4758] TS buffer on device 1 thread started (pid=4188, tid=4758) Apr 28 09:18:40 localhost vdr: [4197] frontend 0 timed out while tuning to channel 2782, tp 111914 Apr 28 09:18:40 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:18:40 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:18:50 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:18:50 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:00 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:00 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:10 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:10 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:20 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:20 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:30 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:30 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:41 localhost vdr: [4197] frontend 0 timed out while tuning to channel 2782, tp 111914 Please post the channels.conf line of that channel. ASTRA HD+;BetaDigital:11914:hC910M2O35S1:S19.2E:27500:1279:0;1283=deu:0:0:131:133:6:0 but the problem was in bug inside cx24116 driver Gilmi has fixed it in HVR-4000-multiproto_plus-2008-04-25_inversion patch for cx24116.c Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 multiproto hvr4000 - multiproto_plus
with this patch I could receive dvb-s2 channels on my VDR 170 I don't have the error May 3 22:42:15 localhost vdr: [3471] ERROR (dvbdevice.c,302): Invalid argument anymore @gilmi thanks Igor sorry, took a little bit longer to find time for made the patch. This patch is against multiproto_plus + HVR-4000-multiproto_plus-2008-04-25.diff. With this combination i'm able to tune all HDTV channels on Astra 19.2E. My Hardware is a WinTV Nova HD S2. cu Edgar (gimli) Hucek On Tue, Apr 29, 2008 at 10:18:30AM +0200, gimli wrote: Some postings before i read about multiproto + hvr4000 and tuning problems. I had that problems myselfe. The problem is the inversion setting in the driver. It's a driver bug. At the moment i do not have my modified driver by hand. Will post it in later today. I did a mixuup between : http://www.linuxtv.org/pipermail/linux-dvb/2008-March/024487.html and http://www.mail-archive.com/[EMAIL PROTECTED]/msg27438.html a patch i have done. c Edgar (gimli) Hucek Oh, nice one, could you correct my update on your work for multiproto_plus : http://linuxtv.org/pipermail/linux-dvb/2008-April/025655.html I must have different hardware because all works just fine here... Thanks, -- GrИgoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre ATTACHMENT: application/octet-stream (HVR-4000-multiproto_plus-2008-04-25_inversion.diff) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 multiproto hvr4000 - multiproto_plus
On Fri, May 02, 2008 at 12:03:48AM +0200, gimli wrote: Hi, sorry, took a little bit longer to find time for made the patch. This patch is against multiproto_plus + HVR-4000-multiproto_plus-2008-04-25.diff. With this combination i'm able to tune all HDTV channels on Astra 19.2E. My Hardware is a WinTV Nova HD S2. With this new patch, there is no change for me, which is fine, because everything was already working so it don't break anything here :-) I attach an all in one patch just to be easier to follow, and as you wrote it to VDR's ml, I sent a copy there also. Steven and Manu : could it be included into multiproto_plus ? Thanks you very much, -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre HVR-4000-multiproto_plus-2008-05-02.diff.bz2 Description: Binary data ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 multiproto hvr4000 - multiproto_plus
Gregoire Favre wrote: On Fri, May 02, 2008 at 12:03:48AM +0200, gimli wrote: Hi, sorry, took a little bit longer to find time for made the patch. This patch is against multiproto_plus + HVR-4000-multiproto_plus-2008-04-25.diff. With this combination i'm able to tune all HDTV channels on Astra 19.2E. My Hardware is a WinTV Nova HD S2. With this new patch, there is no change for me, which is fine, because everything was already working so it don't break anything here :-) I attach an all in one patch just to be easier to follow, and as you wrote it to VDR's ml, I sent a copy there also. Steven and Manu : could it be included into multiproto_plus ? after this patch the multiproto_plus does not compile against my older kernel (suse 10.2 stock kernel 2.6.18) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 multiproto hvr4000 - multiproto_plus
Gregoire Favre wrote: On Fri, May 02, 2008 at 01:15:45PM +0200, Lars Bläser wrote: after this patch the multiproto_plus does not compile against my older kernel (suse 10.2 stock kernel 2.6.18) Have you replaced linux/include/linux/compiler.h with the one from your kernel ? (in multiproto_plus dir) if that's going to be included, this shouldn't be in of course. your patch included the compiler.h, after replacing it with the right one the drivers are build your patch also created a .config.old in v4l and the cx88 modules are not build (the .config created during make does only contain inaktive lines for cx88 modules), i modified the .config manual and started make again ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 multiproto hvr4000 - multiproto_plus
Hi, sorry, took a little bit longer to find time for made the patch. This patch is against multiproto_plus + HVR-4000-multiproto_plus-2008-04-25.diff. With this combination i'm able to tune all HDTV channels on Astra 19.2E. My Hardware is a WinTV Nova HD S2. cu Edgar (gimli) Hucek On Tue, Apr 29, 2008 at 10:18:30AM +0200, gimli wrote: Some postings before i read about multiproto + hvr4000 and tuning problems. I had that problems myselfe. The problem is the inversion setting in the driver. It's a driver bug. At the moment i do not have my modified driver by hand. Will post it in later today. I did a mixuup between : http://www.linuxtv.org/pipermail/linux-dvb/2008-March/024487.html and http://www.mail-archive.com/[EMAIL PROTECTED]/msg27438.html a patch i have done. c Edgar (gimli) Hucek Oh, nice one, could you correct my update on your work for multiproto_plus : http://linuxtv.org/pipermail/linux-dvb/2008-April/025655.html I must have different hardware because all works just fine here... Thanks, -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre HVR-4000-multiproto_plus-2008-04-25_inversion.diff Description: Binary data ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR 1.7.0 multiproto hvr4000
Some postings before i read about multiproto + hvr4000 and tuning problems. I had that problems myselfe. The problem is the inversion setting in the driver. It's a driver bug. At the moment i do not have my modified driver by hand. Will post it in later today. I did a mixuup between : http://www.linuxtv.org/pipermail/linux-dvb/2008-March/024487.html and http://www.mail-archive.com/[EMAIL PROTECTED]/msg27438.html a patch i have done. c Edgar (gimli) Hucek ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 multiproto hvr4000 - multiproto_plus
On Tue, Apr 29, 2008 at 10:18:30AM +0200, gimli wrote: Some postings before i read about multiproto + hvr4000 and tuning problems. I had that problems myselfe. The problem is the inversion setting in the driver. It's a driver bug. At the moment i do not have my modified driver by hand. Will post it in later today. I did a mixuup between : http://www.linuxtv.org/pipermail/linux-dvb/2008-March/024487.html and http://www.mail-archive.com/[EMAIL PROTECTED]/msg27438.html a patch i have done. c Edgar (gimli) Hucek Oh, nice one, could you correct my update on your work for multiproto_plus : http://linuxtv.org/pipermail/linux-dvb/2008-April/025655.html I must have different hardware because all works just fine here... Thanks, -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 + xine plugin 0.8.2 - seve ral issues
But if I disconnect from the card the antenna I will have this problem [snip] let's see in the xine output [snip] video_out: throwing away image with pts 96108366 because it's too old (diff : 434402). video_out: throwing away image with pts 96111366 because it's too old (diff : 431402). When you disconnect the antenna cable for a certain amount of time, there will be a gap in presentation time stamps (PTS). This will cause xine to jump over the gap with the result that the previously established buffer will run empty immediately. Any further received images will therefore arrive to late at xine and cause the above messages. today I disconnected the antenna cable again and didn't discover this problem (I don't know why) Apr 28 09:54:29 localhost vdr: [6060] switching to channel 2 Apr 28 09:54:29 localhost vdr: [6060] buffer stats: 0 (0%) used Apr 28 09:54:29 localhost vdr: [6126] transfer thread started (pid=6060, tid=6126) Apr 28 09:54:29 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:54:30 localhost vdr: [6124] TS buffer on device 1 thread ended (pid=6060, tid=6124) Apr 28 09:54:30 localhost vdr: [6123] buffer stats: 0 (0%) used Apr 28 09:54:30 localhost vdr: [6123] receiver on device 1 thread ended (pid=6060, tid=6123) Apr 28 09:54:30 localhost vdr: [6127] receiver on device 1 thread started (pid=6060, tid=6127) Apr 28 09:54:30 localhost vdr: [6128] TS buffer on device 1 thread started (pid=6060, tid=6128) Apr 28 09:54:40 localhost vdr: [6064] frontend 0 timed out while tuning to channel 2, tp 111953 Apr 28 09:54:40 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:55:11 localhost last message repeated 3 times Apr 28 09:55:32 localhost last message repeated 2 times Apr 28 09:55:42 localhost vdr: [6064] frontend 0 timed out while tuning to channel 2, tp 111953 Apr 28 09:55:42 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:56:13 localhost last message repeated 3 times Apr 28 09:56:34 localhost last message repeated 2 times Apr 28 09:56:45 localhost vdr: [6064] frontend 0 timed out while tuning to channel 2, tp 111953 Apr 28 09:56:45 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Maybe I can find a solution for vdr-xine to detect this issue and reestablish a suitable buffer in this case. fine :) Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 ERROR (dvbdevice.c,302): Invalid argument
On Mon, Apr 28, 2008 at 09:29:26AM +0400, Igor wrote: Hi when I want to switch on dvb-s2 channel ASTRA HD+;BetaDigital:11914:hC910I1M2O35S1:S19.2E:27500:1279:0;1283=deu:0:0:131:133:6:0 Well, I have this : ASTRA HD+;BetaDigital:11914:hC910M2O35S1:S19.2E:27500:1279:0;1283=deu:0:0:131:133:6:0 Which is alsmost the same, but not, and which works ;-) Give it a try :-) -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 ERROR (dvbdevice.c,302): Invalid argument
Gregoire have you the same dvbdevice.c as me ? when I want to switch on dvb-s2 channel ASTRA HD+;BetaDigital:11914:hC910I1M2O35S1:S19.2E:27500:1279:0;1283=deu:0:0:131:133:6:0 Well, I have this : ASTRA HD+;BetaDigital:11914:hC910M2O35S1:S19.2E:27500:1279:0;1283=deu:0:0:131:133:6:0 Which is alsmost the same, but not, and which works ;-) the difference is only in Inversion parameter. But your string didn't help me :( I have the same error Apr 28 22:13:27 localhost vdr: [4778] switching to channel 1 Apr 28 22:13:27 localhost vdr: [4789] transfer thread ended (pid=4778, tid=4789) Apr 28 22:13:27 localhost vdr: [4778] buffer stats: 0 (0%) used Apr 28 22:13:27 localhost vdr: [4822] transfer thread started (pid=4778, tid=4822) Apr 28 22:13:27 localhost vdr: [4791] TS buffer on device 1 thread ended (pid=4778, tid=4791) Apr 28 22:13:27 localhost vdr: [4790] buffer stats: 0 (0%) used Apr 28 22:13:27 localhost vdr: [4790] receiver on device 1 thread ended (pid=4778, tid=4790) Apr 28 22:13:27 localhost vdr: [4823] receiver on device 1 thread started (pid=4778, tid=4823) Apr 28 22:13:27 localhost vdr: [4824] TS buffer on device 1 thread started (pid=4778, tid=4824) Apr 28 22:13:30 localhost vdr: [4782] ERROR (dvbdevice.c,302): Invalid argument Apr 28 22:13:30 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 22:13:40 localhost vdr: [4782] frontend 0 timed out while tuning to channel 1, tp 111914 Apr 28 22:13:40 localhost vdr: [4782] ERROR (dvbdevice.c,302): Invalid argument Apr 28 22:13:40 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 22:13:50 localhost vdr: [4782] ERROR (dvbdevice.c,302): Invalid argument Apr 28 22:13:50 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 22:14:00 localhost vdr: [4782] ERROR (dvbdevice.c,302): Invalid argument Apr 28 22:14:00 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 22:14:11 localhost vdr: [4782] ERROR (dvbdevice.c,302): Invalid argument Apr 28 22:14:11 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 22:14:21 localhost vdr: [4782] ERROR (dvbdevice.c,302): Invalid argument Apr 28 22:14:21 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 22:14:31 localhost vdr: [4782] ERROR (dvbdevice.c,302): Invalid argument Apr 28 22:14:31 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 22:14:41 localhost vdr: [4782] frontend 0 timed out while tuning to channel 1, tp 111914 Apr 28 22:14:41 localhost vdr: [4782] ERROR (dvbdevice.c,302): Invalid argument ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 ERROR (dvbdevice.c,302): Invalid argument
On Mon, Apr 28, 2008 at 10:19:44PM +0400, Igor wrote: Gregoire have you the same dvbdevice.c as me ? md5sum /usr/src/vdr-1.7.0/dvbdevice.c 18981c81c4da6bb303b71b21147f3726 /usr/src/vdr-1.7.0/dvbdevice.c No idea... just md5sum your's. the difference is only in Inversion parameter. But your string didn't help me :( I have the same error Are you certain you compil vdr against multiproto ? Otherwise I don't have any idea what's going wrong at your place, sorry. -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR 1.7.0 + xine plugin 0.8.2 - several iisues
Hi I'm start to test my system - dvb-s2 card hvr4000 (with latest multiproto_plus + hvr4000 patch from Gregoire Favre) + VDR 1.7.0 + xine-plugin 0.8.2 + xine-lib-1.2 from HG + xine-ui from CVS + ffmpeg from SVN (I didn't test dvb-s2 yet, but it seems to me - the dvb-s works well) But if I disconnect from the card the antenna I will have this problem [EMAIL PROTECTED]:/usr/src/VDR$ ./vdr -c /etc/vdr -P xine -r - MakePrimaryDevice: 1 = SetVideoFormat: 0 SetVolumeDevice: 255 SetAudioChannelDevice: 0 SetDigitalAudioDevice: 0 SetAudioChannelDevice: 0 SetVolumeDevice: 255 SetPlayMode: 1 frame: (0, 0)-(-1, -1), zoom: (1.00, 1.00) vdr-xine: Client connecting ... vdr-xine: Client connected! frame: (0, 0)-(720, 576), zoom: (1.00, 1.00) video: synced early [VMA]buffered 8.2 frames (v:20.1, a:8.2) buffered 9.5 frames (v:18.8, a:9.5) SetPlayMode: 0 SetAudioChannelDevice: 0 SetDigitalAudioDevice: 0 SetAudioChannelDevice: 0 SetPlayMode: 1 [vVMA]buffered 8.5 frames (v:14.8, a:8.5) buffered 6.6 frames (v:15.3, a:6.6) frame: (0, 0)-(720, 576), zoom: (1.00, 1.00) SetPlayMode: 0 SetAudioChannelDevice: 0 SetDigitalAudioDevice: 0 SetAudioChannelDevice: 0 SetPlayMode: 1 frame: (0, 0)-(720, 576), zoom: (1.00, 1.00) audio: synced early [AMvV]buffered 12.2 frames (v:20.9, a:12.2) SetPlayMode: 0 frame: (0, 0)-(720, 576), zoom: (1.00, 1.00) SetAudioChannelDevice: 0 SetDigitalAudioDevice: 0 SetAudioChannelDevice: 0 =skipped frame: (0, 0)-(720, 576), zoom: (1.00, 1.00) SetPlayMode: 0 SetAudioChannelDevice: 0 SetDigitalAudioDevice: 0 SetAudioChannelDevice: 0 SetPlayMode: 1 SetPlayMode: 0 SetAudioChannelDevice: 0 SetDigitalAudioDevice: 0 SetAudioChannelDevice: 0 SetPlayMode: 1 SetPlayMode: 0 SetAudioChannelDevice: 0 SetDigitalAudioDevice: 0 SetAudioChannelDevice: 0 SetPlayMode: 1 SetPlayMode: 0 SetAudioChannelDevice: 0 SetDigitalAudioDevice: 0 SetAudioChannelDevice: 0 SetPlayMode: 1 frame: (0, 0)-(720, 576), zoom: (1.00, 1.00) vdr-xine: Client disconnected! #!!1 SetPlayMode: 0 [EMAIL PROTECTED]:/usr/src/VDR$ let's see in the xine output input_cache: read calls: 0, main input read calls: 0 input_cache: seek_calls: 0, main input seek calls: 0 input_vdr: shutting down rpc thread (timeout: 1 ms) ... input_vdr: joining rpc thread ... input_vdr: rpc thread joined. xine: found input plugin : file input plugin load_plugins: probing demux 'anx' load_plugins: probing demux 'image' load_plugins: probing demux 'wve' load_plugins: probing demux 'idcin' load_plugins: probing demux 'ipmovie' load_plugins: probing demux 'vqa' load_plugins: probing demux 'wc3movie' load_plugins: probing demux 'roq' load_plugins: probing demux 'str' load_plugins: probing demux 'film' load_plugins: probing demux 'smjpeg' load_plugins: probing demux 'fourxm' load_plugins: probing demux 'vmd' load_plugins: probing demux 'aiff' load_plugins: probing demux 'flac' load_plugins: probing demux 'realaudio' load_plugins: probing demux 'snd' load_plugins: probing demux 'tta' load_plugins: probing demux 'voc' load_plugins: probing demux 'vox' load_plugins: probing demux 'mpeg-ts' load_plugins: probing demux 'avi' load_plugins: probing demux 'mpeg_block' load_plugins: probing demux 'mpeg_pes' load_plugins: probing demux 'quicktime' load_plugins: probing demux 'fli' load_plugins: probing demux 'yuv4mpeg2' load_plugins: probing demux 'real' load_plugins: probing demux 'pva' load_plugins: probing demux 'slave' load_plugins: probing demux 'nsv' load_plugins: probing demux 'matroska' ebml: invalid EBML ID size (0x0) at position 1 ebml: invalid master element load_plugins: probing demux 'iff' load_plugins: probing demux 'flashvideo' load_plugins: probing demux 'playlist' load_plugins: probing demux 'nsfdemux' load_plugins: probing demux 'ogg' load_plugins: probing demux 'asf' load_plugins: probing demux 'mpeg' load_plugins: probing demux 'dts' demux_dts: unsupported DTS stream type, or not a DTS stream load_plugins: probing demux 'ac3' load_plugins: probing demux 'wav' load_plugins: probing demux 'cdda' load_plugins: probing demux 'rawdv' load_plugins: probing demux 'mpc' load_plugins: probing demux 'mp3' load_plugins: probing demux 'shn' load_plugins: probing demux 'elem' xine: found demuxer plugin: Elementary MPEG stream demux plugin load_plugins: plugin mpeg2 will be used for video streamtype 00. av_offset=0 pts spu_offset=0 pts xine_play play_internal ...done video_out: throwing away image with pts 96108366 because it's too old (diff : 434402). video_out: throwing away image with pts 96111366 because it's too old (diff : 431402). video_out: throwing away image with pts 96114366 because it's too old (diff : 428402). video_out: throwing away image with pts 96117366 because it's too old (diff : 425402). video_out: throwing away image with pts 96120366 because it's too old (diff : 422402). video_out: throwing away image with pts
Re: [vdr] VDR 1.7.0 + xine plugin 0.8.2 - several iisues
Hi, Igor Nikanov schrieb: But if I disconnect from the card the antenna I will have this problem [snip] Apr 27 13:37:32 localhost vdr: [5732] timer 1 (88 1318-1618 '@Das gemütliche Schlafzimmer') set to event Sun 27.04.2008 14:0 Apr 27 13:37:32 localhost vdr: [5732] switching device 1 to channel 88 Apr 27 13:37:32 localhost vdr: [5732] timer 1 (88 1318-1618 '@Das gemütliche Schlafzimmer') start Apr 27 13:37:32 localhost vdr: [5732] Title: 'Das gemütliche Schlafzimmer' Subtitle: '(null)' Apr 27 13:37:32 localhost vdr: [5732] record /video/@Das_gemütliche_Schlafzimmer/2008-04-27.13.18.50.99.rec Apr 27 13:37:32 localhost vdr: [5732] recording to'/video/@Das_gemütliche_Schlafzimmer/2008-04-27.13.18.50.99.rec/003.vdr' [snip] Apr 27 13:38:03 localhost vdr: [5746] ERROR: video data stream broken Apr 27 13:38:03 localhost vdr:[5746] initiating emergency exit Apr 27 13:38:03 localhost vdr: [5732] emergency exit requested - shuttingdown [snip] Apr 27 13:38:06 localhost vdr: [5732] exiting, exit code 1 Apr 27 13:38:06 localhost vdr: [5732] emergency exit! When there is a recording going on and no more data comes in (due to the disconnected antenna cable), then VDR assumes a buggy driver/card, requests an emergency exit which will then reload the driver. In the case where this doesn't fix the problem (i. e. it won't help if you disconnected the antenna cable), VDR will continue to record but still sees no data. The result is, it will again request an emergency exit. This scenario will go on until either the timer(s) get(s) outdated or the signal comes back (by having someone connect the antenna cable again). There has been a discussion regarding pro and cons of emergency exit and the result is that at least from VDR-1.5.18 on you can disable this feature in VDR's setup/miscellaneous menu. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 + xine plugin 0.8.2 - several iisues
Hi, Igor Nikanov schrieb: But if I disconnect from the card the antenna I will have this problem [snip] let's see in the xine output [snip] video_out: throwing away image with pts 96108366 because it's too old (diff : 434402). video_out: throwing away image with pts 96111366 because it's too old (diff : 431402). video_out: throwing away image with pts 96114366 because it's too old (diff : 428402). video_out: throwing away image with pts 96117366 because it's too old (diff : 425402). video_out: throwing away image with pts 96120366 because it's too old (diff : 422402). video_out: throwing away image with pts 96123366 because it's too old (diff : 419402). video_out: throwing away image with pts 96126366 because it's too old (diff : 416402). video_out: throwing away image with pts 96129366 because it's too old (diff : 413402). video_out: throwing away image with pts 96132366 because it's too old (diff : 410402). video_out: throwing away image with pts 96135366 because it's too old (diff : 407402). video_out: throwing away image with pts 96138366 because it's too old (diff : 404402). video_out: throwing away image with pts 96141366 because it's too old (diff : 401531). video_out: throwing away image with pts 96144366 because it's too old (diff : 398630). video_out: throwing away image with pts 96147366 because it's too old (diff : 395630). When you disconnect the antenna cable for a certain amount of time, there will be a gap in presentation time stamps (PTS). This will cause xine to jump over the gap with the result that the previously established buffer will run empty immediately. Any further received images will therefore arrive to late at xine and cause the above messages. Maybe I can find a solution for vdr-xine to detect this issue and reestablish a suitable buffer in this case. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr 1.7.0 channell's scan
Hi how is it possible to scan dvb-s/s2 channels with vdr 1.7.0 ? Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.0 channell's scan
Hi, Igor Nikanov schrieb: how is it possible to scan dvb-s/s2 channels with vdr 1.7.0 ? Well, there is no explicit scan functionality. When VDR receives a channel (for example when it does an EPG scan for all already known transponders (generated from channels.conf)) and sees a network information table (NIT), it will analyze it and add new channels to channels.conf, when it is allowed to do so. See VDR's setup / dvb menu, update channels = add new transponders. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR 1.7.0
Hi when I want to switch on dvb-s2 channels ( Apr 28 09:18:32 localhost vdr: [4188] switching to channel 2782 Apr 28 09:18:32 localhost vdr: [4535] transfer thread ended (pid=4188, tid=4535) Apr 28 09:18:32 localhost vdr: [4188] buffer stats: 0 (0%) used Apr 28 09:18:32 localhost vdr: [4756] transfer thread started (pid=4188, tid=4756) Apr 28 09:18:32 localhost vdr: [4537] TS buffer on device 1 thread ended (pid=4188, tid=4537) Apr 28 09:18:32 localhost vdr: [4536] buffer stats: 0 (0%) used Apr 28 09:18:32 localhost vdr: [4536] receiver on device 1 thread ended (pid=4188, tid=4536) Apr 28 09:18:32 localhost vdr: [4757] receiver on device 1 thread started (pid=4188, tid=4757) Apr 28 09:18:32 localhost vdr: [4758] TS buffer on device 1 thread started (pid=4188, tid=4758) Apr 28 09:18:40 localhost vdr: [4197] frontend 0 timed out while tuning to channel 2782, tp 111914 Apr 28 09:18:40 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:18:40 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:18:50 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:18:50 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:00 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:00 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:10 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:10 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:20 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:20 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:30 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:30 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:41 localhost vdr: [4197] frontend 0 timed out while tuning to channel 2782, tp 111914 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR 1.7.0 ERROR (dvbdevice.c,302): Invalid argument
Hi when I want to switch on dvb-s2 channel ASTRA HD+;BetaDigital:11914:hC910I1M2O35S1:S19.2E:27500:1279:0;1283=deu:0:0:131:133:6:0 I receive this error Apr 28 09:18:32 localhost vdr: [4188] switching to channel 2782 Apr 28 09:18:32 localhost vdr: [4535] transfer thread ended (pid=4188, tid=4535) Apr 28 09:18:32 localhost vdr: [4188] buffer stats: 0 (0%) used Apr 28 09:18:32 localhost vdr: [4756] transfer thread started (pid=4188, tid=4756) Apr 28 09:18:32 localhost vdr: [4537] TS buffer on device 1 thread ended (pid=4188, tid=4537) Apr 28 09:18:32 localhost vdr: [4536] buffer stats: 0 (0%) used Apr 28 09:18:32 localhost vdr: [4536] receiver on device 1 thread ended (pid=4188, tid=4536) Apr 28 09:18:32 localhost vdr: [4757] receiver on device 1 thread started (pid=4188, tid=4757) Apr 28 09:18:32 localhost vdr: [4758] TS buffer on device 1 thread started (pid=4188, tid=4758) Apr 28 09:18:40 localhost vdr: [4197] frontend 0 timed out while tuning to channel 2782, tp 111914 Apr 28 09:18:40 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:18:40 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:18:50 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:18:50 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:00 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:00 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:10 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:10 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:20 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:20 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:30 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:30 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:41 localhost vdr: [4197] frontend 0 timed out while tuning to channel 2782, tp 111914 in attachment you can find my dvbdevice.c Igor dvbdevice.c.bz2 Description: BZip2 compressed data ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.0 does not compile
Hi dvbdevice.c dvbdevice.c: In member function 'bool cDvbTuner::SetFrontend()': dvbdevice.c:271: error: 'struct dvbfe_info' has no member named 'delivery' dvbdevice.c:286: error: 'struct dvbfe_info' has no member named 'delivery' dvbdevice.c:307: error: 'struct dvbfe_info' has no member named 'delivery' make: *** [dvbdevice.o] Error 1 The driver I am using ist http://jusst.de/hg/multiproto svn from today, and the included frontend.h really has no delivery member in this structure. delivery was removed 5 weeks ago: http://jusst.de/hg/multiproto/log/46df93f7bcee/linux/include/linux/dvb/frontend.h -- Helmut Auer, [EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.0 does not compile
On 04/13/08 18:21, Helmut Auer wrote: Hi dvbdevice.c dvbdevice.c: In member function 'bool cDvbTuner::SetFrontend()': dvbdevice.c:271: error: 'struct dvbfe_info' has no member named 'delivery' dvbdevice.c:286: error: 'struct dvbfe_info' has no member named 'delivery' dvbdevice.c:307: error: 'struct dvbfe_info' has no member named 'delivery' make: *** [dvbdevice.o] Error 1 The driver I am using ist http://jusst.de/hg/multiproto svn from today, and the included frontend.h really has no delivery member in this structure. delivery was removed 5 weeks ago: http://jusst.de/hg/multiproto/log/46df93f7bcee/linux/include/linux/dvb/frontend.h I used the same driver as in VDR version 1.5.14 (dated 2008-01-28). I tried to make today's driver from http://jusst.de/hg/multiproto, mixed with Oliver's full-ts mod stuff, but that didn't compile. So I just used what had worked with version 1.5.14. Let's hope there will soon be a combined driver source... Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.0 does not compile
Let's hope there will soon be a combined driver source... I guess the driver team cannot ignore the linux killer application :) -- Helmut Auer, [EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.0 does not compile
Hi,
Helmut Auer schrieb:
dvbdevice.c
dvbdevice.c: In member function 'bool cDvbTuner::SetFrontend()':
dvbdevice.c:271: error: 'struct dvbfe_info' has no member named 'delivery'
dvbdevice.c:286: error: 'struct dvbfe_info' has no member named 'delivery'
dvbdevice.c:307: error: 'struct dvbfe_info' has no member named 'delivery'
make: *** [dvbdevice.o] Error 1
The driver I am using ist http://jusst.de/hg/multiproto svn from today,
and the included frontend.h really has no delivery member in this structure.
delivery was removed 5 weeks ago:
http://jusst.de/hg/multiproto/log/46df93f7bcee/linux/include/linux/dvb/frontend.h
The attached patch should make it build.
Bye.
--
Dipl.-Inform. (FH) Reinhard Nissl
mailto:[EMAIL PROTECTED]
diff -Nurp ../vdr-1.7.0-orig/dvbdevice.c ./dvbdevice.c
--- ../vdr-1.7.0-orig/dvbdevice.c 2008-04-13 16:15:35.0 +0200
+++ ./dvbdevice.c 2008-04-13 21:16:45.0 +0200
@@ -266,10 +266,6 @@ bool cDvbTuner::SetFrontend(void)
tuneTimeout = DVBS_TUNE_TIMEOUT;
lockTimeout = DVBS_LOCK_TIMEOUT;
-
- dvbfe_info feinfo;
- feinfo.delivery = Frontend.delivery;
- CHECK(ioctl(fd_frontend, DVBFE_GET_INFO, feinfo)); //switch system
}
else if (frontendType DVBFE_DELSYS_DVBC) {
Frontend.delivery = DVBFE_DELSYS_DVBC;
@@ -281,10 +277,6 @@ bool cDvbTuner::SetFrontend(void)
tuneTimeout = DVBC_TUNE_TIMEOUT;
lockTimeout = DVBC_LOCK_TIMEOUT;
-
- dvbfe_info feinfo;
- feinfo.delivery = Frontend.delivery;
- CHECK(ioctl(fd_frontend, DVBFE_GET_INFO, feinfo)); //switch system
}
else if (frontendType DVBFE_DELSYS_DVBT) {
Frontend.delivery = DVBFE_DELSYS_DVBT;
@@ -302,15 +294,12 @@ bool cDvbTuner::SetFrontend(void)
tuneTimeout = DVBT_TUNE_TIMEOUT;
lockTimeout = DVBT_LOCK_TIMEOUT;
-
- dvbfe_info feinfo;
- feinfo.delivery = Frontend.delivery;
- CHECK(ioctl(fd_frontend, DVBFE_GET_INFO, feinfo)); //switch system
}
else {
esyslog(ERROR: attempt to set channel with unknown DVB frontend type);
return false;
}
+ CHECK(ioctl(fd_frontend, DVBFE_SET_DELSYS, Frontend.delivery)); //switch system
if (ioctl(fd_frontend, DVBFE_SET_PARAMS, Frontend) 0) {
esyslog(ERROR: frontend %d: %m, cardIndex);
return false;
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.0 - when ?
On 02/19/08 13:05, Igor wrote: sorry , I meant - when will be release the vdr 1.7.0 Shortly after 1.6.0. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
