No subject


Wed Jun 24 15:02:31 UTC 2009


which became more than just the 8400GS...

<quote>
In theory none of this should apply to a digital signal on a flat panel =
monitor, but overscan seems to have persisted in the HDTV world.  I  =
suspect this is because there are CRT HDTV sets out there and the spec =
has to accommodate them.  </quote>


Possibly a development of this explanation is that if all HD's did not =
overscan it makes the overscanning ones more obvious and therefore would =
make for more unhappy consumers, which should be the case in any event.  =
If they do not know what to blame, blame becomes difficult.

Also we have had sliders for Volume, Bass, Brightness etc for ages, why =
not one for overscan?

In the predecessor thread I argued that where a manufacturer promoted a =
set as capable of displaying a certain resolution then I think the set =
should display that, and not a cut down overscanned version.  (As that =
thread had a narrower subject I repeat the notion here)

Its a bit like buying a five seater car and getting a two seater...and =
not realising you only have two seats.  Perhaps a bit exaggerated, the =
analogy remains valid.

<quote>You fixed yours at the TV end - and that's nVidia's answer.  =
There used to be settings at the video card end, and those don't work, =
apparently for 8x00 series cards.  In my case I have a plain old CRT TV, =
and there's no adjusting for this.  Besides, it works correctly with =
other consumer electronics.
Dale Pontius </quote>

I agree it is annoying that NVIDIA have taken back what they gave.  =
However is there a greater case for your TV manufacturer to update the =
TV firmware and fix this?  NVIDIA updates their firmware, have done for =
years..will do for years..why should your TV not be any different? =20

If there was more consumer pull for manufacturers to fix their TV's we =
might move the problem and its fix back to where it belongs - in the TV.
------=_NextPart_000_00EB_01CA01A0.21CE16F0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16825" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV>From thread:&nbsp;[mythtv-users] overscan problems with nvidia 8400 =
GS -=20
which became more than just the 8400GS...<BR></DIV>
<DIV>&lt;quote&gt;</DIV>
<DIV>In theory none of this should apply to a digital signal on a flat =
panel=20
monitor, but overscan seems to have persisted in the HDTV world.&nbsp; =
I&nbsp;=20
suspect this is because there are CRT HDTV sets out there and the spec =
has to=20
accommodate them.&nbsp; &lt;/quote&gt;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>Possibly a development of this explanation is that if all HD's did =
not=20
overscan it makes the overscanning ones more obvious and therefore would =
make=20
for more unhappy consumers, which should be the case in any event.&nbsp; =
If they=20
do not know what to blame, blame becomes difficult.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Also we have had sliders for Volume, Bass, Brightness etc for ages, =
why not=20
one for overscan?</DIV>
<DIV>&nbsp;</DIV>
<DIV>In the predecessor thread I argued that where a manufacturer =
promoted a set=20
as capable of displaying a certain resolution then I think the set =
should=20
display that, and not a cut down overscanned version.&nbsp; (As that =
thread had=20
a narrower subject I repeat&nbsp;the&nbsp;notion&nbsp;here)</DIV>
<DIV>&nbsp;</DIV>
<DIV>Its a bit like buying a five seater car and getting a two =
seater...and not=20
realising you only have two seats.&nbsp; Perhaps a bit exaggerated, the =
analogy=20
remains valid.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&lt;quote&gt;You fixed yours at the TV end - and that's nVidia's=20
answer.&nbsp; There used to be settings at the video card end, and those =
don't=20
work, apparently for 8x00 series cards.&nbsp; In my case I have a plain =
old CRT=20
TV, and there's no adjusting for this.&nbsp; Besides, it works correctly =
with=20
other consumer electronics.<BR>Dale Pontius &lt;/quote&gt;<BR><BR>I =
agree it is=20
annoying that NVIDIA have taken&nbsp;back what they gave.&nbsp; However =
is there=20
a greater case for your TV manufacturer to update the TV firmware and =
fix=20
this?&nbsp; NVIDIA updates their firmware, have done for years..will do =
for=20
years..why should your TV not be any different?&nbsp; </DIV>
<DIV>&nbsp;</DIV>
<DIV>If there was more consumer pull for manufacturers to fix their TV's =
we=20
might move the problem and its fix back to where it belongs -&nbsp;in =
the=20
TV.</DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_00EB_01CA01A0.21CE16F0--



More information about the mythtv-users mailing list