(2013-01-04, 00:09)tdavis Wrote: (2013-01-03, 21:32)cfetzer Wrote: (2012-12-31, 23:35)tdavis Wrote: Ok, I've just tried to rebuild to RC2, and both PR's don't work, so it needs to be rebased.
Also found that when using VDPAU decoding under Nvidia, it runs fast; that's why my commercial skips under xbmc are too early.
Rebased both PRs so it should work again. When you're saying 'too early'. What does it mean? Seconds? Minutes?
The problem is that MythTV stores frame offsets, but XBMC needs time offsets and we convert them by multiplying the frame rate. If that is inaccurate it won't work properly.
It starts off on the first correctly, and as the recording plays, it jumps early; ie, if a commercials are at 10, 15, 20 and 25 minutes marks, the 10 minute commercial is correct, and the 15 starts at say 14:55, the 20 at 19:50, and etc. It gets worse the farther in you get into the recording.
This is a on NVIDIA ION/intel 330atom machine. I haven't tried it on a VAAPI based system yet, it's on my list of things to do.
There was this fix put in:
https://github.com/xbmc/xbmc/pull/1936 for something along those lines..
I've figured out what is wrong, but I have no idea how to correct it.
Myth is reporting in the DB that frame is fixed, for the whole recording. This is not true; using mplayer, I get these messages:
demux_mpg: 30000/1001fps NTSC content detected, switching framerate.
A:47551.5 V:47551.5 A-V: 0.041 ct: 0.070 2556/2529 27% 0% 1.0% 0 0
Warning! FPS changed 23.976 -> 29.970 (-5.994005) [4]
A:47557.6 V:47557.6 A-V: -0.003 ct: 0.119 2739/2710 27% 0% 1.0% 0 0
demux_mpg: 24000/1001fps progressive NTSC content detected, switching framerate.
A:47557.9 V:47557.9 A-V: 0.038 ct: 0.137 2747/2717 27% 0% 1.0% 0 0
demux_mpg: 30000/1001fps NTSC content detected, switching framerate.
A:47557.9 V:47557.9 A-V: 0.041 ct: 0.141 2748/2718 27% 0% 1.0% 0 0
Warning! FPS changed 23.976 -> 29.970 (-5.994005) [4]
A:47558.4 V:47558.4 A-V: 0.009 ct: 0.177 2763/2731 27% 0% 1.0% 0 0
demux_mpg: 24000/1001fps progressive NTSC content detected, switching framerate.
A:47559.4 V:47559.3 A-V: 0.042 ct: 0.229 2787/2755 27% 0% 1.0% 0 0
demux_mpg: 30000/1001fps NTSC content detected, switching framerate.
A:47559.4 V:47559.4 A-V: 0.044 ct: 0.233 2788/2756 27% 0% 1.0% 0 0
Warning! FPS changed 23.976 -> 29.970 (-5.994005) [4]
A:47563.4 V:47563.4 A-V: -0.006 ct: 0.287 2910/2875 27% 0% 1.0% 0 0
demux_mpg: 24000/1001fps progressive NTSC content detected, switching framerate.
A:47564.2 V:47564.2 A-V: 0.042 ct: 0.325 2931/2895 27% 0% 1.0% 0 0
demux_mpg: 30000/1001fps NTSC content detected, switching framerate.
A:47564.3 V:47564.2 A-V: 0.045 ct: 0.329 2932/2896 27% 0% 1.0% 0 0
Warning! FPS changed 23.976 -> 29.970 (-5.994005) [4]
A:47573.5 V:47573.5 A-V: -0.005 ct: 0.384 3210/3168 27% 0% 1.0% 0 0
demux_mpg: 24000/1001fps progressive NTSC content detected, switching framerate.
A:47595.8 V:47595.7 A-V: 0.041 ct: 0.562 3747/3705 27% 0% 1.0% 0 0
demux_mpg: 30000/1001fps NTSC content detected, switching framerate.
A:47595.8 V:47595.7 A-V: 0.049 ct: 0.566 3748/3706 27% 0% 1.0% 0 0
Warning! FPS changed 23.976 -> 29.970 (-5.994005) [4]
A:47596.1 V:47596.1 A-V: 0.025 ct: 0.592 3758/3714 27% 0% 1.0% 0 0
demux_mpg: 24000/1001fps progressive NTSC content detected, switching framerate.
A:47600.7 V:47600.7 A-V: 0.040 ct: 0.658 3871/3826 27% 0% 1.0% 0 0
demux_mpg: 30000/1001fps NTSC content detected, switching framerate.
A:47600.8 V:47600.7 A-V: 0.047 ct: 0.662 3872/3827 27% 0% 1.0% 0 0
Warning! FPS changed 23.976 -> 29.970 (-5.994005) [4]
A:47656.4 V:47656.4 A-V: -0.002 ct: 0.712 5541/5496 28% 0% 1.0% 0 0
Which means.. This is breaks everything, because the time stamps are calculated using a single frame rate for the whole recording, and this recording switches between 2 FPS as it plays (and strangely, it's not where on scene changes, but in the middle of a scene!)
So it keeps switching between 23.976 and 29.970 and then back.. which means by the time it gets to where Myth says a commercial should be, XBMC is claiming it's another 15 seconds of video!
This is recorded using a HDHomerun Prime, on Comcast, with cable card.. time to check and see if this occurring in the OTA recordings (HDHome Dual).
I just checked an OTA recording, and they do not have these frame rate changes; so Comcast & the Prime's are doing wierd.