Difference between revisions of "Talk:Developer tips"

From WiiBrew
Jump to: navigation, search
(where does 678 come from for PAL widescreen?)
 
m
Line 7: Line 7:
 
Also TV pixels are [http://lurkertech.com/lg/pixelaspect/ non-square]. Any ideas?  
 
Also TV pixels are [http://lurkertech.com/lg/pixelaspect/ non-square]. Any ideas?  
 
[[User:CarstenK|CarstenK]] 19:28, 6 August 2008 (CEST)
 
[[User:CarstenK|CarstenK]] 19:28, 6 August 2008 (CEST)
 +
 +
: The 678 number was found by experimentation with my Widescreen LCD TV - 678 stretches the 640 pixel wide framebuffer to just touch the edge of my screen.  Other people's TVs may vary.  It doesn't have anything to do with a 16:9 aspect ratio, you still need to use the GX matrices to squash a 16:9 view into a 4:3 framebuffer. --[[User:Pepsiman|Pepsiman]] 14:37, 7 August 2008 (CEST)

Revision as of 13:37, 7 August 2008

Where does this number 678 come from to achieve a PAL 16:9 aspect ratio screen? I want to write similar code for NTSC.

#define VI_MAX_WIDTH_PAL            720
#define VI_MAX_HEIGHT_PAL           574

Looking at video_types.h I calculate 16*574/9 = 1020 for PAL and 16*480/9 = 852 NTSC EDTV. Also TV pixels are non-square. Any ideas? CarstenK 19:28, 6 August 2008 (CEST)

The 678 number was found by experimentation with my Widescreen LCD TV - 678 stretches the 640 pixel wide framebuffer to just touch the edge of my screen. Other people's TVs may vary. It doesn't have anything to do with a 16:9 aspect ratio, you still need to use the GX matrices to squash a 16:9 view into a 4:3 framebuffer. --Pepsiman 14:37, 7 August 2008 (CEST)