[Freevo-tracker] [ freevo-Bugs-2829494 ] Geometry problem with 720x576 resolution

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Bugs item #2829494, was opened at 2009-07-30 10:03
Message generated for change (Comment added) made by highking81
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=446895&aid=2829494&group_id=46652

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: core
Group: 1.x svn (rel-1)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: HighKing (highking81)
Assigned to: Nobody/Anonymous (nobody)
Summary: Geometry problem with 720x576 resolution

Initial Comment:
I use Freevo with X11 (I run Freevo with the -fs switch) at a resolution of 720x576. This resolution is natively supported by the nvidia driver using s-video output. It is the only resolution configured, so X cannot use anything else.

As of Freevo 1.9.0, setting the geometry in freevo.conf to 720x576 doesn't work right anymore... the screen is simply not completely filled. I have to set the geometry to approximately 960x740 to see Freevo full screen again. Not too proper, but not a huge issue. This becomes an issue when playing video which are not exactly 720x576 resolution, since Freevo passes the geometry on to mplayer, which results in parts of the video displayed off screen.

So the actual question: Why doesn't Freevo fill the entire screen anymore when I set geometry to 720x576 while running X at that same resolution? Note that reverting back to 1.8.3 'solves' this... but that's not what I want ;-)

----------------------------------------------------------------------

>Comment By: HighKing (highking81)
Date: 2009-10-04 14:40

Message:
Hi,

Nice timing... yesterday evening we bought ourselves a nice 32" Samsung
LED tv. I can say, Freevo looks great in Full HD! ;-)
Since I seem to be the only one with the 720x576 resolution problem, I
guess it's not worth the effort to try to solve this issue anymore.

Michel

----------------------------------------------------------------------

Comment By: Duncan Webb (duncanwebb)
Date: 2009-10-04 13:43

Message:
Hi Michel,

Sorry not to have replied earlier, I'm completely stuck trying to
reproduce your problem. The code I sent you was the start up code of
freevo.

The only thing that you can do it to track down the revision number where
the problem started. But this is a lot of work and I fully understand if
you don't want to do this.

Basically with svn you can do this quite quickly using the divide and
conquer technique.

# cat freevo-1.8.3/src/revision.py 
__revision__ = '11210'
# cat freevo-1.9.0/src/revision.py 
__revision__ = '11576'

Start at r11393 using the formula first + (<last>-<first>)/2 so 11210 +
(11576-11210)/2 = 11393

svn co -r 11393 svn://svn.freevo.org/freevo/branches/rel-1/freevo
cd freevo
./freevo -f

Then if the problem already exists in this revision update to the earlier
revision, 11210 + (11393-11210)/2 = 11301.5

svn update -r 11301

Then if the problem does not exist in this revision then we know that the
problem was introduced between revisions 11393 and 11576 so update to the
later revision, 11393 + (11576-11393)/2 = 11484.5

svn update -r 11484

etc.

It will take 20 iterations before you find the revision where the problem
was introduced.

----------------------------------------------------------------------

Comment By: HighKing (highking81)
Date: 2009-08-21 16:10

Message:
Hi Duncan,

Sorry for the late response. I tried the patch, and ran 'freevo overscan'
from my .xinitrc. 
This is strange: The blue part completely fills the screen! I need just a
tiny bit of overscanning to get the green rectangle in the middle of the
screen.

Somehow this doesn't display on the screen the way Freevo itself does...

When I don't use any overscanning in my local_conf.py, and then run
Freevo, I see a big black border at the right and bottom of the screen, and
the left and top are a bit offscreen. When I set overscan_left to 80 and
top to 20 everything is on screen again, but the black borders still exist,
and have not changed in size. When I use a huge negative value for right
and bottom, the borders are still in place and the right and bottom parts
of Freevo are off-screen (under the black borders).

I tried to make a few photo's of it, but it's not that easy to photograph
a CRT-screen :-P

In the meantime I completely reïnstalled my system without any change. I
started my config from the clean local_conf.py.example to make sure it's
not because of some old config item... but without any luck. The problem
persists.
Already thinking about buying a flatscreen to 'solve' this... I can't be
the only one with this problem can I?

By the way, did I tell you this problem is only on X11? It's not there
when using the framebuffer... but since the framebuffer won't let me use a
720x576 resolution that's not an option to me... DVD's look awful at
800x600.
Using 800x600 in X works fine as well, but still: I just want to use
720x576 as it's perfectly well supported by both the video card (nvidia)
and the TV.

----------------------------------------------------------------------

Comment By: Duncan Webb (duncanwebb)
Date: 2009-08-13 19:43

Message:
Hi Michel,

Attached is a patch (for the
svn://svn.freevo.org/freevo/tags/REL-1_9_1/freevo) that will add a new
helper to show the display of screen. Run this from a xterm session as
"freevo overscan". You can then use the arrow keys to more a green
rectangle and will display the overscan settings when esc is pressed.

Over-scanning is only interesting when freevo is displayed on analogue
TVs.

Will you let me know the results from running this patch?

----------------------------------------------------------------------

Comment By: HighKing (highking81)
Date: 2009-08-11 19:49

Message:
Just took a few screenshots... not realy what I expected. When I set the
geometry to 720x576, the screenshot is exactly that! If I set it to
960x740, the screenshot is 960x740... strange... note that 1.8.3 still
filled the screen just fine, I haven't made any changes to xorg.conf and
the ONLY available resolution in xorg.conf is 720x576.

The convert_config helper outputted:
    changing config file line:                                            

    IMAGEVIEWER_ASPECT = (float(768) / float(720))                        

    OSD_PIXEL_ASPECT = (float(768) / float(720))           

I don't have the OSD_PIXEL_ASPECT setting in my local_conf.py though. I
tried adding it but if didn't make any difference.

I don't have OSD_FORCE_FONTNAME and OSD_FORCE_FONTSIZE in my config as
well.

Anything else I could try?

----------------------------------------------------------------------

Comment By: Duncan Webb (duncanwebb)
Date: 2009-08-11 18:26

Message:
Hi Michel,

These type of problems are difficult to resolve... but does sound like
there is a new bug there.

Will you press F10 and check the dimension of the image in the
/tmp/freevo_ss* do try this with the geometry set to 720x576 (and possibly
768x576)

Looking through the code from version 1.8.3 to 1.9.0 there doesn't seem to
be anything that would affect the resolution. Have you used the
convert_config helper to fix any updated settings?

The settings will now have a bigger influence on fonts and their sizes.

OSD_FORCE_FONTNAME = None
OSD_FORCE_FONTSIZE = 4.0 / 3.0

Do let us know the results of your screen shots images.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=446895&aid=2829494&group_id=46652