<div dir="ltr">Hi<br><div class="gmail_extra"><br><br><div class="gmail_quote">On 16 April 2013 23:05, Paul Gardiner <span dir="ltr"><<a href="mailto:lists@glidos.net" target="_blank">lists@glidos.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm now on 313.30, so maybe I wont have the problem now (yet to<br>
experiment), but what I was<br>
seeing (as were others): if you activate "Separate video modes for GUI and TV playback", but don't set up any "Overrides for specific video<br>
sizes" then the mode is set on every transition between GUI and<br>
playback. The patch seemed to fix it, and not by forcing a single<br></blockquote><div><br></div><div>That's how I have mine set up.<br></div><div>Separate video modes is checked, the resolution is set to 1920x1080 and the refresh rate set to auto. No other overrides.<br>
<br></div><div>The refresh rate change from the default 50Hz in GUI to the refresh rate for the video being played; 24Hz, 60Hz whatever.<br><br></div><div>I have noticed that sometimes during Video->GUI it doesn't revert back to the original 50Hz. Which doesn't bother me as my frontends are machines dedicated to myth and as such, I had very little incentive to look at fixing it.<br>
<br></div><div>What I don't understand is what exactly is your problem? That setting is designed for the mode to be changed going from GUI to playback.<br><br></div><div>You're saying that it changes even if say GUI is currently at 50Hz and you try to play a 50Hz video? and that shouldn't happen?<br>
<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
refresh rate, because I'd still see a mode change if transitioning<br>
from playback => gui =>playback if the two playbacks were for different<br>
rates.<br></blockquote><div><br></div><div>but that's intended... <br><br></div><div>I guess I must be missing something.. Because I just don't get what the problem is.<br><br></div><div>if you run mythfrontend with -v playback --loglevel debug<br>
</div><div>You see that when I start playback from GUI, then myth issues request for one change only, to the mode matching what the video that is about to play would use.<br></div><div> <br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
One quick question: when some part of MythTV wants current video mode<br>
information, does it enquire of the system, or does it use cached<br>
information from when it last set the mode itself? I sometimes see<br>
signs that it does the former, and would be better doing the latter.<br>
I wonder whether perhaps requests for mode changes don't have effect<br>
immediately, and queries too soon after a change request come back<br>
with the old mode rather than the new mode.<br></blockquote><div><br></div><div>it starts believing that the current mode is "0", then set to whatever you asked the system to be. From that point on, that's the current mode (m_last) as opposed to what's coming ("next" in the code)<br>
<br></div><div>myth doesn't cache anything from a previous run, it's always within the current lifespan of the myth process<br><br></div><div>Not sure if that answer your questions, but I'm not sure I fully understand it :)<br>
<br></div></div></div></div>