2005-07-03, 03:01
sweet dude, worked like a charm. i forgot to define ntsc_4x3 at the beginning of the script. cheers dude :kickass:
2005-07-03, 18:40
jonathan,
i was playing with this some more and it appears the list control does not scale height, it scales position and width only.
i was playing with this some more and it appears the list control does not scale height, it scales position and width only.
2005-07-18, 22:41
hi jonathan,
i just thought that this functionality could solve the overscan problems my tv has with some scripts.
do you think that there could be a setting to set the scaled resolution to the video calibration setting? im hoping it's as simple as that. thanks so much!
-ast
/fellow jonathan irl (-:
i just thought that this functionality could solve the overscan problems my tv has with some scripts.
do you think that there could be a setting to set the scaled resolution to the video calibration setting? im hoping it's as simple as that. thanks so much!
-ast
/fellow jonathan irl (-:
Add yourself to the xbmc forums frappr map!
Collection of XBMC and Python resources - Screensaver Megapack
Collection of XBMC and Python resources - Screensaver Megapack
2005-12-08, 20:42
given the tight real estate i vote to un stickify this thread.
Add yourself to the xbmc forums frappr map!
Collection of XBMC and Python resources - Screensaver Megapack
Collection of XBMC and Python resources - Screensaver Megapack
2006-01-18, 03:25
hi jonathan,
i've just been able to play with self.setcoordinateresolution(ntsc_4x3) on 720p resolution.
to get controlimages to scale so they look close to the original i had to use this formula. it's probably not exact, but it looks alot better. the .91 is from dividing the 4:3 pixel ratio compared to the 1:1 of 720p.
should your code do this automatically, it appears the list control is scaling correctly.
the 1st picture is 720p with the formula, the second is 720p without the formula and the 3rd is the original at 480ntsc
i've just been able to play with self.setcoordinateresolution(ntsc_4x3) on 720p resolution.
to get controlimages to scale so they look close to the original i had to use this formula. it's probably not exact, but it looks alot better. the .91 is from dividing the 4:3 pixel ratio compared to the 1:1 of 720p.
Quote:self.padw = int(float((300 / 4)* 3 / .91))
should your code do this automatically, it appears the list control is scaling correctly.
the 1st picture is 720p with the formula, the second is 720p without the formula and the 3rd is the original at 480ntsc
2006-01-18, 04:57
i don't think so, no.
the problem is basically the aspect ratio changes. if i did this then anything full screen in 4x3 wouldn't be fullscreen in 720p (and vice-versa).
images are the only thing this really effects (ie size of dialog boxes is not as much of an issue) and the <keepaspectratio> tag in the skin (and i think you can set this from python as well?) takes care of that.
the skin uses 2 resolutions (pal and pal16x9) as the base for exactly this reason, and i don't think there's an easy way to do any automatic conversion.
you could probably do it on the fly by setting the window coordinate system to be ntsc16x9 rather than ntsc if using a widescreen mode?
any ideas are welcome
cheers,
jonathan
the problem is basically the aspect ratio changes. if i did this then anything full screen in 4x3 wouldn't be fullscreen in 720p (and vice-versa).
images are the only thing this really effects (ie size of dialog boxes is not as much of an issue) and the <keepaspectratio> tag in the skin (and i think you can set this from python as well?) takes care of that.
the skin uses 2 resolutions (pal and pal16x9) as the base for exactly this reason, and i don't think there's an easy way to do any automatic conversion.
you could probably do it on the fly by setting the window coordinate system to be ntsc16x9 rather than ntsc if using a widescreen mode?
any ideas are welcome
cheers,
jonathan
Always read the XBMC online-manual, FAQ and search the forum before posting.
Do not e-mail XBMC-Team members directly asking for support. Read/follow the forum rules.
For troubleshooting and bug reporting please make sure you read this first.
Do not e-mail XBMC-Team members directly asking for support. Read/follow the forum rules.
For troubleshooting and bug reporting please make sure you read this first.
2006-01-18, 19:33
thanks jonathan,
getresolution() and then setcoordinateresolution() to ntsc or ntsc_16x9 based on if getresolution() is a widescreen result works. i'll test more, but it worked for 720p.
getresolution() and then setcoordinateresolution() to ntsc or ntsc_16x9 based on if getresolution() is a widescreen result works. i'll test more, but it worked for 720p.
