Hi!
I observed that periodically appears lot of dashes in the console running my
vdr-1.7.9.
Probably this comes from this code in transfer.c:
if (cPlayer::IsAttached()) {
// Transfer Mode means "live tv", so there's no point in doing any additional
// buffering here. The TS packets *must* get through here! However, every
// now and then there may be conditions where the packet just can't be
// handled when offered the first time, so that's why we try several times:
for (int i = 0; i < 100; i++) {
if (PlayTs(Data, Length) > 0)
return;
fprintf(stderr, "-");//XXX just for testing - remove when stable
cCondWait::SleepMs(10);
}
esyslog("ERROR: TS packet not accepted in Transfer Mode");
}
In syslog sometimes the following can be found:
Sep 27 10:14:07 vdr vdr: [4806] ERROR: TS packet not accepted in Transfer Mode
Sep 27 11:22:02 vdr vdr: [5035] ERROR: TS packet not accepted in Transfer Mode
Sep 27 16:06:19 vdr vdr: [5168] ERROR: TS packet not accepted in Transfer Mode
Sep 27 20:52:02 vdr vdr: [5362] ERROR: TS packet not accepted in Transfer Mode
What does this mean? Is it TS handling problem in vdr or hardware related?
How bad is it and how to find the cause of this?
Can it be reason why sometimes recordings are corrupted?
I have 1 FF Nexus DVB-S (primary output device) and 2 DVB-C PCI cards on P4 HT
2.4GHz PC.
AK
_______________________________________________
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
