Overrides for specific video sizes ineffective

[[e-mail]]

In the "Video Mode Settings", there is an option to set "Overrides for specific video sizes". Nothing I set under here seems to have any effect.

I have it set to use 1366x768 @ 60Hz for the GUI and 1024x768 @ 75Hz for video output in general. This works. I want to match NTSC DVDs (720x480) and play these at 1366x768 @ 60Hz, using the override - this doesn't work.

I have "Separate video modes for GUI and TV playback" checked. If I change the settings for "Video Output" here, this is effective - I can make it play back at the different resolutions I want to use. So, I know that Myth is capable of switching to the resolution I want. However, I cannot make it override automatically by setting the override values underneath.

I am using mythfrontend 0.23.0+fixes24879-0ubuntu0+mythbuntu2

I have tried running from a console so I can see any output, but I can't see anything relevant.

I was able to get this to work on a previous box running earlier versions of MythTV.

[[e-mail] (tenminjoe)]

I have since found that I can accomplish something close to what I wanted, without using the overrides at all, by using the "Any" refresh rate, and letting Myth pick the appropriate video mode itself. This lets me watch NTSC DVDs at 60Hz, albeit at 1024x768 instead of 1366x768. It's not as if the DVDs themselves have enough resolution for that difference to matter.

However, whilst I am now happy, it does still seem to me like the override feature isn't working properly.

[melenzb (woodhouser)]

I confirm this bug on 23.1 updated today 29aug 2010 from weekly build.

I would like my mythbox to output different resolutions for different content because my bravia full hd tv does a much better job of scaling than mythtv does. I hoped to achieve this with Overrides for specific video sizes , but it is indeed ineffective.

I hope someone will fix this soon.

[Thomas Mashos (tgm4883)]

We really do appreciate you opening this ticket to help improve Mythbuntu, but it needs to be closed for a number of reasons. The biggest one is that upstream believes this to be fixed in the latest version. Could you please verify if this issue still exists in the latest version?

Please do not let the closing of this ticket dissuade you from opening a new ticket if this (or any other) problem occurs with the newer versions.