Hi,<div>I'm using MythTV 0.25 on Arch linux with an Nvidia GT 430, and my playback set to use VDPAU for all recordings. I have a user job that transcodes all recordings to .mkv immediately after recording is finished.</div>
<div>My xorg.conf uses the option "CustomEDID" "DFP-1:/etc/X11/edid_Panasonic.bin" that I saved from nvidia-settings, and I only use 3 modes. 1080p@60Hz, 1080p@50Hz and 1080p@24Hz. </div><div><br></div>
<div>During playback (since upgrading to 0.25) I get what seems like a few frames dropping (judder) every 5-10 minutes when I view the playback with MythTV. However, I do not see the same problem when I view the same .mkv file with XBMC. Also, if I rewind the scene in MythTV and view it again I do not see the judder.</div>
<div><br></div><div>I ran the frontend with "mythfrontend -v playback --loglevel=debug > /home/david/MythTV/mythplayback20120520_082900.log" and around the time of the issue I get this:</div><div><br></div><div>
<div>2012-05-20 08:34:15.096448 I Player(0): FPS: 25.01 Mean: 39988 Std.Dev: 107 CPUs: 0% 3% </div><div>2012-05-20 08:34:15.498838 I AFD: Key frame distance changed from 46 to 47.</div><div>2012-05-20 08:34:19.015662 I Player(0): 7200 progressive frames seen.</div>
<div>2012-05-20 08:34:19.096445 I Player(0): FPS: 25.01 Mean: 39988 Std.Dev: 104 CPUs: 0% 1% </div><div>2012-05-20 08:34:19.978526 I AFD: Key frame distance changed from 47 to 112.</div><div>2012-05-20 08:34:21.976198 I AFD: Key frame distance changed from 112 to 50.</div>
<div>2012-05-20 08:34:23.096477 I Player(0): FPS: 25.01 Mean: 39988 Std.Dev: 103 CPUs: 0% 0% </div><div>2012-05-20 08:34:24.500470 I AFD: Key frame distance changed from 50 to 63.</div><div>2012-05-20 08:34:27.096472 I Player(0): FPS: 25.01 Mean: 39988 Std.Dev: 109 CPUs: 0% 1% </div>
<div>2012-05-20 08:34:30.817576 I AFD: Key frame distance changed from 63 to 158.</div><div>2012-05-20 08:34:31.096458 I Player(0): FPS: 25.01 Mean: 39988 Std.Dev: 105 CPUs: 0% 1% </div><div>2012-05-20 08:34:32.940184 I AFD: Key frame distance changed from 158 to 53.</div>
<div>2012-05-20 08:34:35.015671 I Player(0): 7600 progressive frames seen.</div><div>2012-05-20 08:34:35.096474 I Player(0): FPS: 25.01 Mean: 39988 Std.Dev: 105 CPUs: 1% 0% </div><div>2012-05-20 08:34:39.116440 I Player(0): FPS: 24.88 Mean: 40188 Std.Dev: 2008 CPUs: 0% 1% </div>
<div>2012-05-20 08:34:40.597611 I AFD: Key frame distance changed from 53 to 191.</div><div>2012-05-20 08:34:42.236107 I AFD: Key frame distance changed from 191 to 41.</div><div>2012-05-20 08:34:43.116450 I Player(0): FPS: 25.01 Mean: 39989 Std.Dev: 102 CPUs: 0% 0% </div>
<div>2012-05-20 08:34:43.839227 I AFD: Key frame distance changed from 41 to 40.</div><div>2012-05-20 08:34:45.276116 I AFD: Key frame distance changed from 40 to 36.</div><div>2012-05-20 08:34:47.116505 I Player(0): FPS: 25.01 Mean: 39988 Std.Dev: 101 CPUs: 0% 1% </div>
<div>2012-05-20 08:34:47.521747 I AFD: Key frame distance changed from 36 to 56.</div><div>2012-05-20 08:34:51.035625 I Player(0): 8000 progressive frames seen.</div><div>2012-05-20 08:34:51.116503 I Player(0): FPS: 25.01 Mean: 39988 Std.Dev: 117 CPUs: 0% 1%</div>
</div><div><br></div><div>How can I further diagnose what the issue might be?</div>