Re: Instability with recordings on VDR-1.7.4 when recording to a NTFS partition

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 22.03.2009 12:39, Niedermeier Günter wrote:
>> Strange - the code for actually writing the index file hasn't changed
>> between PES and TS recording. But maybe you can take a closer look at
>> the changes to cIndexFile between version 1.7.2 and 1.7.3.
> 
> Possibly you may want to have a look to my logfile,
> while the error occurs:
> 
> ----snip----------------------------------------------------------------
> Mar 22 12:25:06 vdr-142 vdr: [23234] record 
> /video0/@Wintersport/2009-03-22.12.25.2-0.rec
> Mar 22 12:25:06 vdr-142 vdr: [23234] creating directory /video0/@Wintersport
> Mar 22 12:25:06 vdr-142 vdr: [23234] creating directory 
> /video0/@Wintersport/2009-03-22.12.25.2-0.rec
> Mar 22 12:25:06 vdr-142 vdr: [23234] recording to 
> '/video0/@Wintersport/2009-03-22.12.25.2-0.rec/00001.ts'
> Mar 22 12:25:06 vdr-142 vdr: [2257] recording thread started (pid=23234, 
> tid=2257)
> Mar 22 12:25:06 vdr-142 vdr: [2258] receiver on device 2 thread started 
> (pid=23234, tid=2258)
> Mar 22 12:25:06 vdr-142 vdr: [2259] TS buffer on device 2 thread started 
> (pid=23234, tid=2259)
> Mar 22 12:25:08 vdr-142 vdr: [23234] replay 
> /video0/@Wintersport/2009-03-22.12.25.2-0.rec
> Mar 22 12:25:08 vdr-142 vdr: [23234] playing 
> '/video0/@Wintersport/2009-03-22.12.25.2-0.rec/00001.ts'
> Mar 22 12:25:09 vdr-142 vdr: [2260] dvbplayer thread started (pid=23234, 
> tid=2260)
> Mar 22 12:25:09 vdr-142 vdr: [2261] non blocking file reader thread 
> started (pid=23234, tid=2261)
> Mar 22 12:25:11 vdr-142 vdr: [23234] timer 1 (2 1225-1525 
> '@Wintersport') set to event Son 22.03.2009 13:05-15:00 (VPS: 22.03 
> 10:15) 'Wintersport'
> Mar 22 12:25:14 vdr-142 vdr: [2258] buffer usage: 70% (tid=2257)
> Mar 22 12:25:14 vdr-142 vdr: [2258] buffer usage: 60% (tid=2257)
> Mar 22 12:25:14 vdr-142 vdr: [2258] buffer usage: 70% (tid=2257)
> Mar 22 12:25:15 vdr-142 vdr: [2258] buffer usage: 80% (tid=2257)
> Mar 22 12:25:16 vdr-142 vdr: [2258] buffer usage: 90% (tid=2257)
> Mar 22 12:25:17 vdr-142 vdr: [2258] buffer usage: 100% (tid=2257)
> Mar 22 12:25:17 vdr-142 vdr: [2258] ERROR: 1 ring buffer overflow (65 
> bytes dropped)
> Mar 22 12:25:23 vdr-142 vdr: [2258] ERROR: 19932 ring buffer overflows 
> (3747216 bytes dropped)
> Mar 22 12:25:29 vdr-142 vdr: [2258] ERROR: 21852 ring buffer overflows 
> (4108176 bytes dropped)
> Mar 22 12:25:35 vdr-142 vdr: [2258] ERROR: 19089 ring buffer overflows 
> (3588732 bytes dropped)
> ----snap----------------------------------------------------------------
> 
> BTW:
> I just tried to replay this recording using vlc, and the TS file is also
> corrupted. Not only the index file stops, the ts file is also defect.

Well, if there are buffer overflows and the TS data is corrupted, it's
no wonder the index file stops growing.

Does this happen on all channels, or only on some (or even only on a
particular one)?

Klaus

_______________________________________________
vdr mailing list
vdr@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


[Index of Archives]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Big List of Linux Books]     [Fedora Users]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux