Duncan,
 
Can you tell when (i'm not trying to push you) this patch is in SVN or how I
can check when it is (by viewing the status of the tracker or something)
 
Thanks,
Frank


  _____  

Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Namens Pirlouwi
Verzonden: 09 September 2007 14:45
Aan: Stephen Rowles; [email protected]
Onderwerp: Re: [Freevo-users] OSD_OVERSCAN info needed


I just posted the patch to the freevo tracker on sourceforge, trying to
follow the contribution rules as close as possible (first time, fear to
forgot something, huh... :-)
I've followed the advice of Duncan for the variables names, because as they
are people that are maintaining the code, any modification should be easier
to read for them if it respects their logic. 

Happy to gave you help.
Bye
_Pirlouwi.


2007/9/9, Stephen Rowles <[EMAIL PROTECTED]>: 


This patch works great for me :)

TV positioning is now spot on - thank you!


Pirlouwi wrote:
> Sorry,
> I forgot to mention that the two variables defined inside local_conf.py :
> OSD_OVERSCAN_X 
> OSD_OVERSCAN_Y
> have to be replaced by:
> OSD_OVERSCAN_X1
> OSD_OVERSCAN_X2
> OSD_OVERSCAN_Y1
> OSD_OVERSCAN_Y2
> X1 represents the screen left shift
> X2 represents the screen right shift 
> Y1 represents the screen upside shift
> Y2 represents the screen bottom shift.
>
> In my config, the values are:
> OSD_OVERSCAN_X1 = 40
> OSD_OVERSCAN_X2 = 65
> OSD_OVERSCAN_Y1 = 35 
> OSD_OVERSCAN_Y2 = 35
> which places the freevo screen exactly on the right position on my CRT
> television, except that it does not work for image viewing. The images
> are still cut, and the OSD_OVERSCAN feature do not change this fact. 
>
> _Pirlouwi.
>
>
> 2007/9/8, Pirlouwi <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>:
>
>     Hello Stephen,
>
>     I have the same problem at home, and I wrote for that a little
>     patch for freevo 1.7.1, which I adapted to 1.7.3. Here it is (in
>     attachment). Could you test it on your configuration? 
>
>     I think I discovered a little bug, which I already have corrected
>     in my patch :
>
>     in /skins/main/xml_skin.py
>          def rect(self, type):
>              if type == 'screen': 
>                 return (self.x - config.OSD_OVERSCAN_X, self.y -
>     config.OSD_OVERSCAN_X,
>
>     I think that the second occurrence of OSD_OVERSCAN_X should be
>     replaced by OSD_OVERSCAN_Y, to be coherent with self.y.
>
>     _Pirlouwi.
>
>     2007/8/14, Stephen Rowles <[EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]  <mailto:[EMAIL PROTECTED]> >>:
>
>
>         The problem is this is TV out - not VGA. Its not a simple case of
>         tweaking with xvidtune a small fraction and having the monitor
>         re-sync.
>         I've tried vid tune and all I get is horribly non-synced 
>         output, and the
>         danger of damaging my TV ;)
>
>
>         Rob Shortt wrote:
>         > Guys, you need to find a way to adjust your modeline in X or
>         framebuffer 
>         > (whichever you use).  The screen positioning is controlled
>         there.  The
>         > easiest way to do this in X is (was at least) to use
>         xvidtune, tweak it,
>         > and capture the new parameters to use.
>         >
>         > -Rob
>         >
>         > P.S. - For some info on overscan see
http://scanline.ca/overscan/
>         >
>         > P.P.S. - Sorry for top-posting. :)
>         >
>         > John Molohan wrote:
>         >
>         >> Frank [Antispam account] wrote: 
>         >>
>         >>> Me too!
>         >>>
>         >>> Anyone got an idea in which file I need to edit to add this
>         >>> code/functionality? 
>         >>>
>         >>> Thanks,
>         >>> Frank
>         >>>
>         >> Not me but a grep for the overscan settings might show you
>         that code and 
>         >> put you on the right track.
>         >>
>         >> John
>         >>
>         >>
>
------------------------------------------------------------------------- 
>         >> This SF.net email is sponsored by: Splunk Inc.
>         >> Still grepping through log files to find problems?  Stop.
>         >> Now Search log events and configuration files using AJAX and 
>         a browser.
>         >> Download your FREE copy of Splunk now >>
>         http://get.splunk.com/
>         >> _______________________________________________ 
>         >> Freevo-users mailing list
>         >> [email protected]
>         <mailto:  <mailto:[email protected]>
[email protected]>
>         >> https://lists.sourceforge.net/lists/listinfo/freevo-users
>         >> 
>         >
>         >
>         >
------------------------------------------------------------------------
>
>         >
>         >
------------------------------------------------------------------------- 
>         > This SF.net email is sponsored by: Splunk Inc.
>         > Still grepping through log files to find problems?  Stop.
>         > Now Search log events and configuration files using AJAX and 
>         a browser.
>         > Download your FREE copy of Splunk now >>  http://get.splunk.com/
>         >
------------------------------------------------------------------------ 
>
>         >
>         > _______________________________________________
>         > Freevo-users mailing list
>         > [email protected]
<mailto:[email protected]> 
>         <mailto:[email protected]>
>         > https://lists.sourceforge.net/lists/listinfo/freevo-users
<https://lists.sourceforge.net/lists/listinfo/freevo-users> 
>         <https://lists.sourceforge.net/lists/listinfo/freevo-users>
>         >
>
>
>
------------------------------------------------------------------------- 
>         This SF.net email is sponsored by: Splunk Inc.
>         Still grepping through log files to find problems?  Stop.
>         Now Search log events and configuration files using AJAX and a
>         browser. 
>         Download your FREE copy of Splunk now >>  http://get.splunk.com/
>         _______________________________________________
>         Freevo-users mailing list 
>         [email protected]
>         <mailto:[email protected]
<mailto:[email protected]> >
>         https://lists.sourceforge.net/lists/listinfo/freevo-users
>         <  <https://lists.sourceforge.net/lists/listinfo/freevo-users>
https://lists.sourceforge.net/lists/listinfo/freevo-users>
>
>
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------- 
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
<http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/> 
> ------------------------------------------------------------------------
>
> _______________________________________________
> Freevo-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/freevo-users
>




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Freevo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freevo-users

Reply via email to