[mythtv-users] Issues with playback - 0.24-fixes - vdpau

Greg Oliver oliver.greg at gmail.com
Tue Dec 7 05:16:39 UTC 2010


I have seen skips/snags/micro-freezes whatever you want to call them
(a lot like those described frequently with 0.24), so tonight I have
been watching with a detailed log rolling beside me.

When it happened I noticed something interesting (although I do not
know what it means):

'video_output' mean = '33368.09', std. dev. = '28.59', fps = '29.97'
2010-12-06 23:02:15.217 Player(3): Video is 3.20626 frames behind
audio (too slow), dropping frame to catch up.
2010-12-06 23:02:15.217 Player(3): Video is 3.38623 frames behind
audio (too slow), dropping frame to catch up.
2010-12-06 23:02:15.237 Player(3): Video is 3.27393 frames behind
audio (too slow), dropping frame to catch up.
2010-12-06 23:02:15.237 Player(3): Video is 3.08482 frames behind
audio (too slow), dropping frame to catch up.
'video_output' mean = '33869.57', std. dev. = '20534.40', fps = '29.53'
'video_output' mean = '33368.11', std. dev. = '34.81', fps = '29.97'
'video_output' mean = '33368.87', std. dev. = '22.40', fps = '29.97'

No matter how I try, I cannot get the 20534.40 number to compute with
anything I can think of.  I am sure it does, but this is exactly when
it happened.  The machine is not taxed at all during this, I have
mythfrontend assigned 2 cores each running at 2.86GHz, with all other
processes running on other cores.  I have nvidia's gpu (gt220) set to
performance mode.

Tasks: 314 total,   2 running, 312 sleeping,   0 stopped,   0 zombie
Cpu0  :  0.0%us,  0.0%sy,  7.8%ni, 92.2%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu1  :  0.0%us,  0.0%sy,  2.0%ni, 98.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu2  :  1.9%us,  1.9%sy,  7.7%ni, 84.6%id,  3.8%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu3  :  0.0%us,  0.0%sy,  2.0%ni, 98.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu4  :  0.0%us,  0.0%sy, 94.1%ni,  5.9%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu5  :  0.0%us,  2.0%sy,  0.0%ni, 90.2%id,  7.8%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu6  :  1.9%us,  1.9%sy,  5.8%ni, 90.4%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu7  :  0.0%us,  0.0%sy,  0.0%ni,100.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   3857392k total,  3702420k used,   154972k free,     5468k buffers
Swap:  8191992k total,    46816k used,  8145176k free,  2544944k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
18808 greg      37  17  895m 227m  19m S 96.5  6.0   0:19.13
mythcommflag
18578 greg      37  17  717m  34m 3716 S 11.8  0.9   7:04.58
mythcommflag
18477 greg      37  17  718m  33m 3704 S  7.9  0.9   5:16.59
mythcommflag
18600 greg      37  17  717m  34m 3720 S  5.9  0.9   5:12.55
mythcommflag
 2485 greg      20   0 3181m  54m 3356 S  3.9  1.5  12:13.61
mythbackend
17796 greg      20   0 2676m 278m  30m S  2.0  7.4   2:44.51 mythfrontend

mythfrontend is nailed to cpu 6&7 there..  As you can see mythcommflag
is churning away, but the i/o waits are still quite low, so I know the
system is not starved.  Also, from the low number of frames it says it
had to drop in that 20th of a second, it should not have been as
noticeable like it was.  Anyone have any ideas or solutions?  I just
upgraded this machine last weekend to 0.24, and this was definitely
not happening with 0.23  .?.?.?

I see other posts like this with no resolution as of yet that I can
see.  I was getting the same OSD glitches as well, but those seemed to
iron themselves out as soon as the automatic run of the metadagrabber
stopped.  It is now only *jerky* after a video has been playing a
while and the OSD is requested here.

Thanks

-Greg


More information about the mythtv-users mailing list