Bug 12473

Summary: [randr12] Xv scales to match virtual resulotion, not actual resolution.
Product: xorg Reporter: Peter Hjalmarsson <xake>
Component: Driver/nouveauAssignee: Nouveau Project <nouveau>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: arthur.huillet
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Peter Hjalmarsson 2007-09-18 14:39:48 UTC
01:00.0 VGA compatible controller [0300]: nVidia Corporation NV31 [GeForce FX 5600] [10de:0312] (rev a1)

Dualhead, using two analog monitors. Resolution is 1280x1024 on both, desktop spanning over both (not clone-mode).
If I in my xorg.conf set
      virtual      2560 2560
then it seems like using vx in mplayer on my first monitor scales according to the virtual size. If I move the window up and down the picture within the window moves more than the window.
It seems like if I move the window down one third in regards to 1024 pixels then the picture moves downward one third in regards to 2560 pixels.

workaround:
in your xorg.conf set:
      virtual      2560 1024
Comment 1 Maarten Maathuis 2007-10-05 07:37:54 UTC
Does this occur both with overlay and blitter (use xvinfo to determine which ports are blitter)?
Comment 2 Peter Hjalmarsson 2007-10-05 13:07:05 UTC
So currently I am running my screen with the same desktop-size as the virtual screen.
Most of the time the overlay seems to work as it should, i.e. good picture on first screen, blank windows on second screen.
But sometimes somehow the scaling is still wrong. I have not been able to find out a way to reproduce currently.
I will report back if I find a way to reproduce.

Blitter seems to work perfectly on both screens.
Comment 3 Arthur Huillet 2008-01-08 08:45:27 UTC
Hello,

could you please update to latest git, try again and see if you're still experiencing the bug?
Comment 4 Peter Hjalmarsson 2008-01-12 15:46:13 UTC
seems to work now.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.