<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: DVI to HDMI overscan (screen edge cutoff) on an HDTV</title>
	<atom:link href="http://www.ypass.net/blog/2009/07/dvi-to-hdmi-overscan-screen-edge-cutoff-on-an-hdtv/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ypass.net/blog/2009/07/dvi-to-hdmi-overscan-screen-edge-cutoff-on-an-hdtv/</link>
	<description>Solaris, PHP, and Random Things</description>
	<lastBuildDate>Tue, 17 Jan 2012 00:24:06 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Switching off overscan in Samsung SyncMaster P2470HD &#124; koppschütteln.de</title>
		<link>http://www.ypass.net/blog/2009/07/dvi-to-hdmi-overscan-screen-edge-cutoff-on-an-hdtv/comment-page-1/#comment-1663</link>
		<dc:creator>Switching off overscan in Samsung SyncMaster P2470HD &#124; koppschütteln.de</dc:creator>
		<pubDate>Thu, 07 Jul 2011 13:26:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.ypass.net/blog/?p=275#comment-1663</guid>
		<description>[...] to be designed for a TV. There are lots of solutions to the problem, starting with messing with NVida&#8217;s driver settings, just using the VGA cable (or a DVI one, for that matter). The cleanest solution to this is, of [...]</description>
		<content:encoded><![CDATA[<p>[...] to be designed for a TV. There are lots of solutions to the problem, starting with messing with NVida&#8217;s driver settings, just using the VGA cable (or a DVI one, for that matter). The cleanest solution to this is, of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kristianhk</title>
		<link>http://www.ypass.net/blog/2009/07/dvi-to-hdmi-overscan-screen-edge-cutoff-on-an-hdtv/comment-page-1/#comment-1661</link>
		<dc:creator>kristianhk</dc:creator>
		<pubDate>Fri, 01 Jul 2011 12:44:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.ypass.net/blog/?p=275#comment-1661</guid>
		<description>Thanks. The modeline-trick didn&#039;t work, but got me going to a working solution:
1. Added

Option         &quot;UseEDID&quot; &quot;False&quot;
Option         &quot;ExactModeTimingsDVI&quot; &quot;True&quot;

to the &quot;Monitor&quot; section.
2. Restarted Xorg/gdm.
3. Ran the nvidia-settings program as root.
4. Saw that even more resolutions now was detected, strangely enough.
5. Changed to my preferred resolution, and it worked without overscan!
6. Saved the X configuration from nvidia-settings (check for merge with existing file, so you keep the two beforementioned lines).
7. Enjoy.

I can, ofcourse, not guarantee that this works for anyone else, but it&#039;s worth a try.</description>
		<content:encoded><![CDATA[<p>Thanks. The modeline-trick didn&#8217;t work, but got me going to a working solution:<br />
1. Added</p>
<p>Option         &#8220;UseEDID&#8221; &#8220;False&#8221;<br />
Option         &#8220;ExactModeTimingsDVI&#8221; &#8220;True&#8221;</p>
<p>to the &#8220;Monitor&#8221; section.<br />
2. Restarted Xorg/gdm.<br />
3. Ran the nvidia-settings program as root.<br />
4. Saw that even more resolutions now was detected, strangely enough.<br />
5. Changed to my preferred resolution, and it worked without overscan!<br />
6. Saved the X configuration from nvidia-settings (check for merge with existing file, so you keep the two beforementioned lines).<br />
7. Enjoy.</p>
<p>I can, ofcourse, not guarantee that this works for anyone else, but it&#8217;s worth a try.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: doorknob60</title>
		<link>http://www.ypass.net/blog/2009/07/dvi-to-hdmi-overscan-screen-edge-cutoff-on-an-hdtv/comment-page-1/#comment-1646</link>
		<dc:creator>doorknob60</dc:creator>
		<pubDate>Sun, 22 May 2011 05:15:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.ypass.net/blog/?p=275#comment-1646</guid>
		<description>Wow, thanks! With the open source ATI drivers and HDMI out, my Sony 32&quot; LCD was cutting things off (the proprietary Catalyst has overscan correction, but I wanted to try the free drivers), and this worked great. I used the findcoords program and used new modelines and set them with xrandr, and it seems to work just fine, cool. Now, if only sound will start outputting out of HDMI like it was earlier, don&#039;t know why it stopped working....</description>
		<content:encoded><![CDATA[<p>Wow, thanks! With the open source ATI drivers and HDMI out, my Sony 32&#8243; LCD was cutting things off (the proprietary Catalyst has overscan correction, but I wanted to try the free drivers), and this worked great. I used the findcoords program and used new modelines and set them with xrandr, and it seems to work just fine, cool. Now, if only sound will start outputting out of HDMI like it was earlier, don&#8217;t know why it stopped working&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nVidia Overscan Correction fixed in Latest Drivers &#124; yPass.net Blog</title>
		<link>http://www.ypass.net/blog/2009/07/dvi-to-hdmi-overscan-screen-edge-cutoff-on-an-hdtv/comment-page-1/#comment-1413</link>
		<dc:creator>nVidia Overscan Correction fixed in Latest Drivers &#124; yPass.net Blog</dc:creator>
		<pubDate>Fri, 02 Apr 2010 00:03:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.ypass.net/blog/?p=275#comment-1413</guid>
		<description>[...] solution for fixing overscan on nvidia cards is obsolete! I did find out just a few days ago that it does actually [...]</description>
		<content:encoded><![CDATA[<p>[...] solution for fixing overscan on nvidia cards is obsolete! I did find out just a few days ago that it does actually [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://www.ypass.net/blog/2009/07/dvi-to-hdmi-overscan-screen-edge-cutoff-on-an-hdtv/comment-page-1/#comment-1284</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Thu, 04 Mar 2010 11:05:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.ypass.net/blog/?p=275#comment-1284</guid>
		<description>I also had this problem, and your page was the very first to appear when doing a google search, thank you for the suggestion to look on the TV itself. I found that my Samsung 40&quot; Series 6 TV had a display mode of &quot;Just scan&quot; to fix the problem. Without it, all four sides of the picture were indeed cut off.</description>
		<content:encoded><![CDATA[<p>I also had this problem, and your page was the very first to appear when doing a google search, thank you for the suggestion to look on the TV itself. I found that my Samsung 40&#8243; Series 6 TV had a display mode of &#8220;Just scan&#8221; to fix the problem. Without it, all four sides of the picture were indeed cut off.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Mcmanus</title>
		<link>http://www.ypass.net/blog/2009/07/dvi-to-hdmi-overscan-screen-edge-cutoff-on-an-hdtv/comment-page-1/#comment-1189</link>
		<dc:creator>Alex Mcmanus</dc:creator>
		<pubDate>Sun, 17 Jan 2010 13:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ypass.net/blog/?p=275#comment-1189</guid>
		<description>Thanks for the info!

My setup is an NVidia graphics card with HDMI output going to an Panasonic Viera 1080p TV - solved by turning off the Overscan option in the TV settings menu.</description>
		<content:encoded><![CDATA[<p>Thanks for the info!</p>
<p>My setup is an NVidia graphics card with HDMI output going to an Panasonic Viera 1080p TV &#8211; solved by turning off the Overscan option in the TV settings menu.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dude</title>
		<link>http://www.ypass.net/blog/2009/07/dvi-to-hdmi-overscan-screen-edge-cutoff-on-an-hdtv/comment-page-1/#comment-1127</link>
		<dc:creator>Dude</dc:creator>
		<pubDate>Fri, 13 Nov 2009 04:40:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.ypass.net/blog/?p=275#comment-1127</guid>
		<description>Dudes, 
I just wasted two days playing with modelines and my Toshiba Regza TV via DVI-HDMI. I guess it doesnt matter what are the modelines settings if connected via HDMI. Finally, I found a setting in the TV menu to use &quot;native&quot; screen size (used to be &quot;natural&quot;) and it works perfect with ANY modelines.

cheers</description>
		<content:encoded><![CDATA[<p>Dudes,<br />
I just wasted two days playing with modelines and my Toshiba Regza TV via DVI-HDMI. I guess it doesnt matter what are the modelines settings if connected via HDMI. Finally, I found a setting in the TV menu to use &#8220;native&#8221; screen size (used to be &#8220;natural&#8221;) and it works perfect with ANY modelines.</p>
<p>cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dutchman</title>
		<link>http://www.ypass.net/blog/2009/07/dvi-to-hdmi-overscan-screen-edge-cutoff-on-an-hdtv/comment-page-1/#comment-1125</link>
		<dc:creator>Dutchman</dc:creator>
		<pubDate>Thu, 12 Nov 2009 15:00:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.ypass.net/blog/?p=275#comment-1125</guid>
		<description>&lt;a href=&quot;#comment-1118&quot; rel=&quot;nofollow&quot;&gt;@Chris&lt;/a&gt; 

On my Toshiba XV365DB I can solve the problem by selecting &#039;game mode&#039; in the setup menus of the TV itself. Maybe not an elegant solution, but it works for me (and is very easy). Hope this helps someone.</description>
		<content:encoded><![CDATA[<p><a href="#comment-1118" rel="nofollow">@Chris</a> </p>
<p>On my Toshiba XV365DB I can solve the problem by selecting &#8216;game mode&#8217; in the setup menus of the TV itself. Maybe not an elegant solution, but it works for me (and is very easy). Hope this helps someone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.ypass.net/blog/2009/07/dvi-to-hdmi-overscan-screen-edge-cutoff-on-an-hdtv/comment-page-1/#comment-1118</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Mon, 09 Nov 2009 14:26:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.ypass.net/blog/?p=275#comment-1118</guid>
		<description>Thanks so much for your help.  After reading this post, I knew to look for the 1:1 mode on my TV, which I found.  It was MUCH easier than all the messing with xorg.conf I tried.</description>
		<content:encoded><![CDATA[<p>Thanks so much for your help.  After reading this post, I knew to look for the 1:1 mode on my TV, which I found.  It was MUCH easier than all the messing with xorg.conf I tried.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary Murphy</title>
		<link>http://www.ypass.net/blog/2009/07/dvi-to-hdmi-overscan-screen-edge-cutoff-on-an-hdtv/comment-page-1/#comment-1090</link>
		<dc:creator>Gary Murphy</dc:creator>
		<pubDate>Sun, 18 Oct 2009 13:21:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.ypass.net/blog/?p=275#comment-1090</guid>
		<description>Great post.

My resolution ended up being at the TV.  My Philips had a setting called &quot;Unscaled&quot; that did the 1:1 pixel mapping that you mentioned.  For others reading this, I am not terribly happy with the Philips.  It is a FullHD, 1080p 1920x1080 TV and the quality from the PC is still isn&#039;t that great.</description>
		<content:encoded><![CDATA[<p>Great post.</p>
<p>My resolution ended up being at the TV.  My Philips had a setting called &#8220;Unscaled&#8221; that did the 1:1 pixel mapping that you mentioned.  For others reading this, I am not terribly happy with the Philips.  It is a FullHD, 1080p 1920&#215;1080 TV and the quality from the PC is still isn&#8217;t that great.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

