Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#8113 closed defect (fixed)

LiveTV gets horizontally shifted after EPG

Reported by: Antonio Marcos López Alonso <amlopezalonso@…> Owned by: markk
Priority: minor Milestone: unknown
Component: MythTV - General Version: 0.22-fixes
Severity: medium Keywords: EPG, overscan, offset
Cc: Ticket locked: no


I had to modify Mythfrontend GUI resolution and horizontal offset, and also LiveTV overscan using MythTV internal controls for such task. Then whenever I'm watching LiveTV and get into EPG, returning to LiveTV gives an horizontally shifted video, leaving a black (letterboxing) vertical bar on the left side. Iterating the process gives a further displaced video and thus a wider bar.

To trigger the bug you must: a) Setup --> Appearance --> move to the GUI page and give GUI horizontal offset a positive, non-zero value (mine is 62). b) Go to LiveTV. The image appears normal. c) Enter EPG and change channel from there. d) LiveTV appears --wrongly-- shifted to the right side of the screen. e) To reset the shifting you must quit LiveTV and re-enter.

To avoid the bug you must set GUI horizontal offset to zero.

Regards, Antonio

Change History (4)

comment:1 Changed 10 years ago by barry@…

I have a similar problem, I have GUI width, height, x and y offset values non-zero. The problem only occurs when "Use GUI size for TV playback" is NOT selected (i.e. you want TV to overscan, but not the mythtv GUI).

When going into "Live TV" there is a noticeable shift toward the top left of the interface just before the video starts, when going into the EPG there is an opposite shift of the same amount. When leaving the EPG, no shift occurs which is presumably what is causing this offset.

I'm posting this report whilst using Mythfrontend version: branches/release-0.22-fixes (23604)

comment:2 Changed 10 years ago by robertm

Owner: changed from Isaac Richards to markk
Status: newassigned

comment:3 Changed 10 years ago by markk

Resolution: fixed
Status: assignedclosed

The only remaining issue I could find in trunk was fixed in r26295

comment:4 Changed 10 years ago by amlopezalonso@…

Sorry but I upgraded to 0.24 (26340) and this problem is still alive and kicking, so I have to kindly request to reopen this bug.

Regards, Antonio

Note: See TracTickets for help on using tickets.