Originally Posted by rnissl
The file plays well with xine and mplayer when using vdpau or software decoding. There are no noticeable decoding artefacts or something like that. Sometimes, the call takes longer than 13 * 40 ms in xine which causes an underrun in xines video output queue and hence a few dropped frames in the video sequence, though without decoding errors.
Just wanted to add some further numbers from watching H.264 live TV in xine:
================= 12:59:58.880 WATCHDOG 35 ms: vdp_decoder_render returned after 894.750 ms =================
vi: (5000, 1080, 3919), ai: (2300, 0, 2300), vo: (30, 0, 13), ao: (32, 25, 7)
0 in the vo log line means, that there are no more frames ready for displaying in the video output queue (under run). As mentioned before, this is noticeable, as decoded frames after the delay get dropped to catch up with output time line.
================= 13:42:39.404 WATCHDOG 35 ms: vdp_decoder_render returned after 110.619 ms =================
vi: (5000, 576, 4423), ai: (2300, 0, 2300), vo: (30, 10, 2), ao: (32, 26, 6)
10 in the vo log line means, that there are still 10 frames ready for displaying in the video output queue (usually 13 frames are ready, so the queue level delta is 3 frames; the delay matches almost 3 * 40 ms). Hence, there is no noticeable effect (frame drop) of this delay.
Please find attached the xine-lib watchdog patch for creating the above WATCHDOG messages.