From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problem with xf86-video-ati & nvidia-drivers
Date: Wed, 20 Jul 2011 11:29:08 -0400 [thread overview]
Message-ID: <CA+czFiBDPmGkDUGWM-C87FxWXHBPs8xLgCXqSpjdUSA9UYVdpQ@mail.gmail.com> (raw)
In-Reply-To: <84CC57F5-56A7-4926-A235-6A7EB49CFB9D@stellar.eclipse.co.uk>
On Wed, Jul 20, 2011 at 10:29 AM, Stroller
<stroller@stellar.eclipse.co.uk> wrote:
>
> On 19 July 2011, at 20:41, Grant wrote:
>> ...
>> I found this:
>>
>> "We recommend using the Just Scan mode with 1080i and 1080p material,
>> which assures zero overscan and proper 1:1 pixel matching for this
>> 1080p display."
>>
>> http://reviews.cnet.com/flat-panel-tvs/lg-47lh90/4505-6482_7-33485570.html#reviewPage1
>>
>> Just Scan is what I've always used which has the ghosting problem. I
>> think I'm back to square one.
>
> I think the Windows versions of the nVidia drivers have options to over- or under-scan.
>
> This compensates for (older?) TVs which have no way to switch to a "just scan" mode. So the graphics card will, I think, output a slightly over-sized picture, then the telly will scale it down a bit back to normal size. This will not produce a perfect picture, but if overscan on the TV cannot be disabled, then there is no better choice.
>
> Is it possible they have recently added this feature to the Linux nVidia driver?
Possibly related observation: On my 720p TV, if I output (via HDMI)
720p to it, I lose the outer ten or so pixels off of each side of the
screen. NVidia video card configuration tool indicated a higher
resolution was available, 13??x???, which resulted in a fine picture
with no missing pixels, once I switched to it. This was about a year
ago. (Can't easily test, now, because I no longer have a PC hooked up
to that TV)
--
:wq
next prev parent reply other threads:[~2011-07-20 15:30 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-09 23:21 [gentoo-user] Problem with xf86-video-ati & nvidia-drivers Grant
2011-07-10 0:20 ` meino.cramer
2011-07-11 23:48 ` Grant
2011-07-12 22:33 ` Grant
2011-07-13 2:27 ` meino.cramer
2011-07-13 15:55 ` Roger Mason
2011-07-13 16:17 ` meino.cramer
2011-07-13 17:13 ` Grant
2011-07-13 17:38 ` meino.cramer
2011-07-14 19:44 ` Grant
2011-07-14 20:07 ` Michael Mol
2011-07-14 23:29 ` Grant
2011-07-14 20:23 ` [gentoo-user] " Nikos Chantziaras
2011-07-14 23:30 ` Grant
2011-07-17 16:22 ` Grant
2011-07-17 16:47 ` Nikos Chantziaras
2011-07-17 16:54 ` Grant
2011-07-17 21:53 ` Michael Mol
2011-07-17 23:28 ` Grant
2011-07-18 13:18 ` [gentoo-user] " Stroller
2011-07-18 22:52 ` Grant
2011-07-19 0:56 ` Grant
2011-07-19 16:03 ` Daniel Frey
2011-07-19 19:41 ` Grant
2011-07-19 21:00 ` Mick
2011-07-20 18:38 ` Grant
2011-07-20 14:29 ` Stroller
2011-07-20 15:29 ` Michael Mol [this message]
2011-07-19 2:01 ` [gentoo-user] " Volker Armin Hemmann
2011-07-19 20:35 ` Grant
2011-07-19 20:54 ` Michael Mol
2011-07-20 21:22 ` Grant
2011-07-13 7:19 ` Nikos Chantziaras
2011-07-13 17:27 ` Grant
2011-07-13 7:13 ` Nikos Chantziaras
2011-07-13 12:25 ` Mick
2011-07-13 14:42 ` Nikos Chantziaras
2011-07-13 16:36 ` Mick
2011-07-16 16:22 ` Mick
2011-07-13 17:23 ` Grant
2011-07-14 6:13 ` Nikos Chantziaras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+czFiBDPmGkDUGWM-C87FxWXHBPs8xLgCXqSpjdUSA9UYVdpQ@mail.gmail.com \
--to=mikemol@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox