Hello
Yesterday i set EGP timeout to 1 in the hope the LNBsharing patch will prevent the usual deadlocks. It does not need to do anything.
It happens too that the box ran that hour without any recordings instead of being powered off as usual, so EPG scan could really start. (Hm, why 1h as minimum?)
As you may se below, "Starting EPG scan" starts at channel 0 (zero? What is channel 0?), switches to channel 1, that's Ok... got new transponders/programs, that's OK. (so many new to day?) then VDR switches to channel 279! Why 279 and not 2? What's that?
The next timer event would be a timer to record channel 27 at 10:52 but the switch attempt occurs at 10:42:18 and obviuosly leads VDR into a deep endless loop.
channel 279 is OLD GOLD;PREMIERE:11720:hC34:S19.2E:27500:0:336=deu:0:1801,1722,1702:167:133:3:0
Never ever tuned to 279 (encrypted) channel, no timer except the one in approx 10 minutes at channel 27 ( an ASCII buffer Bug? *27*9?)
09:09:08 [8593]: info: Channel locked by LNB! 09:09:58 [8600]: changing name of channel 312 from 'D 4 - 07:45,;' to 'D 4 - 09:30,;' 09:09:58 [8600]: linking channel 118 from 305 308 304 415 310 313 312 311 309 to 305 308 304 415 310 313 311 312 309 ... 09:40:48 [8593]: Power button pressed 09:40:48 [8593]: next timer event at Mon Jun 6 10:52:00 2005 09:40:48 [8593]: confirm: Press any key to cancel shutdown 09:40:54 [8593]: confirmed ... 10:00:57 [8593]: next timer event at Mon Jun 6 10:52:00 2005 ... 10:40:37 [8597]: changing pids of channel 160 from 901+901:902:204 to 701+701:702:204 10:41:34 [8593]: info: Starting EPG scan 10:41:36 [8593]: switching to channel 0 10:41:36 [22711]: TS buffer on device 1 thread ended (pid=22711, tid=2752525) 10:41:36 [22710]: buffer stats: 4136 (0%) used 10:41:36 [22710]: receiver on device 1 thread ended (pid=22710, tid=2736140) 10:41:36 [8593]: buffer stats: 0 (0%) used 10:41:37 [8603]: changing pids of channel 636 from 0+0:0:0 to 32+32:33:0 10:41:37 [8603]: changing pids of channel 637 from 0+0:0:0 to 70+70:71:54 10:41:38 [8603]: changing pids of channel 638 from 0+0:0:0 to 0+0:73:0 10:41:38 [8603]: changing pids of channel 639 from 0+0:0:0 to 61+61:62:0 10:41:41 [8603]: changing pids of channel 646 from 0+0:0:0 to 41+41:40:0 10:41:42 [8603]: changing pids of channel 647 from 0+0:0:0 to 0+0:58=eng:0 10:41:42 [8603]: changing pids of channel 648 from 0+0:0:0 to 0+0:59:0 10:42:00 [8600]: creating new channel 'TVP Kultura,;TVP' on S19.2E transponder 110861 with id 1-1059-7101-0 10:42:00 [8600]: creating new channel 'TV Polonia,;TVP Service' on S19.2E transponder 110861 with id 1-1059-7100-0 10:42:00 [8600]: changing pids of channel 814 from 0+0:0:0 to 516+8190:690=pol:580 10:42:00 [8600]: changing pids of channel 815 from 0+0:0:0 to 514+8190:670=pol:578 10:42:02 [8603]: creating new channel 'Cartoon Network/TCM,Cartoon Network/TCM;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20341-0 10:42:02 [8603]: creating new channel 'Boomerang,Boomerang;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20343-0 10:42:02 [8603]: creating new channel 'Viasat Explorer,Viasat Explorer;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20344-0 10:42:02 [8603]: creating new channel 'Viasat History,Viasat History;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20345-0 10:42:02 [8603]: creating new channel 'AXN,AXN;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20346-0 10:42:02 [8603]: creating new channel 'Cinemax,Cinemax;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20347-0 10:42:02 [8603]: creating new channel 'Minimax/A+,Minimax/A+;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20348-0 10:42:02 [8603]: creating new channel 'CT1,CT1;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20342-0 10:42:02 [8603]: creating new channel 'CT2,CT2;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20350-0 10:42:02 [8603]: creating new channel 'Film+,Film+;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20349-0 10:42:02 [8603]: changing pids of channel 818 from 0+0:0:0 to 251+251:260=hun,261=cze:270 10:42:02 [8603]: changing caids of channel 818 from 0 to D02 10:42:02 [8603]: changing pids of channel 819 from 0+0:0:0 to 301+301:310=hun,311=cze:320 10:42:02 [8603]: changing caids of channel 819 from 0 to D02 10:42:02 [8603]: changing pids of channel 820 from 0+0:0:0 to 351+351:360=hun,361=cze,362=eng:370 10:42:02 [8603]: changing caids of channel 820 from 0 to D02 10:42:03 [8603]: changing pids of channel 821 from 0+0:0:0 to 401+401:410=hun,411=cze,412=eng:0 10:42:03 [8603]: changing caids of channel 821 from 0 to D02 10:42:03 [8603]: changing caids of channel 821 from 0 to D02 10:42:03 [8603]: changing pids of channel 822 from 0+0:0:0 to 451+451:460=hun:0 10:42:03 [8603]: changing caids of channel 822 from 0 to D02 10:42:03 [8603]: changing pids of channel 825 from 0+0:0:0 to 501+501:511=cze:0 10:42:03 [8603]: changing caids of channel 825 from 0 to D02 10:42:03 [8603]: changing pids of channel 824 from 0+0:0:0 to 551+551:561=cze:570 10:42:03 [8603]: changing caids of channel 824 from 0 to D02 10:42:04 [8603]: changing pids of channel 816 from 0+0:0:0 to 101+101:110=hun,112=eng:120 10:42:04 [8603]: changing caids of channel 816 from 0 to D02 10:42:04 [8603]: changing pids of channel 823 from 0+0:0:0 to 151+151:161=cze:170 10:42:04 [8603]: changing caids of channel 823 from 0 to D02 10:42:04 [8603]: changing pids of channel 817 from 0+0:0:0 to 201+201:210=hun,212=eng,213=pol:0 10:42:04 [8603]: changing caids of channel 817 from 0 to D02 10:42:18 [8593]: switching to channel 279 10:42:18 [8593]: info: Channel not available! 10:42:20 [8593]: switching to channel 279 10:44:20 [8593]: info: Channel not available! 10:44:22 [8593]: switching to channel 279 10:44:22 [8593]: info: Channel not available! 10:44:24 [8593]: switching to channel 279 10:44:24 [8593]: info: Channel not available! 10:44:26 [8593]: switching to channel 279 10:44:26 [8593]: info: Channel not available! 10:44:28 [8593]: switching to channel 279 10:44:28 [8593]: info: Channel not available! 10:44:30 [8593]: switching to channel 279 10:44:30 [8593]: info: Channel not available! 10:44:32 [8593]: switching to channel 279 10:44:32 [8593]: info: Channel not available! 10:44:34 [8593]: switching to channel 279
10:51:56 [8593]: switching to channel 279 10:51:56 [8593]: info: Channel not available! 10:51:58 [8593]: switching to channel 279 10:51:58 [8593]: info: Channel not available! 10:52:00 [8593]: switching to channel 279 10:52:00 [8593]: info: Channel not available! 10:52:02 [8593]: switching to channel 279 10:52:02 [8593]: info: Channel not available! 10:52:04 [8593]: switching to channel 279 10:52:04 [8593]: info: Channel not available! 10:52:06 [8593]: switching to channel 279 10:52:06 [8593]: info: Channel not available! 10:52:08 [8593]: switching to channel 279 10:52:08 [8593]: info: Channel not available!
msi:~# ps fax | grep vdr 29410 pts/1 S+ 0:00 _ grep vdr 8593 ? S 5:46 ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8595 ? S 0:00 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8596 ? S 0:00 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8597 ? RN 34:45 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8599 ? S 0:00 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8600 ? SN 30:26 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8602 ? S 0:00 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8603 ? SN 31:34 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8605 ? S 0:00 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8606 ? SN 9:03 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8607 ? S 0:00 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ msi:~# kill 8593 msi:~# kill 8593
a kill -9 was required...
vdr 1.3.25 only patch LNBsharing.
Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------
Rainer Zocholl wrote:
Hello
Yesterday i set EGP timeout to 1 in the hope the LNBsharing patch will prevent the usual deadlocks. It does not need to do anything.
It happens too that the box ran that hour without any recordings instead of being powered off as usual, so EPG scan could really start. (Hm, why 1h as minimum?)
On a single card system it doesn't really make much sense to have shorter times - after all, you wouldn't even be able to watch a full length movie.
Besides, if you want to start an EPG scan you can select "Scan" from the Setup/EPG menu at any time.
As you may se below, "Starting EPG scan" starts at channel 0 (zero? What is channel 0?),
This may be a dummy channel that's used to tune to a new transponder. It doesn't have a number.
switches to channel 1, that's Ok... got new transponders/programs, that's OK. (so many new to day?) then VDR switches to channel 279! Why 279 and not 2? What's that?
The next timer event would be a timer to record channel 27 at 10:52 but the switch attempt occurs at 10:42:18 and obviuosly leads VDR into a deep endless loop.
channel 279 is OLD GOLD;PREMIERE:11720:hC34:S19.2E:27500:0:336=deu:0:1801,1722,1702:167:133:3:0
Never ever tuned to 279 (encrypted) channel, no timer except the one in approx 10 minutes at channel 27 ( an ASCII buffer Bug? *27*9?)
Well, since there is a patch involved that may well interfere with all this I'd say you should test without that patch first and see if it happens there, too.
09:09:08 [8593]: info: Channel locked by LNB! 09:09:58 [8600]: changing name of channel 312 from 'D 4 - 07:45,;' to 'D 4 - 09:30,;' 09:09:58 [8600]: linking channel 118 from 305 308 304 415 310 313 312 311 309 to 305 308 304 415 310 313 311 312 309 ... 09:40:48 [8593]: Power button pressed 09:40:48 [8593]: next timer event at Mon Jun 6 10:52:00 2005 09:40:48 [8593]: confirm: Press any key to cancel shutdown 09:40:54 [8593]: confirmed ... 10:00:57 [8593]: next timer event at Mon Jun 6 10:52:00 2005 ... 10:40:37 [8597]: changing pids of channel 160 from 901+901:902:204 to 701+701:702:204 10:41:34 [8593]: info: Starting EPG scan 10:41:36 [8593]: switching to channel 0 10:41:36 [22711]: TS buffer on device 1 thread ended (pid=22711, tid=2752525) 10:41:36 [22710]: buffer stats: 4136 (0%) used 10:41:36 [22710]: receiver on device 1 thread ended (pid=22710, tid=2736140) 10:41:36 [8593]: buffer stats: 0 (0%) used 10:41:37 [8603]: changing pids of channel 636 from 0+0:0:0 to 32+32:33:0 10:41:37 [8603]: changing pids of channel 637 from 0+0:0:0 to 70+70:71:54 10:41:38 [8603]: changing pids of channel 638 from 0+0:0:0 to 0+0:73:0 10:41:38 [8603]: changing pids of channel 639 from 0+0:0:0 to 61+61:62:0 10:41:41 [8603]: changing pids of channel 646 from 0+0:0:0 to 41+41:40:0 10:41:42 [8603]: changing pids of channel 647 from 0+0:0:0 to 0+0:58=eng:0 10:41:42 [8603]: changing pids of channel 648 from 0+0:0:0 to 0+0:59:0 10:42:00 [8600]: creating new channel 'TVP Kultura,;TVP' on S19.2E transponder 110861 with id 1-1059-7101-0 10:42:00 [8600]: creating new channel 'TV Polonia,;TVP Service' on S19.2E transponder 110861 with id 1-1059-7100-0 10:42:00 [8600]: changing pids of channel 814 from 0+0:0:0 to 516+8190:690=pol:580 10:42:00 [8600]: changing pids of channel 815 from 0+0:0:0 to 514+8190:670=pol:578 10:42:02 [8603]: creating new channel 'Cartoon Network/TCM,Cartoon Network/TCM;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20341-0 10:42:02 [8603]: creating new channel 'Boomerang,Boomerang;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20343-0 10:42:02 [8603]: creating new channel 'Viasat Explorer,Viasat Explorer;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20344-0 10:42:02 [8603]: creating new channel 'Viasat History,Viasat History;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20345-0 10:42:02 [8603]: creating new channel 'AXN,AXN;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20346-0 10:42:02 [8603]: creating new channel 'Cinemax,Cinemax;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20347-0 10:42:02 [8603]: creating new channel 'Minimax/A+,Minimax/A+;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20348-0 10:42:02 [8603]: creating new channel 'CT1,CT1;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20342-0 10:42:02 [8603]: creating new channel 'CT2,CT2;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20350-0 10:42:02 [8603]: creating new channel 'Film+,Film+;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20349-0 10:42:02 [8603]: changing pids of channel 818 from 0+0:0:0 to 251+251:260=hun,261=cze:270 10:42:02 [8603]: changing caids of channel 818 from 0 to D02 10:42:02 [8603]: changing pids of channel 819 from 0+0:0:0 to 301+301:310=hun,311=cze:320 10:42:02 [8603]: changing caids of channel 819 from 0 to D02 10:42:02 [8603]: changing pids of channel 820 from 0+0:0:0 to 351+351:360=hun,361=cze,362=eng:370 10:42:02 [8603]: changing caids of channel 820 from 0 to D02 10:42:03 [8603]: changing pids of channel 821 from 0+0:0:0 to 401+401:410=hun,411=cze,412=eng:0 10:42:03 [8603]: changing caids of channel 821 from 0 to D02 10:42:03 [8603]: changing caids of channel 821 from 0 to D02 10:42:03 [8603]: changing pids of channel 822 from 0+0:0:0 to 451+451:460=hun:0 10:42:03 [8603]: changing caids of channel 822 from 0 to D02 10:42:03 [8603]: changing pids of channel 825 from 0+0:0:0 to 501+501:511=cze:0 10:42:03 [8603]: changing caids of channel 825 from 0 to D02 10:42:03 [8603]: changing pids of channel 824 from 0+0:0:0 to 551+551:561=cze:570 10:42:03 [8603]: changing caids of channel 824 from 0 to D02 10:42:04 [8603]: changing pids of channel 816 from 0+0:0:0 to 101+101:110=hun,112=eng:120 10:42:04 [8603]: changing caids of channel 816 from 0 to D02 10:42:04 [8603]: changing pids of channel 823 from 0+0:0:0 to 151+151:161=cze:170 10:42:04 [8603]: changing caids of channel 823 from 0 to D02 10:42:04 [8603]: changing pids of channel 817 from 0+0:0:0 to 201+201:210=hun,212=eng,213=pol:0 10:42:04 [8603]: changing caids of channel 817 from 0 to D02 10:42:18 [8593]: switching to channel 279 10:42:18 [8593]: info: Channel not available! 10:42:20 [8593]: switching to channel 279 10:44:20 [8593]: info: Channel not available! 10:44:22 [8593]: switching to channel 279 10:44:22 [8593]: info: Channel not available! 10:44:24 [8593]: switching to channel 279 10:44:24 [8593]: info: Channel not available! 10:44:26 [8593]: switching to channel 279 10:44:26 [8593]: info: Channel not available! 10:44:28 [8593]: switching to channel 279 10:44:28 [8593]: info: Channel not available! 10:44:30 [8593]: switching to channel 279 10:44:30 [8593]: info: Channel not available! 10:44:32 [8593]: switching to channel 279 10:44:32 [8593]: info: Channel not available! 10:44:34 [8593]: switching to channel 279
10:51:56 [8593]: switching to channel 279 10:51:56 [8593]: info: Channel not available! 10:51:58 [8593]: switching to channel 279 10:51:58 [8593]: info: Channel not available! 10:52:00 [8593]: switching to channel 279 10:52:00 [8593]: info: Channel not available! 10:52:02 [8593]: switching to channel 279 10:52:02 [8593]: info: Channel not available! 10:52:04 [8593]: switching to channel 279 10:52:04 [8593]: info: Channel not available! 10:52:06 [8593]: switching to channel 279 10:52:06 [8593]: info: Channel not available! 10:52:08 [8593]: switching to channel 279 10:52:08 [8593]: info: Channel not available!
msi:~# ps fax | grep vdr 29410 pts/1 S+ 0:00 _ grep vdr 8593 ? S 5:46 ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8595 ? S 0:00 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8596 ? S 0:00 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8597 ? RN 34:45 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8599 ? S 0:00 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8600 ? SN 30:26 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8602 ? S 0:00 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8603 ? SN 31:34 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8605 ? S 0:00 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8606 ? SN 9:03 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ 8607 ? S 0:00 _ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/ msi:~# kill 8593 msi:~# kill 8593
a kill -9 was required...
vdr 1.3.25 only patch LNBsharing.
Does the problem also occur _without_ that patch (plain vanilla VDR)?
Klaus
Klaus.Schmidinger@cadsoft.de(Klaus Schmidinger) 06.06.05 18:20
Rainer Zocholl wrote:
Hello
Yesterday i set EGP timeout to 1 in the hope the LNBsharing patch will prevent the usual deadlocks. It does not need to do anything.
It happens too that the box ran that hour without any recordings instead of being powered off as usual, so EPG scan could really start. (Hm, why 1h as minimum?)
On a single card system
I have more than one card ;-) But somewhere i read the EPG infos are mostly changed only between 2:00 and 3:00.
it doesn't really make much sense to have shorter times
- after all, you wouldn't even be able to watch a full length movie.
Ah, i see. I thought EPG scan would only occur after a lengthly "idle" time and "politely" switch away the channels when no user is present. (If i am already sleeping it would be a feature if VDR would wake me up by switching the channel. ;-))
Besides, if you want to start an EPG scan you can select "Scan" from the Setup/EPG menu at any time.
I would not expect such a function under "Setup", more under "Commands"- but anyway: Under "Setup/EPG": I have only a line named "EPG scan timeout(h): 0" "EPG bugfis level: 2 "EPG linger time(min): 90" "Set Systemtime: yes" "Use time... But no "EPG scan now!" (because i have more than one card?)
As you may se below, "Starting EPG scan" starts at channel 0 (zero? What is channel 0?),
This may be a dummy channel that's used to tune to a new transponder. It doesn't have a number.
Ok, it makes no trouble. just interessting to know.thanks.
switches to channel 1, that's Ok... got new transponders/programs, that's OK. (so many new to day?) then VDR switches to channel 279! Why 279 and not 2? What's that?
The next timer event would be a timer to record channel 27 at 10:52 but the switch attempt occurs at 10:42:18 and obviuosly leads VDR into a deep endless loop.
channel 279 is OLD GOLD;PREMIERE:11720:hC34:S19.2E:27500:0:336=deu:0:1801,1722,1702 :167:133:3:0
Never ever tuned to 279 (encrypted) channel, no timer except the one in approx 10 minutes at channel 27 ( an ASCII buffer Bug? *27*9?)
Well, since there is a patch involved that may well interfere with all this I'd say you should test without that patch first and see if it happens there, too.
I can't test it because the box is normally turned off. An i don't understand why the EPG scan switches to channel 279 and not to channel 3.
Too i really don't think that the patch could cause that loop. The message was not "locked by LNB", as no recording was running, but simply "Channel not available" because is needs a CA.
msi:~# kill 8593
a kill -9 was required...
vdr 1.3.25 only patch LNBsharing.
Does the problem also occur _without_ that patch (plain vanilla VDR)?
That patch existential for my box. With out it EPG scan would switch to a not allowed polarization, given "video stream broken" panic bye bye.
I never had the problem before (but a) the box never idles so long b) EPG was of because of history reasons
Maybe we should first ask, why it is switching to channel 279? Why does EPG do not react to the error code but insists on switching to 279? I assume no one was at home and press 279 on the Rc. And if, it should not lead to a loop (and does not normally)
Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------
On Mon, 6 Jun 2005, Rainer Zocholl (RZ) wrote:
RZ> RZ> >Besides, if you want to start an EPG scan you can RZ> >select "Scan" from the Setup/EPG menu at any time. RZ> RZ> I would not expect such a function under "Setup", more under "Commands"- RZ> but anyway: RZ> Under "Setup/EPG": I have only a line named RZ> "EPG scan timeout(h): 0" RZ> "EPG bugfis level: 2 RZ> "EPG linger time(min): 90" RZ> "Set Systemtime: yes" RZ> "Use time... RZ> But no "EPG scan now!"
Red button
c ya Sergei
Rainer Zocholl wrote:
Klaus.Schmidinger@cadsoft.de(Klaus Schmidinger) 06.06.05 18:20
On a single card system
I have more than one card ;-) But somewhere i read the EPG infos are mostly changed only between 2:00 and 3:00.
it doesn't really make much sense to have shorter times
- after all, you wouldn't even be able to watch a full length movie.
Ah, i see. I thought EPG scan would only occur after a lengthly "idle" time and "politely" switch away the channels when no user is present. (If i am already sleeping it would be a feature if VDR would wake me up by switching the channel. ;-))
The EPG timeout setting is that "idle" time.
But since you have multiple cards, that setting doesn't apply at all.
Sergei.Haller@math.uni-giessen.de(Sergei Haller) 06.06.05 20:21
Once upon a time "Sergei Haller " shaped the electrons to say...
On Mon, 6 Jun 2005, Rainer Zocholl (RZ) wrote:
RZ>> RZ>>>Besides, if you want to start an EPG scan you can RZ>>>select "Scan" from the Setup/EPG menu at any time. RZ>> RZ>> I would not expect such a function under "Setup", more under RZ>> "Commands"- but anyway: RZ>> Under "Setup/EPG": I have only a line named RZ>> "EPG scan timeout(h): 0" RZ>> "EPG bugfis level: 2 RZ>> "EPG linger time(min): 90" RZ>> "Set Systemtime: yes" RZ>> "Use time... RZ>> But no "EPG scan now!"
Red button
Outsch. I really did not expect such a command function in that menu, and what should tell the word "scan" alone? It's time for a online help key ;-) (No, i don't have the time) Maybe someone can scan in the "keyfunction table" and make a still video of it?
And: When i press red button, simply all menue closes- nothing is reported to the user. Syslog does not show "EPG scan start". I set the scan timeout to 1h. but that does not help.
anssi.hannula@gmail.com(Anssi Hannula) 06.06.05 21:32
Rainer Zocholl wrote:
Klaus.Schmidinger@cadsoft.de(Klaus Schmidinger) 06.06.05 18:20
On a single card system
I have more than one card ;-) But somewhere i read the EPG infos are mostly changed only between 2:00 and 3:00.
it doesn't really make much sense to have shorter times
- after all, you wouldn't even be able to watch a full length movie.
Ah, i see. I thought EPG scan would only occur after a lengthly "idle" time and "politely" switch away the channels when no user is present. (If i am already sleeping it would be a feature if VDR would wake me up by switching the channel. ;-))
The EPG timeout setting is that "idle" time.
But since you have multiple cards, that setting doesn't apply at all.
Almost. The value "0" switches EPG scan of. I once needed that because of LNBsharing.
Rainer Zocholl wrote:
Sergei.Haller@math.uni-giessen.de(Sergei Haller) 06.06.05 20:21
Once upon a time "Sergei Haller " shaped the electrons to say...
On Mon, 6 Jun 2005, Rainer Zocholl (RZ) wrote:
RZ>> RZ>>>Besides, if you want to start an EPG scan you can RZ>>>select "Scan" from the Setup/EPG menu at any time. RZ>> RZ>> I would not expect such a function under "Setup", more under RZ>> "Commands"- but anyway: RZ>> Under "Setup/EPG": I have only a line named RZ>> "EPG scan timeout(h): 0" RZ>> "EPG bugfis level: 2 RZ>> "EPG linger time(min): 90" RZ>> "Set Systemtime: yes" RZ>> "Use time... RZ>> But no "EPG scan now!"
Red button
Outsch. I really did not expect such a command function in that menu,
Well, it's gotta be _somewhere_ ;-)
and what should tell the word "scan" alone?
Hmm, it's the EPG setup menu, and there's a command button that says "Scan"... What might that scan? The transponders? The channels? The user's iris? The bar code on your forehead? Surely it can't mean that it scans the EPG - because then it wouldn't be in the EPG setup menu - or would it?
SCNR
It's time for a online help key ;-) (No, i don't have the time) Maybe someone can scan in the "keyfunction table" and make a still video of it?
How about taking a look at the MANUAL file?
* Parameters in the "Setup" menu ... EPG: ... Scan The "Red" button in the "Setup/EPG" menu can be used to force an EPG scan on a single DVB card system. If pressed, and the primary DVB device is currently not recording or replaying, it will loop through the transponders once and then switch back to the original channel. Any user activity during the EPG scan will also stop the scan and bring back the original channel.
And: When i press red button, simply all menue closes- nothing is reported to the user. Syslog does not show "EPG scan start". I set the scan timeout to 1h. but that does not help.
This function is mainly for single card systems. In multiple card systems the EPG scan is always active when there has been no user activity for some 60 seconds. The "Scan" button then simply cuts that timeout short. There is no need for an explicit message because the primary card is not switched to a different channel.
Klaus
Klaus Schmidinger wrote:
Hmm, it's the EPG setup menu, and there's a command button that says "Scan"... What might that scan? The transponders? The channels? The user's iris? The bar code on your forehead?
I always wondered what that button really did, because I cannot see is doing anything here (and I'm almost glad it doesn't since random satellite hopping[*] isn't really great). Maybe it's not supposed to work with a budget card playing through softdevice/xine/dxr3 ?
[*] that's what I get when I setup epg scan timeout != 0 and I'm playing a recording.
Bye
UseNet-Posting-Nospam-74308-@zocki.toppoint.de(Rainer Zocholl) 06.06.05 21:11
[How to force EPG scan]
Red button
When i press red button, simply all menue closes- nothing is reported to the user. Syslog does not show "EPG scan start". I set the scan timeout to 1h. but that does not help.
But after one hour i get again the same error, now with channel 660...
I don't know if there is a corelation bewteen the (failed) powerdown attempt and the bug.
16:42 [26395]: next timer event at Tue Jun 7 01:00:00 2005 16:42 [26395]: confirm: Press any key to cancel shutdown 17:37 [26399]: changing pids of channel 161 from 701+701:702:204 to 901+901:902:204 18:38 [26399]: changing pids of channel 161 from 901+901:902:204 to 701+701:702:204 19:33 [26399]: changing pids of channel 161 from 701+701:702:204 to 901+901:902:204 20:36 [26399]: changing pids of channel 161 from 901+901:902:204 to 701+701:702:204 21:39 [26399]: changing pids of channel 161 from 701+701:702:204 to 901+901:902:204 21:43 [26395]: confirmed 21:43 [26395]: executing '/video0/pwroff 1118098800 5897 80 "Rec" 0' 21:45 [26395]: max. latency time 60 seconds 22:34 [26399]: changing pids of channel 161 from 901+901:902:204 to 701+701:702:204 23:31 [26395]: info: Starting EPG scan 23:33 [26395]: switching to channel 0 23:33 [28128]: TS buffer on device 1 thread ended (pid=28128, tid=950285) 23:33 [28127]: buffer stats: 3948 (0%) used 23:33 [28127]: receiver on device 1 thread ended (pid=28127, tid=933900) 23:33 [26395]: buffer stats: 0 (0%) used 23:35 [26399]: creating new channel 'TAQUILLA 1,;TQ1' on S19.2E transponder 210788 with id 1-1054-30350-0 23:35 [26399]: creating new channel 'TAQUILLA 2,;TQ2' on S19.2E transponder 210788 with id 1-1054-30351-0 23:35 [26399]: creating new channel 'TAQUILLA 3,;TQ3' on S19.2E transponder 210788 with id 1-1054-30352-0 23:35 [26399]: creating new channel 'TAQUILLA 4,;TQ4' on S19.2E transponder 210788 with id 1-1054-30353-0 23:35 [26399]: creating new channel 'TAQUILLA XY,;TXY' on S19.2E transponder 210788 with id 1-1054-30357-0 23:35 [26399]: creating new channel 'TAQUILLA 8,;TQ8' on S19.2E transponder 210788 with id 1-1054-30358-0 23:35 [26399]: creating new channel 'TELECINCO,;T5' on S19.2E transponder 210788 with id 1-1054-30359-0 23:35 [26399]: creating new channel 'BOOMERANG,;BOOM' on S19.2E transponder 210788 with id 1-1054-30361-0 23:35 [26399]: changing pids of channel 852 from 0+0:0:0 to 160+160:80=esl:0 23:35 [26399]: changing caids of channel 852 from 0 to 100 ... 25:18 [26405]: creating new channel 'LATINA TV,;GCE' on S19.2E transponder 211508 with id 1-1020-7007-0 25:18 [26405]: creating new channel 'full-X3,;GlobeCast' on S19.2E transponder 211508 with id 1-1020-7001-0 25:18 [26405]: creating new channel 'full-X3 M,;' on S19.2E transponder 211508 with id 1-1020-7002-0 25:18 [26405]: changing pids of channel 964 from 0+0:0:0 to 705+705:725:0 25:18 [26405]: changing pids of channel 965 from 0+0:0:0 to 704+704:724:0 25:19 [26405]: changing pids of channel 966 from 0+0:0:0 to 706+706:726=esl:0 25:19 [26405]: changing pids of channel 967 from 0+0:0:0 to 708+708:728:0 25:19 [26405]: changing pids of channel 968 from 0+0:0:0 to 707+707:727:0 25:19 [26405]: changing pids of channel 970 from 0+0:0:0 to 6045+6045:6010:0 25:19 [26405]: changing caids of channel 970 from 0 to 4A60 25:20 [26405]: changing pids of channel 969 from 0+0:0:0 to 6045+6045:6010:0 25:20 [26405]: changing caids of channel 969 from 0 to 4A60,4A61,4A63 25:20 [26405]: changing pids of channel 963 from 0+0:0:0 to 6101+6101:0:0 25:20 [26405]: changing caids of channel 963 from 0 to 4A6F 26:00 [26395]: switching to channel 660 26:00 [26395]: info: Channel not available! 26:02 [26395]: switching to channel 660 26:02 [26395]: info: Channel not available! 26:04 [26395]: switching to channel 660 26:04 [26395]: info: Channel not available! 26:06 [26395]: switching to channel 660 26:06 [26395]: info: Channel not available! 26:08 [26395]: switching to channel 660 26:08 [26395]: info: Channel not available! 26:10 [26395]: switching to channel 660 26:10 [26395]: info: Channel not available! ...forever until "kill -9"
Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------
Klaus Schmidinger wrote:
This function is mainly for single card systems. In multiple card systems the EPG scan is always active when there has been no user activity for some 60 seconds. The "Scan" button then simply cuts that timeout short. There is no need for an explicit message because the primary card is not switched to a different channel.
Hi,
I tested this function some time ago (already VDR 1.3.x) on a single card system but nothing happened - the current channel continued being displayed, so EPG scan simply did not seem to work. Anybody out there who can confirm that this function really works? I have a multi-card system for a long time now so I can´t test it myself, but I am interested asking for some people that I infected with the VDR virus :-)
With kind regards
Joerg
Joerg Knitter wrote: ...
I tested this function some time ago (already VDR 1.3.x) on a single card system but nothing happened - the current channel continued being displayed, so EPG scan simply did not seem to work. Anybody out there who can confirm that this function really works? I have a multi-card system for a long time now so I can´t test it myself, but I am interested asking for some people that I infected with the VDR virus :-)
There was a bug that prevented the EPG scan from running. A fix has been posted here recently and was incorporated into 1.3.25.
Carsten.
On Tue, 2005-06-07 at 11:56 +0200, Joerg Knitter wrote:
I tested this function some time ago (already VDR 1.3.x) on a single card system but nothing happened - the current channel continued being displayed, so EPG scan simply did not seem to work. Anybody out there who can confirm that this function really works? I have a multi-card system for a long time now so I can´t test it myself, but I am interested asking for some people that I infected with the VDR virus :-)
Whenever I've tried to trigger an EPG scan on a single card system, it has never seemed to do anything! I haven't tried doing so for a while, though (6 months?!). I'll try later on, if I remember...
Cheers,
Laz
En/na Carsten Koch ha escrit:
Joerg Knitter wrote: ...
I tested this function some time ago (already VDR 1.3.x) on a single card system but nothing happened - the current channel continued being displayed, so EPG scan simply did not seem to work. Anybody out there who can confirm that this function really works? I have a multi-card system for a long time now so I can´t test it myself, but I am interested asking for some people that I infected with the VDR virus :-)
There was a bug that prevented the EPG scan from running. A fix has been posted here recently and was incorporated into 1.3.25.
I don't think it's working (see my other message in this thread, I'm using 1.3.25).
Bye
Joerg Knitter wrote:
Klaus Schmidinger wrote:
This function is mainly for single card systems. In multiple card systems the EPG scan is always active when there has been no user activity for some 60 seconds. The "Scan" button then simply cuts that timeout short. There is no need for an explicit message because the primary card is not switched to a different channel.
Hi,
I tested this function some time ago (already VDR 1.3.x) on a single card system but nothing happened - the current channel continued being displayed, so EPG scan simply did not seem to work. Anybody out there who can confirm that this function really works? I have a multi-card system for a long time now so I can´t test it myself, but I am interested asking for some people that I infected with the VDR virus :-)
You can easily test this by running VDR with the -D option, as in
./vdr -D0
so that it uses only one device. I just did so, and pressing the red button in Setup/EPG does start the EPG scan immediately (blank screen and message "Starting EPG scan"). Of course, if you press any key after that the EPG scan will be stopped again and it tunes back to the previous channel.
Klaus
Luca Olivetti wrote:
En/na Carsten Koch ha escrit:
Joerg Knitter wrote: ...
I tested this function some time ago (already VDR 1.3.x) on a single card system but nothing happened - the current channel continued being displayed, so EPG scan simply did not seem to work. Anybody out there who can confirm that this function really works? I have a multi-card system for a long time now so I can´t test it myself, but I am interested asking for some people that I infected with the VDR virus :-)
There was a bug that prevented the EPG scan from running. A fix has been posted here recently and was incorporated into 1.3.25.
I don't think it's working (see my other message in this thread, I'm using 1.3.25).
Just tested it - it does work (at least with my plain vanilla VDR 1.3.25).
Klaus
Klaus Schmidinger wrote:
I don't think it's working (see my other message in this thread, I'm using 1.3.25).
Just tested it - it does work (at least with my plain vanilla VDR 1.3.25).
Just tested: it doesn't work here (plain vanilla vdr 1.3.25 + xine plugin or dxr3 plugin : I need one of them to be able to watch tv).
Bye
Luca Olivetti wrote:
Klaus Schmidinger wrote:
I don't think it's working (see my other message in this thread, I'm using 1.3.25).
Just tested it - it does work (at least with my plain vanilla VDR 1.3.25).
Just tested: it doesn't work here (plain vanilla vdr 1.3.25 + xine plugin or dxr3 plugin : I need one of them to be able to watch tv).
Ah, maybe that's the point - I have a full featured card.
I'll look into that...
Klaus
Klaus Schmidinger wrote:
Luca Olivetti wrote:
Klaus Schmidinger wrote:
Just tested it - it does work (at least with my plain vanilla VDR 1.3.25).
Just tested: it doesn't work here (plain vanilla vdr 1.3.25 + xine plugin or dxr3 plugin : I need one of them to be able to watch tv).
Ah, maybe that's the point - I have a full featured card.
does _not_ work for me: full featured card (Hauppauge 2.1), vanilla vdr 1.3.25, Kernel 2.6.11.4 (SuSE 9.3), standard kernel DVB drivers and cvs (some days ago) tested
Andreas
Carsten.Koch@icem.com(Carsten Koch) 07.06.05 12:17
Joerg Knitter wrote: ...
I tested this function some time ago (already VDR 1.3.x) on a single card system but nothing happened - the current channel continued being displayed, so EPG scan simply did not seem to work. Anybody out there who can confirm that this function really works? I have a multi-card system for a long time now so I can't test it myself, but I am interested asking for some people that I infected with the VDR virus :-)
There was a bug that prevented the EPG scan from running. A fix has been posted here recently and was incorporated into 1.3.25.
I am running 1.3.25. Could that fix be the reason for this loop problem in a LNBsharing (=multi card) system?
If i press the red button NOTHING happens according to the logfile. After one hour, EPG scan starts (in a Multicard system!!! not after 60sec of idle as supposed), switches to 0 , to 1 and then always(?) to a pure garbage channel, as if something has overwritten the variable. Once it was "279" and another time "660". After that the box is in endless loop. Only repainting the OSD "Channel not available" (because it needs a CA).
Because i always have to wait one hour of idle the "testing" is not very effective... Too i can't used an "vanilla VDR" bcause the Box IS sharing LNB.
Rainer
Klaus Schmidinger wrote:
Luca Olivetti wrote:
Klaus Schmidinger wrote:
I don't think it's working (see my other message in this thread, I'm using 1.3.25).
Just tested it - it does work (at least with my plain vanilla VDR 1.3.25).
Just tested: it doesn't work here (plain vanilla vdr 1.3.25 + xine plugin or dxr3 plugin : I need one of them to be able to watch tv).
Ah, maybe that's the point - I have a full featured card.
I'll look into that...
Don't worry: I don't need the feature and I've also disabled the automatic epg scan (as I said, I don't like the dish moving randomly when an epg scan starts). I was just curious about the function of the button.
Bye
Rainer Zocholl wrote:
Once it was "279" and another time "660". After that the box is in endless loop.
I saw something similar before I completely disabled the epg scan.
Bye
andreas@andreas-hoelscher.de(Andreas Hölscher) 07.06.05 19:35
Once upon a time "Andreas Hölscher " shaped the electrons to say...
Klaus Schmidinger wrote:
Luca Olivetti wrote:
Klaus Schmidinger wrote:
Just tested it - it does work (at least with my plain vanilla VDR 1.3.25).
Just tested: it doesn't work here (plain vanilla vdr 1.3.25 + xine plugin or dxr3 plugin : I need one of them to be able to watch tv).
Ah, maybe that's the point - I have a full featured card.
does _not_ work for me: full featured card (Hauppauge 2.1), vanilla vdr 1.3.25, Kernel 2.6.11.4 (SuSE 9.3), standard kernel DVB drivers and cvs (some days ago) tested
Same config, but debian and LNB sharing patch. main invoke lines: export LD_ASSUME_KERNEL=2.4.1 VDRPRG="./vdr -v /video0" #VDRCMD="$VDRPRG -D0 -l 3 -w 60 -s /video0/pwroff $*"
EPG scan time=1 (with time=0 the red key only closes the menu..not really ergonomical.) "red key" Screen becomes black any key the screen turns on again
syslog shows 1:44 [8478]: max. latency time 1 seconds 1:54 [8478]: saved setup to /video0/setup.conf 2:03 [8478]: info: Starting EPG scan 2:05 [8478]: max. latency time 2 seconds 2:50 [8478]: switching to channel 14 2:57 [8482]: changing pids of channel 162 from 901+901:902:204 to 701+701:702:204
But: i miss the "switching to 0" ("switch to 14" occured when i pressed any key)
Too that does not really help to determine the looping in a multicard system and why EPG is trying to switch to an entriely senseless random channel (3 FF-DVB-S 1 DVB-T)
Rainer
luca@ventoso.org(Luca Olivetti) 07.06.05 20:30
Rainer Zocholl wrote:
Once it was "channel 279" and another time "660". After that the box is in endless loop.
I saw something similar before I completely disabled the epg scan.
Because EPG interfered recording in a single LNB system (it would switch polarizations causing "video stream broken" panic restarts on the other cards) i had EPG-scan turned off all the time before...It was only a test.
What will happen if i user -D0 -D3 with 0=FF-DVB-S and 3=budget DVB-T? Will EPG scan only collect DVB-T EPG?
Anybody here who is really using EPG scan? ;-)
Rainer
Anybody here who is really using EPG scan? ;-)
Yes, me :-)
It did *never* work here until a bug was fixed in 1.3.25. Now the EPG scan starts in the night (as I want it to), but in the next morning, my screen is black. VDR still works, I can access the menus and so on, but no Live-TV. If I watch a recording, it's fine, if I abort it again => black screen. The only solution I found is restarting VDR.
Maybe the EPG scan tries to tune to a evil/bad/random channel, or one of the channels confuses the FF card, ...
I could not find anything useful in the logfiles...
bye, Michael
Michael Reinelt wrote:
scan starts in the night (as I want it to), but in the next morning, my screen is black. VDR still works, I can access the menus and so on, but no Live-TV. If I watch a recording, it's fine, if I abort it again => black screen. The only solution I found is restarting VDR.
I seen same effect, but only sometimes. Mostly VDR (1.3.25, 1FF+1Skystar2, LNB sharing patch, kernel 2.4.30) returns fine from EPG scan.
SK
On Tue, 7 Jun 2005, Rainer Zocholl (RZ) wrote:
RZ> RZ> Anybody here who is really using EPG scan? ;-)
yes. (although, usually not the red button)
c ya Sergei
reinelt@eunet.at(Michael Reinelt) 08.06.05 07:24
Anybody here who is really using EPG scan? ;-)
Yes, me :-)
Ah, you do? ;-)
Is it a single or multi card system? I assume it's a single card?
It did *never* work here until a bug was fixed in 1.3.25.
Now the EPG scan starts in the night (as I want it to),
If it is a multi card system, when does it start? almost "immediately" or after 1 or 2 h?
but in the next morning, my screen is black.
VDR still works, I can access the menus and so on, but no Live-TV.
I could not, VDR reprints very fast the line "channel not available" on the OSD.
If I watch a recording, it's fine, if I abort it again => black screen.
Have you locked all HDTV channels with an "non existing CA"-ID?
The only solution I found is restarting VDR.
ACK, but is assume in your case "simply" one of the drivers died.
Maybe the EPG scan tries to tune to a evil/bad/random channel, or one of the channels confuses the FF card, ...
I could not find anything useful in the logfiles...
I only found 2 "switch to channel"...
Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------
Rainer Zocholl wrote:
Is it a single or multi card system?
Single FF card.
Now the EPG scan starts in the night (as I want it to),
If it is a multi card system, when does it start? almost "immediately" or after 1 or 2 h?
single card, so after 3 hours or so (as set up in "EPG Scan Delay") or by pressing the Red Button.
Have you locked all HDTV channels with an "non existing CA"-ID?
Huh? How can I find them? If I found'em, how could I "lock" them?
The only solution I found is restarting VDR.
ACK, but is assume in your case "simply" one of the drivers died.
I think so, too, but there's no way to restart just this driver?
I could not find anything useful in the logfiles...
I only found 2 "switch to channel"...
Here's what my log says:
This was the last user interaction: Jun 9 01:31:30 artus vdr[21880]: switching to channel 5
About 2 hours later the EPG scan starts: Jun 9 03:31:51 artus vdr[21880]: info: Beginne mit EPG-Scan
Some corrections done by the EPG scan: Jun 9 03:32:18 artus vdr[21886]: changing name of channel 5500 from 'TV Polonia,;TVP Service' to 'TV Polonia,;TVP' Jun 9 03:32:57 artus vdr[21886]: linking channel 150 from 157 151 158 152 153 159 155 154 to 157 151 158 159 154 155
(btw, what's this 'linking channel...' about?
Somethin strange: Jun 9 03:37:51 artus vdr[21889]: CAM: different stream flag in CA descriptors Jun 9 03:38:11 artus last message repeated 7 times
Is this a "non-existing CA"-ID and/or a HDTV channel?
At 6 in the morning a timer starts: Jun 9 06:01:00 artus vdr[21880]: timer 4 (1 0601-0619 'Die Abenteuer der Maus auf dem Mars~Der Marsmensch') start
10 mins later an error occurs: Jun 9 06:09:10 artus kernel: av7110_fw_request: timeout waiting for COMMAND to complete Jun 9 06:09:10 artus kernel: dvb-ttpci: StartHWFilter error buf 0b07 0010 03f3 b96a ret ffffffff handle c036 Jun 9 06:09:11 artus kernel: StopHWFilter tried to stop invalid filter ffff, filter type = 1
Michael Reinelt wrote:
Anybody here who is really using EPG scan? ;-)
Yes, me :-)
It did *never* work here until a bug was fixed in 1.3.25. Now the EPG scan starts in the night (as I want it to), but in the next morning, my screen is black. VDR still works, I can access the menus and so on, but no Live-TV. If I watch a recording, it's fine, if I abort it again => black screen. The only solution I found is restarting VDR.
Maybe the EPG scan tries to tune to a evil/bad/random channel, or one of the channels confuses the FF card, ...
The EPG scan only tunes to each transponder for some 20 seconds and collects whatever data it finds. It does not switch to any particular _channel_ (i.e. it does not set the primary device to display a certain programme). So even if it tunes to, say, a transponder that broadcasts HDTV programmes, a full featured DVB card shouldn't suffer from that, because it never "sees" the actual HDTV data stream.
Klaus
Andreas Hölscher wrote:
Klaus Schmidinger wrote:
Luca Olivetti wrote:
Klaus Schmidinger wrote:
Just tested it - it does work (at least with my plain vanilla VDR 1.3.25).
Just tested: it doesn't work here (plain vanilla vdr 1.3.25 + xine plugin or dxr3 plugin : I need one of them to be able to watch tv).
Ah, maybe that's the point - I have a full featured card.
does _not_ work for me: full featured card (Hauppauge 2.1), vanilla vdr 1.3.25, Kernel 2.6.11.4 (SuSE 9.3), standard kernel DVB drivers and cvs (some days ago) tested
Well, I don't see why this wouldn't work. Any patches that might be causing this failure?
Klaus
How I have to use nvram wakeup with vdr?
Rudy.
Hi Klaus,
Now the EPG scan starts in the night (as I want it to), but in the next morning, my screen is black. VDR still works, I can access the menus and so on, but no Live-TV. If I watch a recording, it's fine, if I abort it again => black screen. The only solution I found is restarting VDR.
The EPG scan only tunes to each transponder for some 20 seconds and collects whatever data it finds. It does not switch to any particular _channel_ (i.e. it does not set the primary device to display a certain programme). So even if it tunes to, say, a transponder that broadcasts HDTV programmes, a full featured DVB card shouldn't suffer from that, because it never "sees" the actual HDTV data stream.
Thanks for the info. This explains why the screen goes black when I start a scan with the red button, right?
Anyway, I *will* find this bug :-)
Debugging this one will be hard... If I switch to another channel after I started an EPG scan, it's fine: the scan stops, and I get live TV. I would have to start scan, wait 20 seconds, change channel. Start scan, wait 40 seconds, channel switch. start, 60 seconds, .... well, approximately after a year I would have found the reason ;-(
Maybe a debug message "scanning EPG on transponder xy" would be helpful. Klaus, could you give me a hint where to place such a printf? (my C++ knowledge is that miserable)
I think that only live tv does not work, as I said, watching a recording is fine. And I think that recording works fine, too (there's an autotimer from my girlfriend for "Die Maus auf dem Mars" every morning, and I'm *sure* she would have complained :-)
I get lots of "CAM: different stream flag in CA descriptors" messages during the night (probably during the EPG scan), any idea what this means?
btw, today I've seen lots of this messages in my log: changing pids of channel 3203 from 701+701:702:204 to 901+901:902:204 changing pids of channel 3203 from 901+901:902:204 to 701+701:702:204 changing pids of channel 3203 from 701+701:702:204 to 901+901:902:204
they alternate every 30 seconds or so.
Channel 3203 is here: Test-R;ARD:11836:hC34:S19.2E:27500:901:902:204:0:28130:1:1101:0
oh, it's called Test-R... that explains it all :-)
TIA, Michael
Michael Reinelt wrote:
...
The EPG scan only tunes to each transponder for some 20 seconds and collects whatever data it finds. It does not switch to any particular _channel_ (i.e. it does not set the primary device to display a certain programme). So even if it tunes to, say, a transponder that broadcasts HDTV programmes, a full featured DVB card shouldn't suffer from that, because it never "sees" the actual HDTV data stream.
Thanks for the info. This explains why the screen goes black when I start a scan with the red button, right?
Yes.
Anyway, I *will* find this bug :-)
Debugging this one will be hard... If I switch to another channel after I started an EPG scan, it's fine: the scan stops, and I get live TV. I would have to start scan, wait 20 seconds, change channel. Start scan, wait 40 seconds, channel switch. start, 60 seconds, .... well, approximately after a year I would have found the reason ;-(
Maybe a debug message "scanning EPG on transponder xy" would be helpful. Klaus, could you give me a hint where to place such a printf? (my C++ knowledge is that miserable)
Look at the file VDR/eitscan.c and add your output to cEITScanner::Process().
I think that only live tv does not work, as I said, watching a recording is fine. And I think that recording works fine, too (there's an autotimer from my girlfriend for "Die Maus auf dem Mars" every morning, and I'm *sure* she would have complained :-)
I get lots of "CAM: different stream flag in CA descriptors" messages during the night (probably during the EPG scan), any idea what this means?
See cCaDescriptors::GetCaDescriptors() in VDR/pat.c. IIRC (it's been a while since I've worked on this ;-) CA descriptors are either for individual PIDs or an entire program stream. This debug message indicates a discrepancy here. I'm not sure if this constitues an error or what to do with it. We'd need somebody with an actual subscription to such a channel in order to test this.
Klaus
Michael Reinelt wrote:
btw, today I've seen lots of this messages in my log: changing pids of channel 3203 from 701+701:702:204 to 901+901:902:204 changing pids of channel 3203 from 901+901:902:204 to 701+701:702:204 changing pids of channel 3203 from 701+701:702:204 to 901+901:902:204
they alternate every 30 seconds or so.
Channel 3203 is here: Test-R;ARD:11836:hC34:S19.2E:27500:901:902:204:0:28130:1:1101:0
oh, it's called Test-R... that explains it all :-)
Well, when I do a satellite scan, I see various
"changing name of channel from A to B"
and then later on
"changing name of channel from B to A"
(e.g. "TRT INT" and "RAI INTERNATIONAL", but it's not limited to this pair)
and not on test channels. I think that there are various broadcasters that use the same id for different channels, or maybe a vdr bug, I don't know, I didn't bother too much since these are channel that I don't watch or I cannot watch.
Bye
I have the same question - can't find the answer.
I have nvram-wakeup working manually but want to use the VDR timers to set it. How do you do this?
It looks like the timer value set in timers.conf is not std Unix time, but some other number.
I'm not so worried about shutdown at the moment. This doesn't look difficult - just need to define the parameters allowing an automatic shutdown. But I do want to automate powering on for the 'next' timer.
Do I need to write a script that will pull the 'next' timer out of timers.conf, and 'nvram-wakeup -s' it?
----- Original Message ----- From: "Rainer Zocholl" UseNet-Posting-Nospam-74308-@zocki.toppoint.de To: vdr@linuxtv.org Sent: Saturday, June 11, 2005 11:26 PM Subject: Re: [vdr] How to use nvram wakeup with vdr?
rsgorlon@tiscali.it(Rudy Sgorlon) 11.06.05 17:38
How I have to use nvram wakeup with vdr?
By reading the docs inside of the nvram-archive? ;-)
Rainer
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
-- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.6.9 - Release Date: 11/06/2005
Simon Baxter wrote:
I have the same question - can't find the answer.
RTM!
look into vdr-1.3.x/INSTALL under "Automatic shutdown:"
---snip--- The command given in the '-s' option will be called with five parameters. The first one is the time (in UTC) of the next timer event (as a time_t type number), and the second one is the number of seconds from the current time until the next timer event. ---snip---
André.
André Weidemann ha scritto:
Simon Baxter wrote:
I have the same question - can't find the answer.
RTM!
look into vdr-1.3.x/INSTALL under "Automatic shutdown:"
---snip--- The command given in the '-s' option will be called with five parameters. The first one is the time (in UTC) of the next timer event (as a time_t type number), and the second one is the number of seconds from the current time until the next timer event. ---snip---
André.
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Thank you for the information. Sorry for the stupid question, I use apt-get to get nvram-wakup and in the manual I don't find nothing to use with vdr. Now I have download the complete archive ad I have see the doc and the vdr shutdown script.
Rudy.
Klaus Schmidinger wrote:
does _not_ work for me: full featured card (Hauppauge 2.1), vanilla vdr 1.3.25, Kernel 2.6.11.4 (SuSE 9.3), standard kernel DVB drivers and cvs (some days ago) tested
Well, I don't see why this wouldn't work. Any patches that might be causing this failure?
No patch at all for the tests.
Andreas
Andreas Hölscher wrote:
Klaus Schmidinger wrote:
does _not_ work for me: full featured card (Hauppauge 2.1), vanilla vdr 1.3.25, Kernel 2.6.11.4 (SuSE 9.3), standard kernel DVB drivers and cvs (some days ago) tested
Well, I don't see why this wouldn't work. Any patches that might be causing this failure?
No patch at all for the tests.
Andreas
Please try with VDR 1.3.26 - I've changed the way devices are selected for the EPG scan.
Klaus
-
Andreas Hölscher -
André Weidemann -
Anssi Hannula -
Carsten Koch -
Joerg Knitter -
Klaus Schmidinger -
Laurence Abbott -
Luca Olivetti -
Michael Reinelt -
Rainer Zocholl -
Rudy Sgorlon -
Sergei Haller -
Simon Baxter -
Suur Karu