Re: [Freevo-users] OSD_OVERSCAN info needed

2007-09-09 Thread Stephen Rowles

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]:


 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
  Freevo-users@lists.sourceforge.net
 mailto:Freevo-users@lists.sourceforge.net
  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
  Freevo-users@lists.sourceforge.net
 mailto:Freevo-users@lists.sourceforge.net
  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
 Freevo-users@lists.sourceforge.net
 

Re: [Freevo-users] OSD_OVERSCAN info needed

2007-09-09 Thread Pirlouwi
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]:
 
 
  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
   Freevo-users@lists.sourceforge.net
  mailto:Freevo-users@lists.sourceforge.net
   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
   Freevo-users@lists.sourceforge.net
  mailto:Freevo-users@lists.sourceforge.net
   https://lists.sourceforge.net/lists/listinfo/freevo-users
  

Re: [Freevo-users] ivtv problem with HVR-1300

2007-09-09 Thread Pirlouwi
I can get fmt-video, but not set it.

[EMAIL PROTECTED]:~# v4l2-ctl --set-fmt-video=width=768,height=576
ioctl: VIDIOC_S_FMT
[EMAIL PROTECTED]:~# v4l2-ctl --get-fmt-video
Format:
Type  : Video Capture
Width/Height  : 320/240
Pixel Format  : BGR3
Field : Interlaced
Bytes per Line: 960
Size Image: 230400
Colorspace: Unknown ()

Will try some googling about this problem too.

Is there anything else that I could check in a bash shell to help me correct
my HVR-1300 problem?
PS: I can change the resolution of my HVR display in TVTIME application.
_Pirlouwi_


2007/9/9, Duncan Webb [EMAIL PROTECTED]:

 Pirlouwi wrote:
  I have seen in ivtv-devel mailing list:
 
 
  Re: [ivtv-devel] Hauppauge WinTV-HVR-1300 Milos Prudek Tue Mar
  13 12:13:23 2007
 
   is Hauppauge WinTV-HVR-300 card supported by ivtv? Are there any
 plans
   to support it?
 
  There is support for this card in the kernel (the cx88 driver). It is
 not
 
  yet completely stable as far as I know, so your mileage may vary.
 
 
  I have tried only one VideoGroup with record_group=None, but the error
  is still the same.
  What equivalent shell command could I try to test the setfmt() command
  that fails outside of python and freevo?
  In other words, it seems that the cx8800 is effectively an ivtv driver,
  but how can I detect what is wrong with this ioctl?

 r = fcntl.ioctl(self.device, i32(SET_FMT_NO), val)
 is equivalent to:
 v4l2-ctl --set-fmt-video
 and you should also check
 v4l2-ctl --get-fmt-video

 VIDIOC_S_FMT and VIDIOC_G_FMT are basic video4linux commands and should
 work for all cards.

 Duncan


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


Re: [Freevo-users] OSD_OVERSCAN info needed

2007-09-09 Thread Frank [Antispam account]
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; freevo-users@lists.sourceforge.net
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
  Freevo-users@lists.sourceforge.net
 mailto:  mailto:Freevo-users@lists.sourceforge.net
Freevo-users@lists.sourceforge.net
  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/
 

Re: [Freevo-users] ivtv problem with HVR-1300

2007-09-09 Thread Duncan Webb
 I can get fmt-video, but not set it.

 [EMAIL PROTECTED]:~# v4l2-ctl --set-fmt-video=width=768,height=576
 ioctl: VIDIOC_S_FMT

If you have connected this to a TV you will need to use 720x576 as the
pixels are not square on a TV (4:3 aspect has 1.06667:1) 720x1.0667 = 768.

Try this:
v4l2-ctl --set-fmt-video=width=720,height=576

 [EMAIL PROTECTED]:~# v4l2-ctl --get-fmt-video
 Format:
 Type  : Video Capture
 Width/Height  : 320/240
 Pixel Format  : BGR3
 Field : Interlaced
 Bytes per Line: 960
 Size Image: 230400
 Colorspace: Unknown ()

 Will try some googling about this problem too.

Then you may need to set your geometry to 320x240.

 Is there anything else that I could check in a bash shell to help me
 correct
 my HVR-1300 problem?
 PS: I can change the resolution of my HVR display in TVTIME application.

Colorspace seems a bit odd too.

Duncan


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


Re: [Freevo-users] OSD_OVERSCAN info needed

2007-09-09 Thread Duncan Webb
 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)

Not yet.

Duncan


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