Re: [vdr] Failed to read channels.conf after adding transponder
Am Mittwoch 18 Juni 2008 schrieb Peter Evertz:
> >> I want to disable the check, for invalid channels in channels.conf
> >> I just don't care, if a channel is not "tuneable".
> >
> > in config.h, in the function "bool Load()" at about line 123 (vdr 1.4.7)
> > uncomment 2 lines:
> >else {
> > esyslog("ERROR: error in %s, line %d", fileName,
> > line); delete l;
> > //RC: we do not want to exit vdr just because of a
> > simple error
> > //result = false;
> > //break;
> > }
> >}
> > }
> > this will cause vdr to go on starting even if an error accours in a
> > config file and increase waf. ;)
> Are you sure that your fix will increase the WAF ? I don't know if VDR
> works correctly with a "broken" channels list.
It is not broken, as the questionable entry is deleted again (delete l;) when
parsing it. So happens for all configuration files. You can do
a 'cat /dev/random > /etc/vdr/channels.conf' and the vdr still comes up.
This way it is prevented that the vdr hangs inside a boot-loop.
cu, tim
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] lcdproc, utf-8 & VDR
2008/6/18 Michael Brakemeier <[EMAIL PROTECTED]>: > Have you tried the -jw4 Version from Joachims website? > This should fix the ?-issue - it does this at least for me, my > display now correctly prompts "Taste drücken..." instead of > "Taste dr?cken..." on power off. I tried now =) I hadn't even noticed a new version before. And, it really does fix the problem with VDR messages, so Joachim must've changed something. But I still get ?-marks for commands from the commands menu. For example, I have "Äänet pois / päälle" -command in commands.conf. That is displayed correctly when I browse the menu. VDR is supposed to display the name of the command after I run it, and does, but then the Ä and ä are displayed as ?-marks. Still, thanks go to Joachim for maintaining this plugin! -Ville -- Ville Aakko - [EMAIL PROTECTED] -- -- Ville Aakko - [EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Failed to read channels.conf after adding transponder
Tim schrieb:
> Am Mittwoch 18 Juni 2008 schrieb Peter Evertz:
>
>
I want to disable the check, for invalid channels in channels.conf
I just don't care, if a channel is not "tuneable".
>>> in config.h, in the function "bool Load()" at about line 123 (vdr 1.4.7)
>>> uncomment 2 lines:
>>>else {
>>> esyslog("ERROR: error in %s, line %d", fileName,
>>> line); delete l;
>>> //RC: we do not want to exit vdr just because of a
>>> simple error
>>> //result = false;
>>> //break;
>>> }
>>>}
>>> }
>>> this will cause vdr to go on starting even if an error accours in a
>>> config file and increase waf. ;)
>>>
>> Are you sure that your fix will increase the WAF ? I don't know if VDR
>> works correctly with a "broken" channels list.
>>
> It is not broken, as the questionable entry is deleted again (delete l;) when
> parsing it. So happens for all configuration files. You can do
> a 'cat /dev/random > /etc/vdr/channels.conf' and the vdr still comes up.
> This way it is prevented that the vdr hangs inside a boot-loop.
>
You are right. I did not see the delete statement. I thought you have
only removed the check, resulting in a channel list with "invalid" entries.
Bye
Peter
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Test Feed crashes vdr 1.6.0
Hi Patrick (and of course Klaus ;o)) > For some days there i a new "Test Feed" channel being found automatic > new channel scanner of vdr-1.6.0: > > [EMAIL PROTECTED]:/etc/vdr# tail -1 channels.conf > Test Feed;Test Feed:10920:hC56:S19.2E:22000:0:0:0:0:0:1:1063:0 > [EMAIL PROTECTED]:/etc/vdr# I pretty much had the same problem. AFTER discovering what was wrong, I simply deleted the "Test Feed" channel and VDR went back to normal operation. Actually, I woke up in the middle of the night because my TV set was continually blinking a white screen at me every few minutes ;o)) (Due to the drivers being reloaded), which is how a discovered the problem at all. I did, however, lose a good number of timered shows. Not that this will kill me, but personally I don't think VDR should quit operations because of such a "simple" problem. If there is an error in the channels.conf I see no reason to restart VDR more than once. If the conf file is defunct, then no number of restarts will bring it back to life ;o)) Personally, >>I<< think VDR should log such a problem and then display it on screen (I mean that's what the message bar is for ;o)) until the user aknowledeges that the message has been read. While I am at problem discussing, I also think that VDR should NOT delete a timer, if it wasn't possible to fully record the movie. (This can happen if diskspace runs low or if a thunderstrom prevents good reception, e.g.) Here, too, either keep the timer (even if the movie is over) or at least post a message in the message bar "Timer xyz + movie title" wasn't recorded. Keep up the display until it is aknowledged by the user. I know I haven't been posting recently (or doing any "nessy patches (insider for the older VDR users ;o))), but I still use and will continue to do so, only VDR as my method of recording and watching TV or beamer. @Klaus: Do you think the above would be possible? kind regards, Reinhard ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [input_vdr] H.264:-> pts 6957034094
Hi i use the vdr 170 + h264 patch + xineliboutput from cvs , on dvb-s2 channels I can see in logs these messages == Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957023294 Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957037694 <- 0 (DTS 6957026894) Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957030494 <- 0 Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957034094 == what are they mean ? is it possible to avoid their ? un 19 22:31:52 localhost vdr: [7040] switching to channel 4 Jun 19 22:31:52 localhost vdr: [7040] cTS2PES got 0 TS errors, 2 TS continuity errors Jun 19 22:31:52 localhost vdr: [7040] buffer stats: 169388 (8%) used Jun 19 22:31:52 localhost vdr: [7136] transfer thread started (pid=7040, tid=7136) Jun 19 22:31:52 localhost vdr: [7132] TS buffer on device 1 thread ended (pid=7040, tid=7132) Jun 19 22:31:52 localhost vdr: [7131] buffer stats: 122576 (5%) used Jun 19 22:31:52 localhost vdr: [7131] receiver on device 1 thread ended (pid=7040, tid=7131) Jun 19 22:31:52 localhost vdr: [7137] receiver on device 1 thread started (pid=7040, tid=7137) Jun 19 22:31:52 localhost vdr: [7138] TS buffer on device 1 thread started (pid=7040, tid=7138) Jun 19 22:31:52 localhost vdr: [7044] ERROR (dvbdevice.c,302): Invalid argument Jun 19 22:31:52 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2 Jun 19 22:31:52 localhost vdr: [7136] cVideoRepacker: operating in H.264 mode Jun 19 22:31:52 localhost vdr: [7136] [xine..put] cXinelibDevice::PlayVideo: Detected H.264 video Jun 19 22:31:52 localhost vdr: [7057] [input_vdr] H.264 scanner: Possible H.264 NAL AUD Jun 19 22:31:52 localhost vdr: [7057] [input_vdr] H.264: post pts 6957016094 Jun 19 22:31:52 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957016094 <- 0 (DTS 6957005294) Jun 19 22:31:52 localhost vdr: [7057] [input_vdr] Audio changed -> AC3 0 (BD:80) Jun 19 22:31:52 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957012494 <- 0 Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957026894 <- 0 (DTS 6957016094) Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957019694 <- 0 Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957023294 Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957037694 <- 0 (DTS 6957026894) Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957030494 <- 0 Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957034094 Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957048494 <- 0 (DTS 6957037694) Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957041294 <- 0 Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957044894 Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957059294 <- 0 (DTS 6957048494) Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957052094 <- 0 Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957055694 Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957070094 <- 0 (DTS 6957059294) Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957062894 <- 0 Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957066494 Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957080894 <- 0 (DTS 6957070094) Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957073694 <- 0 Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957077294 Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957091694 <- 0 (DTS 6957080894) Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957084494 <- 0 Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957088094 Jun 19 22:31:53 localhost vdr: [7136] [xine..put] H.264: Found NAL SPS at offset 6/2029 Jun 19 22:31:53 localhost vdr: [7136] [xine..put] H.264 SPS: profile_idc 77 Jun 19 22:31:53 localhost vdr: [7136] [xine..put] H.264 SPS: pic_width: 120 mbs Jun 19 22:31:53 localhost vdr: [7136] [xine..put] H.264 SPS: pic_height: 34 mbs Jun 19 22:31:53 localhost vdr: [7136] [xine..put] H.264 SPS: frame only flag: 0 Jun 19 22:31:53 localhost vdr: [7136] [xine..put] H.264 SPS: aspect_ratio_idc 1 Jun 19 22:31:53 localhost vdr: [7136] [xine..put] H.264 SPS: -> aspect ratio 1 / 1 Jun 19 22:31:53 localhost vdr: [7136] [xine..put] H.264 SPS: -> video size 1920x1088, aspect 1:1 Jun 19 22:31:53 localhost vdr: [7136] [xine..put] Detected video size 1920x1088 Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957102494 <- 0 (DTS 6957091694) Jun 19 22:31:53 localhost vdr: [7057] [input_vdr] H.264:-> pts 6957095294 <- 0 Jun 19 22:31:53 localhost vdr:
