well I hope thats not the case, because theres no way I could read anything without things set to large (a 37" 1080p monitor, from about 8 feet away), so this will be something that stops me from using MediaPortal, unfortunately. Although what's really weird for me is that if I start a bunch of different files, after a while the video will return.
Problem viewing movies in fullscreen (stretch-mode) (1 Viewer)
- Thread starter tricke
- Start date
I get the impression this is limited to nvidia chip owners. Is this correct?
By the way, I only had to set the fontsize back to normal again. No reinstall was needed in my case. Fortunately my htpc is dedicated, so I rarely have to work outside MP and I can live with it.
The only workaround I can come up with would be to switch themes on the fly. Create a custom theme with big fonts for normal use, and switch to the standard one before starting MP. Should not be that difficult to script. Or maybe using one of those keypress/macro/automation utilities.
[edit] it seems there are commandline theme switchers available. I found one here.
No idea if it works, but there must be others around if not.
By the way, I only had to set the fontsize back to normal again. No reinstall was needed in my case. Fortunately my htpc is dedicated, so I rarely have to work outside MP and I can live with it.
The only workaround I can come up with would be to switch themes on the fly. Create a custom theme with big fonts for normal use, and switch to the standard one before starting MP. Should not be that difficult to script. Or maybe using one of those keypress/macro/automation utilities.
[edit] it seems there are commandline theme switchers available. I found one here.
No idea if it works, but there must be others around if not.
I can confirm the problem still exists, except with a twist - I use a radeon 9550 card, not NVidia.
I have tried this on two seperate machines, both with the same model card, both before and after a fresh install of v0.2, and tested again after the v0.2.3 update on both machines.
I also tried a couple of different Radeon driver sets, which also made no difference.
I can also confirm that the "fix" (if you can call it that) is to change windows default font size back to normal. I had mine set to 140% or 134 DPI. Viewing the fullscreen video on "Original" aspect ratio also works regardless of the font size, but viewing vids like this is far from ideal.
Furthermore, the fullscreen video WAS displaying normally after a v0.2RC2 upgrade to v0.2.
It was only after I was forced to uninstall and reinstall MP to clear out any older CVS/SVN's that the problem presented.
As far as I'm concerned, this is a major bug. I'll have a look around MANTIS to see if it's already been logged, but this is quite a bad problem.
Regards,
Tim.
I have tried this on two seperate machines, both with the same model card, both before and after a fresh install of v0.2, and tested again after the v0.2.3 update on both machines.
I also tried a couple of different Radeon driver sets, which also made no difference.
I can also confirm that the "fix" (if you can call it that) is to change windows default font size back to normal. I had mine set to 140% or 134 DPI. Viewing the fullscreen video on "Original" aspect ratio also works regardless of the font size, but viewing vids like this is far from ideal.
Furthermore, the fullscreen video WAS displaying normally after a v0.2RC2 upgrade to v0.2.
It was only after I was forced to uninstall and reinstall MP to clear out any older CVS/SVN's that the problem presented.
As far as I'm concerned, this is a major bug. I'll have a look around MANTIS to see if it's already been logged, but this is quite a bad problem.
Regards,
Tim.
Just for the record, switching themes on the fly works just fine, but unfortunately the dpi settings are not part of a theme. Bummer. 
Norway
Well. that diden't do the trick for a friend of mine..... did you use large-fonts?
- July 14, 2006
- 35
- 0
hmmm
I can confirm that with my ATI 9550 and the latest Catalyst (6.6 I think) drivers that I *was* experiencing this but somehow I no longer seem to have this problem and don't know why??
I do still have large fonts though as I very occasionally use the desktop via my TV on my dedicated HTPC. Ahhh I remember what I did, I think I set it to small fonts 96dpi and just increased all the Text sizes in the Appearance settings of windows and that worked. I was just experimenting around and that worked for me...
I can confirm that with my ATI 9550 and the latest Catalyst (6.6 I think) drivers that I *was* experiencing this but somehow I no longer seem to have this problem and don't know why??
I do still have large fonts though as I very occasionally use the desktop via my TV on my dedicated HTPC. Ahhh I remember what I did, I think I set it to small fonts 96dpi and just increased all the Text sizes in the Appearance settings of windows and that worked. I was just experimenting around and that worked for me...
Here's my take on the problem. I haven't had time to look in detail, but I hope here's some useful information.
If I look at my logs, I see several places where the player attempts to deal with a screen size (1932x1092) which is larger than my screen. (1920x1080). In previous versions by editing the configuration files so that a file for the wrong size (1932x1092) actually pointed to a correct configuration for the correct size (1920x1080) the problem would go away. This doesn't seem to work in the latest update.
My guess (it may not be a good one) is that the code is computing an incorrect screen size -- when using VMR9 exclusive mode to open this screen which is larger than the current resolution, the video driver is defaulting to the blank screen. Obviously, this would be driver dependant, so the problem might not show up for everyone.
Just browsing the code, it looks like the overscanwidth is getting set to the larger size (which is reported in the log) , and a sanity check statement in the code is setting the current screen size to be equal to the oversizewidth.
This might also make sense with respect to the font size fix. So going out on a long limb, is it possible that someplace in the GUI code that the screen size is computed in a manner such that it gets increased based upon the size of a font. (i.e. with the larger fonts, something is going beyond the edge of the screen)
I agree this is a big problem. I don't have much experience with this code, but if I get a chance, I'll try to track things down in more detail.
If I look at my logs, I see several places where the player attempts to deal with a screen size (1932x1092) which is larger than my screen. (1920x1080). In previous versions by editing the configuration files so that a file for the wrong size (1932x1092) actually pointed to a correct configuration for the correct size (1920x1080) the problem would go away. This doesn't seem to work in the latest update.
My guess (it may not be a good one) is that the code is computing an incorrect screen size -- when using VMR9 exclusive mode to open this screen which is larger than the current resolution, the video driver is defaulting to the blank screen. Obviously, this would be driver dependant, so the problem might not show up for everyone.
Just browsing the code, it looks like the overscanwidth is getting set to the larger size (which is reported in the log) , and a sanity check statement in the code is setting the current screen size to be equal to the oversizewidth.
This might also make sense with respect to the font size fix. So going out on a long limb, is it possible that someplace in the GUI code that the screen size is computed in a manner such that it gets increased based upon the size of a font. (i.e. with the larger fonts, something is going beyond the edge of the screen)
I agree this is a big problem. I don't have much experience with this code, but if I get a chance, I'll try to track things down in more detail.