2012-01-10, 19:26
Glad to hear some progress. I've been watching that ticket# but haven't seen any notes to it.
FernetMenta Wrote:We have not figured out yet what messes up the timestamps. I guess the problem is related to ffmpeg. As I said earlier the problem has been there in Dharma as well but did not show that much.
This patch does not really fix the problem it only alleviates the symptoms a bit.
https://github.com/FernetMenta/xbmc/comm...f2488de037
You can compile from source and apply this patch until we have found the root cause.
Quote:We have not figured out yet what messes up the timestamps. I guess the problem is related to ffmpeg.
Quote:On atsc, I've seen some channels change framerates on the fly.
Ie: a prgram can be 23.976 and the the ads come up and they're 59.94 for example.
Related? How does xbmc cope with that?
FernetMenta Wrote:The patch does not fix this, it just excludes the timestamps of every second field from the pattern detector. The source of the problem is the input stream. Why has it those gaps? It might be a problem of your HDPVR. I don't think that the stream is broadcasted this way. Do you have a chance to record the same channel with your HDPVR and a different device.
Quote:This occurs due to Windows Media Center resetting the video pipeline when a frame rate change occurs. Each time a frame rate change occurs, it may take a few frames for the video to recover. However, when frequent frame rate changes occur, video appear to constantly stutter or "glitch" without smoothing out.
This problem occurs when broadcasts frequently switch between interlaced and progressive content. Progressive content is shown at 59.94 frames per second (fps) while interlaced content is shown at 29.97 fps. This problem has also been seen when a broadcaster incorrectly flags their content. For instance, interlaced content is incorrectly flagged as progressive content.