From: Jigme Datse Yli-RAsku <jigme.datse@datsemultimedia.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Getting X11 to "underscan"...
Date: Wed, 19 Oct 2016 15:42:45 -0700 [thread overview]
Message-ID: <588de36a-865d-9929-573d-4775b7f0b40e@datsemultimedia.com> (raw)
In-Reply-To: <nu8ghl$la4$1@blaine.gmane.org>
Thank you everyone. It now seems to be working. Not sure if the setting is a per input setting or not, but the main issue was the one input from the computer.
On 2016-10-19 12:11, Grant Edwards wrote:
> On 2016-10-18, Daniel Frey <djqfrey@gmail.com> wrote:
> > On 10/18/2016 08:57 AM, Grant Edwards wrote:
> >> On 2016-10-18, Daniel Frey <djqfrey@gmail.com> wrote:
> >>
> >>> I have three different manufacturers and each one has it, but on mine it
> >>> wasn't marked in the manual.
> >>
> >> Not all TVs can disable overscan. The last time was shopping, many of
> >> the Sony Bravias couldn't (that was a few years ago). On some TVs
> >> I've seen, in order to disable overscan the signal resolution has to
> >> match the panel resolution exactly...
> >>
> >
> > Yeah, I understand about the Sony TVs. A friend bought one in 2012/2013
> > and we even emailed Sony and their reply was it can't be done.
> >
> > Until I found an option under Setup called Screen or Screen Display, and
> > set it to Full Pixel. That disabled the overscan.
>
> Several other brands also have some odd, trademarked, phrase for the
> "disable overscan" feature, so keep an eye out for display modes with
> odd names invented by a marketting person who never quite understood
> what that mode actually does.
>
> If you ask about your model in some of the home-theater forums,
> somebody usually knows. But, you've got to wade through those awful
> web-UI based "forums"...
>
--
Jigme Datse Yli-Rasku
jigme.datse@datsemultimedia.com (Preferred address for new messages)
250-505-6117
Jigme Datse Yli-Rasku
PO Box 270
Rossland, BC V0G 1Y0
Canada
.......................................................................
... This message should be electronically signed, and if the sender ...
... has your public key, may also be encrypted. ...
... If you have any questions about this, please email, or call. ...
... ...
... Note, unknown calls likely will go to voicemail. ...
... Please leave a message if you get voicemail. ...
.......................................................................
prev parent reply other threads:[~2016-10-19 22:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 23:41 [gentoo-user] Getting X11 to "underscan" Jigme Datse Yli-RAsku
2016-10-17 23:47 ` Daniel Frey
2016-10-18 2:48 ` Jigme Datse Yli-RAsku
2016-10-18 12:20 ` Michael Mol
2016-10-19 4:36 ` Jigme Datse Yli-RAsku
2016-10-18 14:50 ` Daniel Frey
2016-10-18 15:57 ` [gentoo-user] " Grant Edwards
2016-10-18 16:18 ` Michael Mol
2016-10-18 19:32 ` Daniel Frey
2016-10-19 4:38 ` Jigme Datse Yli-RAsku
2016-10-19 9:20 ` [gentoo-user] " Stroller
2016-10-19 19:11 ` [gentoo-user] " Grant Edwards
2016-10-19 22:42 ` Jigme Datse Yli-RAsku [this message]
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=588de36a-865d-9929-573d-4775b7f0b40e@datsemultimedia.com \
--to=jigme.datse@datsemultimedia.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