Hi,
I have two cards in my video server:
Technotrend/Hauppauge WinTV Nexus-S rev2.3) Hauppauge Nova-S-Plus DVB-S [card=37]
lspci:
01:0c.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05) 01:0c.1 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05) 01:0c.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05) 01:0c.4 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [IR Port] (rev 05) 01:0f.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
when I use szap to change the channel, I can switch, record, switch, record .... (record with "cat /dev/dvb/adapter1/dvr0 >/tmp/tsvideo".
But when I try to record with vdr, I get the following errors and nothing will be record: (with plain vdr-1.5.0 and plain vdr-1.4.0 and v4l-dvb from yesterdays hg):
Feb 9 12:02:00 video vdr: [30529] connect from 127.0.0.1, port 60607 - accepted Feb 9 12:02:00 video vdr: [30529] timer 10 (1 1200-1215 VPS 'Tagesschau um zwölf') added Feb 9 12:02:00 video vdr: [30529] closing SVDRP connection Feb 9 12:02:00 video vdr: [30529] switching device 2 to channel 1 Feb 9 12:02:00 video vdr: [30529] timer 10 (1 1200-1215 VPS 'Tagesschau um zwölf') start Feb 9 12:02:00 video vdr: [30529] Title: 'Tagesschau um zwölf' Subtitle: '' Feb 9 12:02:00 video vdr: [30529] record /data/nobackup/video/Tagesschau_um_zwölf/2007-02-09.12.00.50.50.rec Feb 9 12:02:00 video vdr: [30529] creating directory /data/nobackup/video/Tagesschau_um_zwölf Feb 9 12:02:01 video vdr: [30529] creating directory /data/nobackup/video/Tagesschau_um_zwölf/2007-02-09.12.00.50.50.rec Feb 9 12:02:01 video vdr: [30529] recording to '/data/nobackup/video/Tagesschau_um_zwölf/2007-02-09.12.00.50.50.rec/001.vdr' Feb 9 12:02:01 video vdr: [30529] connect from 127.0.0.1, port 60610 - accepted Feb 9 12:02:01 video vdr: [30529] closing SVDRP connection Feb 9 12:02:01 video vdr: [30603] file writer thread started (pid=30529, tid=30603) Feb 9 12:02:01 video vdr: [30604] recording thread started (pid=30529, tid=30604) Feb 9 12:02:01 video vdr: [30605] receiver on device 2 thread started (pid=30529, tid=30605) Feb 9 12:02:01 video vdr: [30606] TS buffer on device 2 thread started (pid=30529, tid=30606) Feb 9 12:02:03 video vdr: [30529] timer 10 (1 1200-1215 VPS 'Tagesschau um zwölf') set to event Fre 09.02.2007 12:00-12:15 (VPS: 09.02 12: 00) 'Tagesschau um zwölf' Feb 9 12:02:09 video vdr: [30537] frontend 1 timed out while tuning to channel 1, tp 111836 Feb 9 12:02:10 video vdr: [30529] connect from 127.0.0.1, port 60614 - accepted Feb 9 12:02:10 video vdr: [30529] closing SVDRP connection Feb 9 12:02:10 video vdr: [30529] connect from 127.0.0.1, port 60617 - accepted Feb 9 12:02:10 video vdr: [30529] closing SVDRP connection Feb 9 12:02:27 video vdr: [30529] connect from 127.0.0.1, port 60622 - accepted Feb 9 12:02:27 video vdr: [30529] closing SVDRP connection Feb 9 12:02:32 video vdr: [30603] ERROR: video data stream broken Feb 9 12:02:32 video vdr: [30603] initiating emergency exit Feb 9 12:02:32 video vdr: [30529] emergency exit requested - shutting down Feb 9 12:02:32 video vdr: [30604] recording thread ended (pid=30529, tid=30604) Feb 9 12:02:32 video vdr: [30603] file writer thread ended (pid=30529, tid=30603) Feb 9 12:02:32 video vdr: [30529] buffer stats: 0 (0%) used Feb 9 12:02:32 video vdr: [30529] timer 10 (1 1200-1215 VPS 'Tagesschau um zwölf') stop Feb 9 12:02:32 video vdr: [30529] saved setup to /etc/vdr/setup.conf Feb 9 12:02:32 video vdr: [30534] tuner on device 1 thread ended (pid=30529, tid=30534) Feb 9 12:02:33 video vdr: [30606] TS buffer on device 2 thread ended (pid=30529, tid=30606) Feb 9 12:02:33 video vdr: [30605] buffer stats: 0 (0%) used Feb 9 12:02:33 video vdr: [30605] receiver on device 2 thread ended (pid=30529, tid=30605) Feb 9 12:02:33 video vdr: [30533] CI adapter on device 0 thread ended (pid=30529, tid=30533) Feb 9 12:02:33 video vdr: [30535] section handler thread ended (pid=30529, tid=30535) Feb 9 12:02:34 video vdr: [30537] tuner on device 2 thread ended (pid=30529, tid=30537) Feb 9 12:02:34 video vdr: [30538] section handler thread ended (pid=30529, tid=30538) Feb 9 12:02:36 video vdr: [30529] ===================== Feb 9 12:02:36 video vdr: [30529] EPG bugfix statistics Feb 9 12:02:36 video vdr: [30529] ===================== Feb 9 12:02:36 video vdr: [30529] IF SOMEBODY WHO IS IN CHARGE OF THE EPG DATA FOR ONE OF THE LISTED Feb 9 12:02:36 video vdr: [30529] CHANNELS READS THIS: PLEASE TAKE A LOOK AT THE FUNCTION cEvent::FixEpgBugs() Feb 9 12:02:36 video vdr: [30529] IN VDR/epg.c TO LEARN WHAT'S WRONG WITH YOUR DATA, AND FIX IT! Feb 9 12:02:36 video vdr: [30529] ===================== Feb 9 12:02:36 video vdr: [30529] Fix Hits Channels Feb 9 12:02:36 video vdr: [30529] 3 15 Dok&Deb, hr-fernsehen, KiKa Feb 9 12:02:36 video vdr: [30529] 4 5 SWR2, SWR2, 3sat Feb 9 12:02:36 video vdr: [30529] 6 418 MDR SACHSEN, hr-fernsehen, WDR Köln, Bayerisches FS, Das Erste, Phoenix, arte, ... Feb 9 12:02:36 video vdr: [30529] ===================== Feb 9 12:02:36 video vdr: [30529] exiting Feb 9 12:02:36 video vdr: [30529] emergency exit!
so why can I get ts streams from the second dvb card and vdr doesn't get any bytes ?
Hi,
with strace I can see, that vdr tries to open video0 and audio0, which aren't there. Do they have to exist for "nova" cards ?
video:/var/service/vdr # grep adapter1 /tmp/vdr-1.5.0.strace access("/dev/dvb/adapter1/frontend0", F_OK) = 0 open("/dev/dvb/adapter1/frontend0", O_RDONLY) = 10 open("/dev/dvb/adapter1/frontend0", O_RDWR|O_NONBLOCK) = 10 open("/dev/dvb/adapter1/osd0", O_RDWR) = -1 ENOENT (No such file or directory) open("/dev/dvb/adapter1/video0", O_RDWR|O_NONBLOCK) = -1 ENOENT (No such file or directory) open("/dev/dvb/adapter1/audio0", O_RDWR|O_NONBLOCK) = -1 ENOENT (No such file or directory) open("/dev/dvb/adapter1/demux0", O_RDWR) = 11 open("/dev/dvb/adapter1/ca0", O_RDWR) = -1 ENOENT (No such file or directory) open("/dev/dvb/adapter1/demux0", O_RDWR|O_NONBLOCK) = 26 open("/dev/dvb/adapter1/demux0", O_RDWR|O_NONBLOCK) = 27 open("/dev/dvb/adapter1/demux0", O_RDWR|O_NONBLOCK) = 28 video:/var/service/vdr #
On Fri, Feb 09, Dieter Bloms wrote:
Hi,
Dieter Bloms wrote:
As you can see from the above lines, tuning fails for device 2 (= frontend 1) as VDR reports a timeout about 10 seconds after switching to this channel. VDR retries tuning in that case, but further reports are suppressed for the next 60 seconds so you don't see a second timeout report.
Finally, after 30 seconds, the recording thread issues an emergency exit as it didn't see any data (=> video data stream broken) as the device was not able to tune to the channel.
Is your DiSEqC setup correct (in case you are using DiSEqC)?
Bye.
Hi,
On Sat, Feb 10, Reinhard Nissl wrote:
I don't have a diseqc setup, I have a twin lnb and both dvb cards are connected directly.
It worked in the past, ok many timeouts, but after reloading the driver and restart of vdr it worked.
I was amazed that vdr can not tune to a channel and szap can do it without reloading the driver !
Maybe they use differnt methods to switch the channels.
Hi,
Dieter Bloms wrote:
szap always sends DiSEqC commands, so I'd suggest to use VDR's diseqc.conf. It's default section "Full DiSEqC sequence" is identical to the tuning sequence that szap uses.
You may want to try the attached szap and VDR patch. You'll then get some output while tuning.
Bye.
Hi,
On Sat, Feb 10, Reinhard Nissl wrote:
doesn't my driver or card support diseqc ?
--snip video:/tmp/szap # szap -a 1 -p -i reading channels from file '/root/.szap/channels.conf'
RTL Television,RTL;RTL World
zapping to 5 'RTL Television,RTL;RTL World': sat 0, frequency = 12187 MHz H, symbolrate 27500000, vpid = 0x00a3, apid = 0x0068 sid = 0x0069 using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' FE_DISEQC_SEND_MASTER_CMD failed: Unknown error 524 FE_DISEQC_SEND_BURST failed: Operation not supported couldn't find pmt-pid for sid 0069 status 1f | signal f700 | snr ffdc | ber 00000000 | unc 00000000 | FE_HAS_LOCK
SAT.1;ProSiebenSat.1
zapping to 6 'SAT.1;ProSiebenSat.1': sat 0, frequency = 12480 MHz V, symbolrate 27500000, vpid = 0x06ff, apid = 0x0700 sid = 0x0022 FE_DISEQC_SEND_MASTER_CMD failed: Unknown error 524 FE_DISEQC_SEND_BURST failed: Operation not supported couldn't find pmt-pid for sid 0022 status 1f | signal fb00 | snr ffdc | ber 00000000 | unc 00000000 | FE_HAS_LOCK --snip--
Hi,
Dieter Bloms wrote:
Don't know. But have you tried DiSEqC with VDR (menu Settings - LNB)?
You might get similar messages but on the other hand, it might work ;-)
Bye.
Hi,
On Sat, Feb 10, Reinhard Nissl wrote:
Don't know. But have you tried DiSEqC with VDR (menu Settings - LNB)?
no, because I didn't install any diseqc switches. I had also an empty diseqc.conf
You might get similar messages but on the other hand, it might work ;-)
ok, now I have installed the default diseqc.conf and activate diseqc in vdr setup menu. After a shutdown (and turn off the computer for about 10 seconds) the second card works, even with these two errors:
t: 1171143367,692, c: 0, r: 0, a: ============================================== t: 1171143387,098, c: 1, r: 0, a: ---------------------------------------------- t: 1171143387,099, c: 1, r: 0, a: ioctl(fd_frontend, FE_SET_TONE, SEC_TONE_OFF) t: 1171143387,100, c: 1, r: 0, a: ioctl(fd_frontend, FE_SET_VOLTAGE, SEC_VOLTAGE_13) t: 1171143387,118, c: 1, r: -1, a: ioctl(fd_frontend, FE_DISEQC_SEND_MASTER_CMD, &cmd) t: 1171143387,138, c: 1, r: -1, a: ioctl(fd_frontend, FE_DISEQC_SEND_BURST, SEC_MINI_A) t: 1171143387,158, c: 1, r: 0, a: ioctl(fd_frontend, FE_SET_TONE, SEC_TONE_ON) t: 1171143387,160, c: 1, r: 0, a: ioctl(fd_frontend, FE_SET_FRONTEND, &Frontend) t: 1171143387,288, c: 1, r: 0, a: ==============================================
Either the power off has resolved the error or activating diseqc. but now if I deactivate diseqc the cards work, too .
Very strange.
Thank you very much for your help, for the future I will activate diseqc.
Hi,
Dieter Bloms wrote:
Well, I've just had a further look into the tuning code of VDR. With DiSEqC disabled, VDR simply executes the commands FE_SET_VOLTAGE, FE_SET_TONE and FE_SET_FRONTEND without any extra delay between these ioctl() calls.
I'd like you to do some further tests by modifying diseqc.conf:
A) let's remove FE_DISEQC_SEND_MASTER_CMD and FE_DISEQC_SEND_BURST
S19.2E 11700 V 9750 t v W15 W15 W15 t S19.2E 99999 V 10600 t v W15 W15 W15 T S19.2E 11700 H 9750 t V W15 W15 W15 t S19.2E 99999 H 10600 t V W15 W15 W15 T
B) let's reduce the time to wait
S19.2E 11700 V 9750 t v W15 t S19.2E 99999 V 10600 t v W15 T S19.2E 11700 H 9750 t V W15 t S19.2E 99999 H 10600 t V W15 T
C) omit the time to wait
S19.2E 11700 V 9750 t v t S19.2E 99999 V 10600 t v T S19.2E 11700 H 9750 t V t S19.2E 99999 H 10600 t V T
D) omit the initial FE_SET_TONE
S19.2E 11700 V 9750 v t S19.2E 99999 V 10600 v T S19.2E 11700 H 9750 V t S19.2E 99999 H 10600 V T
Test D) is identical to disabling DiSEqC in VDR's setup menu.
I assume that either B) or C) will be the shortest sequence that still works in your case.
Bye.
Hi Reinhard,
On Sun, Feb 11, Reinhard Nissl wrote:
I'd like you to do some further tests by modifying diseqc.conf:
I will do each setup for about 1 week and will see, if I miss some recordings and let you about the results.
I will begin with A .... to get a stables setup first, because it is not so depressing ;)
Hi,
On Sun, Feb 11, Dieter Bloms wrote:
no diseqc setup works stabel for me :( Also the Full DiSEqC sequence from default diseqc.conf doesn't work a few hours after reboot and sometime it doesn't work directly after reboot. But I can switch the channel with szap and get the TS stream from /dev/dvb/adapter1/dvr0 every time, even vdr can't record I only stop vdr and do not a reload of the driver.
I did some tests with szap:
o I can only get the TS stream with the default lnb type or -l UNIVERSAL o if I use another lnb type like ENHANCED, I can switch, but don't get any data. o The ioctls are the same if I use diseqc with vdr, but as I said before, I didn't get any data a few hours after reboot of the system, and sometime I didn't get any data directly after reboot. o If I use szap, I can switch the channels and get the ts stream every time (via cat /dev/dvb/adapter1/dvr0 > /tmp/bla). o the first status is 01 and it has no lock all others are 1f and it has a lock (as seen below). o when I call szap the second time (with the same channel) the first status is 01 and then 1f, too. o maybe vdr does have to wait a longer time ?
What lnb type vdr is using, when I enable diseqc in vdr menu ? I can't configure any frequenz after activate diseqc.
Here the output from your patched szap:
video:/tmp/szap # ./szap -l UNIVERSAL -a 1 -r -c /etc/vdr/channels.conf -n 2 reading channels from file '/etc/vdr/channels.conf' zapping to 2 'Das Erste;ARD': sat 0, frequency = 11836 MHz H, symbolrate 27500000, vpid = 0x0065, apid = 0x0066 sid = 0x0068 using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' t: 1171518269.386, c: 1, r: 0, a: ---------------------------------------------- t: 1171518269.386, c: 1, r: 0, a: ioctl(fd, FE_SET_TONE, SEC_TONE_OFF) t: 1171518269.389, c: 1, r: 0, a: ioctl(fd, FE_SET_VOLTAGE, v) (v = SEC_VOLTAGE_18) t: 1171518269.408, c: 1, r: 0, a: ioctl(fd, FE_DISEQC_SEND_MASTER_CMD, &cmd->cmd) t: 1171518269.576, c: 1, r: 0, a: ioctl(fd, FE_DISEQC_SEND_BURST, b) (b = SEC_MINI_A) t: 1171518269.700, c: 1, r: 0, a: ioctl(fd, FE_SET_TONE, t) (t = SEC_TONE_ON) t: 1171518269.702, c: 1, r: 0, a: ioctl(fefd, FE_SET_FRONTEND, &tuneto) status 01 | signal f700 | snr e330 | ber 00000000 | unc fffffffe | status 1f | signal f700 | snr f866 | ber 00000000 | unc fffffffe | FE_HAS_LOCK status 1f | signal f700 | snr f8ea | ber 00000000 | unc fffffffe | FE_HAS_LOCK status 1f | signal f700 | snr f8cd | ber 00000000 | unc fffffffe | FE_HAS_LOCK status 1f | signal f700 | snr f8aa | ber 00000000 | unc fffffffe | FE_HAS_LOCK status 1f | signal f700 | snr f887 | ber 00000000 | unc fffffffe | FE_HAS_LOCK status 1f | signal f700 | snr f8a4 | ber 00000000 | unc fffffffe | FE_HAS_LOCK status 1f | signal f700 | snr f93c | ber 00000000 | unc fffffffe | FE_HAS_LOCK status 1f | signal f700 | snr f8ad | ber 00000000 | unc fffffffe | FE_HAS_LOCK status 1f | signal f700 | snr f8a9 | ber 00000000 | unc fffffffe | FE_HAS_LOCK status 1f | signal f700 | snr f93f | ber 00000000 | unc fffffffe | FE_HAS_LOCK status 1f | signal f700 | snr f88a | ber 00000000 | unc fffffffe | FE_HAS_LOCK status 1f | signal f700 | snr f8e8 | ber 00000000 | unc fffffffe | FE_HAS_LOCK status 1f | signal f700 | snr f81b | ber 00000000 | unc fffffffe | FE_HAS_LOCK status 1f | signal f700 | snr f911 | ber 00000000 | unc fffffffe | FE_HAS_LOCK
Hi,
On Thu, Feb 15, Dieter Bloms wrote:
I can reproduce following:
vdr can record from senders on V polarisation like sat1, prosieben ... even without reloading the driver. vdr can not record from any sender on H polarisation like ard, zdf ... even with reloading the driver it doesn't work. This explains, that I got some recording and some not.
Does anybody know what can be the different between H and V polarisation ?
On Friday 16 February 2007 13:48, Dieter Bloms wrote:
Hi,
supply voltage at central wire of koax cable. It seems you have or DVB card or LNB damaged. Test these parts with another receiver or/and another LNB.
Hi,
On Fri, Feb 16, bastlir wrote:
my primary dvb card works fine on both of my Twin-LNB connectors. I can switch the second card via szap and get a video stream via "cat /dev/dvb/adapter1/dvr0 > /tmp/bla" on H and V channels. VDR doesn't get data any data from H channels, but gets data from V channels. I will try to strace vdr and szap to get any difference, maybe they do it in a different way.
Hi,
Dieter Bloms wrote:
I've had a further look into szap's source how it detects the status FE_LOCKED. Attached is an updated tuner patch which now also reports details for FE_READ_STATUS.
One difference between VDR and szap regarding FE_READ_STATUS is, that VDR only honors the read status when ioctl() returns 0 while szap prints just an error when ioctl() returns -1.
Furthermore, VDR's handling of errno == EINTR seems to be wrong due to the do {} while (0); loop.
BTW: I still assume, that your logfile reports a tuning timeout. If this is no longer the case, then you may want to experiment with WAIT_FOR_TUNER_LOCK in device.c.
Bye.
Hi,
I will ike accentuate the do {}while(0) behavior. I've seen this in few projects including VDR and at least one plugin (xineliboutput) In a code like: do {
if (condition1) continue; } while(condition2); continue does not translate to a jump to "do", but to a jump to "while" where the condition2 is evaluated.
do { if (condition1) continue; } while(0);
if equivalent with: do { if (condition1) break; } while (0);
Regards, Ilariu On 2/18/07, Reinhard Nissl rnissl@gmx.de wrote:
Hello Reinhard,
On Sun, Feb 18, Reinhard Nissl wrote:
I've tried your patch and the new vdr-1.4.5-2 for some days now and it works even when I disable diseqc ! So I have to say: greate work Reinhard and many many thanks to you !!!
Hi,
Dieter Bloms wrote:
Would you mind posting some of the new log lines which the last patch added? It would be good to prove my assumptions ;-)
BTW: vdr-1.5.1 uses a further "developed" loop (in regard the the last patch) which is much closer to what szap does. The relevant part of dvbdevice.c looks like that:
while (1) { if (ioctl(fd_frontend, FE_READ_STATUS, &Status) != -1) return true; if (errno != EINTR) break; } return false;
Bye.
-
bastlir -
Dieter Bloms -
Ilariu Raducan -
Reinhard Nissl