On Sat, Dec 22, 2012 at 4:53 PM, HP-mini <span dir="ltr"><<a href="mailto:blm-ubunet@slingshot.co.nz" target="_blank">blm-ubunet@slingshot.co.nz</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br></div>MythTV pre - 0.25 was jitter/judder free with refresh rate / video<br>
framerate mismatch.<br>
<br>
Your xorg.conf setup seems to be at odds with the judder-free wiki.<br>
The common use-case is bad EDID & requirement to force a VESA mode or<br>
custom modeline.<br>
<br></blockquote><div>My EDID is reported correctly, which is why I don't have detailed modelines. I used the 'Basic Configuration' section in the wiki. Plus according to the wiki itself, those don't even work in the 3xx drivers.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You are using EDID modes & no dynamic twinview.<br></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dynamic twinview is/was required to allow meta-mode unique (fake)<br>
refreshrate reporting to xrandr.<br></blockquote><div>That was the problem, I enabled dynamic twinview and the problem was fixed!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You are blocking VESA modes.<br></blockquote><div>I believe I set that to force X to use EDID modes.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You have no monitor section (no vert/horiz freq ranges)<br>
You have no screen in device section (prob not matter with one screen)<br></blockquote><div>I use X's autoconfiguration, since I know my monitor is detected correctly (I figured that out when I originally set this it up).</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
mythfrontend -v playback<br>
might provide better info.<br>
<br>
Can you run "nvidia-settings" & try each of the listed display<br>
resolutions & check what your TV reports.<br>
<br>
<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
</blockquote></div><br><div>Anyway, DynamicTwinView was the problem, once I enabled it the problem was resolved. I'm not sure why that worked in the older driver and not now. I didn't want to go back to the old driver because I was tired of the HDMI audio always breaking when X restarts.</div>
<div><br></div><div>Thanks for the help everyone!</div><div><br></div><div>Daniel</div>