Tim schrieb:
Am Mittwoch 18 Juni 2008 schrieb Frank Scherthan:
Hi
Hanno Zulla schrieb:
Is there an easy fix I could test right now? Can I disable the channel-checking?
Yes, you can. Check the DVB settings menu.
You are wrong. I am not talking about *updating channels*. I know about that and as a workaround, I switched it off. BUT: This is NOT what I am looking for.
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. ;)
It happens again today. So I made a quick fix.
Are you sure that your fix will increase the WAF ? I don't know if VDR works correctly with a "broken" channels list.
I prefer not to add broken channels. The patch does not help for channels that modify pids to a broken state, but prevents to add broken channels.
--- channels.c.org 2008-04-12 15:49:12.000000000 +0200 +++ channels.c 2008-06-18 12:20:17.000000000 +0200 @@ -1151,6 +1151,11 @@ NewChannel->CopyTransponderData(Transponder); NewChannel->SetId(Nid, Tid, Sid, Rid); NewChannel->SetName(Name, ShortName, Provider); + if(! NewChannel->GetChannelID().Valid()) { + esyslog("ERROR: new channel data results in invalid ID!"); + free(NewChannel); + return(NULL); + } Add(NewChannel); ReNumber(); return NewChannel;