Reply to thread

Message

<blockquote data-quote="mrceolla" data-source="post: 800018" data-attributes="member: 109048">Hello,Sorry for the delay in reply.&nbsp; These two issues do seem related but mm is right, it is the overscan adjustments that don't get re-applied in my situation.&nbsp; I usually do not switch inputs while video is playing but will try that when I get home today.As for the timing of things, I do not remember exactly when I switched the input back to MP on that day.&nbsp; I was going to reproduce the problem again last night while paying attention to time but of course it didn't happen this time.&nbsp; I'd say it happens about 80% of the time...perhaps more.What I can tell you is that I exited MP right away after it occurred and then gathered up the logs.&nbsp; I believe it would have been one of:18:06:0418:06:05I think the other times are when my TV is turned on or off but the input is not set to MP.17:04:22 - got home (TV on, set to previous DTV channel)17:11:29 - left for a quick run (TV off)17:45:16 - got back from quick run (TV on, set to previous DTV channel)18:06:04 - switched TV input to MP18:06:05 - ???&nbsp;I didn't want to confuse things but I am using an HDMI switcher between MP and my TV.&nbsp; The switcher is turned on/off along with my TV and receiver.Even if there are brief resolutions changes or resyncing, it would seem that MP could be programmed to 'ignore' these things or at least attempt to re-apply the overscan settings once these events are over.I will try to get you that xml file tonight.&nbsp; Additionally I will set to debug and try to reproduce the problem.Thank you for your continued help.&nbsp; I greatly appreciate it.Have a great day!Mike</blockquote>

[QUOTE="mrceolla, post: 800018, member: 109048"] Hello, Sorry for the delay in reply. These two issues do seem related but mm is right, it is the overscan adjustments that don't get re-applied in my situation. I usually do not switch inputs while video is playing but will try that when I get home today. As for the timing of things, I do not remember exactly when I switched the input back to MP on that day. I was going to reproduce the problem again last night while paying attention to time but of course it didn't happen this time. I'd say it happens about 80% of the time...perhaps more. What I can tell you is that I exited MP right away after it occurred and then gathered up the logs. I believe it would have been one of: 18:06:04 18:06:05 I think the other times are when my TV is turned on or off but the input is not set to MP. 17:04:22 - got home (TV on, set to previous DTV channel) 17:11:29 - left for a quick run (TV off) 17:45:16 - got back from quick run (TV on, set to previous DTV channel) 18:06:04 - switched TV input to MP 18:06:05 - ??? I didn't want to confuse things but I am using an HDMI switcher between MP and my TV. The switcher is turned on/off along with my TV and receiver. Even if there are brief resolutions changes or resyncing, it would seem that MP could be programmed to 'ignore' these things or at least attempt to re-apply the overscan settings once these events are over. I will try to get you that xml file tonight. Additionally I will set to debug and try to reproduce the problem. Thank you for your continued help. I greatly appreciate it. Have a great day! Mike [/QUOTE]

Verification