(**) NVIDIA(0): Option "FlatPanelProperties" "Scaling = Aspect-Scaled"
(WW) NVIDIA(0): Unrecognized FlatPanelProperties property "Scaling";
(WW) NVIDIA(0): ignoring.
Option "FlatPanelProperties" "string"
This option requests particular properties for all or a subset of the
connected flat panels.
The option string is a semicolon-separated list of comma-separated
property=value pairs. Each list of property=value pairs can optionally be
prepended with a flat panel name and GPU specifier.
o "Scaling": controls the flat panel scaling mode; possible values are:
'Default' (the driver will use whichever scaling state is current),
'Native' (the driver will use the flat panel's scaler, if possible),
'Scaled' (the driver will use the NVIDIA GPU's scaler, if possible),
'Centered' (the driver will center the image, if possible), and
'aspect-scaled' (the X driver will scale with the NVIDIA GPU's
scaler, but keep the aspect ratio correct).
Option "FlatPanelProperties" "Scaling = Centered"
set the flat panel scaling mode to centered on all flat panels.
Artem S. Tashkinov
Linux and Open Source advocate
NVIDIA Linux Graphics
aplattner said:The Scaling option was removed when the front-end / back-end timing stuff was removed, but it looks like the documentation wasn't updated at the time. The documentation should be up to date in the next release. Sorry about that.
aplattner said:No, I don't have suggestions there. Those threads are kind of all over the place so it's hard to say. I should note that without an OpenGL-based composite manager, X rendering is not expected to be tear-free in general. VDPAU can do tear-free rendering when it's using the overlay presentation queue, but Xv and VDPAU with the blit presentation queue just do a best-effort wait for vblank and can still tear, for example if your video mode's vblank region is very small and the system can't quite get the rendering ready in time. Systems with high resolution displays using reduced blanking timings are becoming more common, so that might explain why people are seeing more tearing.
You could try enabling the ForceCompositionPipeline and/or ForceFullCompositionPipeline options in the MetaMode to see if that helps.
birdie said:This issue affects only Kepler based GPUs, so why all of a sudden tear-free experience is still readily available in pre-Kepler GPUs?
What is that has changed so drastically in this hardware? Maybe Kepler lacks some hardware synchronization features?
aplattner said:Kepler and earlier GPU architectures are dramatically different. Since, as I mentioned, the sync-to-vblank mechanism for Xv and VDPAU blit presentation queue are best-effort, small changes in timing anywhere in the system can cause tearing to appear or disappear. That's why I can't speculate as to why, on your particular system, one GPU behaves differently from another.
You must log in to send a PM.
Please Login | Register to add a comment.
Not a member? Register Now