<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Acmelabs&#039; Blog &#187; OpenGL</title>
	<atom:link href="http://blog.mymediasystem.net/tag/opengl/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mymediasystem.net</link>
	<description>MyMediaSystem - 1080p - AVCHD - H.264 - Linux - 3D - GPS &#38; GPX</description>
	<lastBuildDate>Wed, 18 Jan 2012 19:36:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>NVIDIA VDPAU 180.11.02 adds OpenGL3.0 support</title>
		<link>http://blog.mymediasystem.net/avchd/nvidia-vdpau-1801102-adds-opengl30-support/</link>
		<comments>http://blog.mymediasystem.net/avchd/nvidia-vdpau-1801102-adds-opengl30-support/#comments</comments>
		<pubDate>Wed, 17 Dec 2008 10:57:56 +0000</pubDate>
		<dc:creator>acmelab68</dc:creator>
				<category><![CDATA[AVCHD]]></category>
		<category><![CDATA[hardware acceleration]]></category>
		<category><![CDATA[nVidia]]></category>
		<category><![CDATA[OpenGL]]></category>
		<category><![CDATA[vdpau]]></category>

		<guid isPermaLink="false">http://blog.mymediasystem.net/?p=1478</guid>
		<description><![CDATA[NVIDIA released on 15th of December 2008 a new VDPAU (PureVideo for Linux) capable Beta Driver. I wrote in the test of 180.11 driver, that only OpenGL3.0 was added to the new driver. That was obviously wrong, because the &#8216;.02&#8242; seems to accomplish this task. For anybody who&#8217;s looking for improvement regarding bug fixing of [...]]]></description>
		<wfw:commentRss>http://blog.mymediasystem.net/avchd/nvidia-vdpau-1801102-adds-opengl30-support/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>NVIDIA VDPAU 180.11 test against .mts (AVCHD) and .mkv (Matroska/h264) playback</title>
		<link>http://blog.mymediasystem.net/avchd/nvidia-vdpau-180-11/</link>
		<comments>http://blog.mymediasystem.net/avchd/nvidia-vdpau-180-11/#comments</comments>
		<pubDate>Sat, 06 Dec 2008 12:19:45 +0000</pubDate>
		<dc:creator>acmelab68</dc:creator>
				<category><![CDATA[AVCHD]]></category>
		<category><![CDATA[Canon]]></category>
		<category><![CDATA[GPU]]></category>
		<category><![CDATA[hardware acceleration]]></category>
		<category><![CDATA[HDC-SD100]]></category>
		<category><![CDATA[HF100]]></category>
		<category><![CDATA[HOWTO]]></category>
		<category><![CDATA[Matroska]]></category>
		<category><![CDATA[mplayer]]></category>
		<category><![CDATA[nVidia]]></category>
		<category><![CDATA[OpenGL]]></category>
		<category><![CDATA[Panasonic]]></category>
		<category><![CDATA[V-Sync]]></category>
		<category><![CDATA[vdpau]]></category>

		<guid isPermaLink="false">http://blog.mymediasystem.net/?p=979</guid>
		<description><![CDATA[[UPDATE] Read here about the latest development of NVIDIA&#8217;s vdpau video output driver: Tag: vdpau NVIDIA&#8217;s hardware acceleration for HD (H264) content is now reality since they published their first beta driver, the 180.06 on the 14th of November 2008. I&#8217;ve tested these new Beta driver here, and found a few bugs. I skipped the [...]]]></description>
		<wfw:commentRss>http://blog.mymediasystem.net/avchd/nvidia-vdpau-180-11/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Tearing with nVidia drivers and mplayer with &#8220;-vo xv&#8221;</title>
		<link>http://blog.mymediasystem.net/my-media-system/tearing-with-nvidia-dirvers-and-mplayer-with-vo-xv/</link>
		<comments>http://blog.mymediasystem.net/my-media-system/tearing-with-nvidia-dirvers-and-mplayer-with-vo-xv/#comments</comments>
		<pubDate>Wed, 15 Oct 2008 15:05:37 +0000</pubDate>
		<dc:creator>acmelab68</dc:creator>
				<category><![CDATA[My Media System]]></category>
		<category><![CDATA[FullHD]]></category>
		<category><![CDATA[HD]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[MMS]]></category>
		<category><![CDATA[mplayer]]></category>
		<category><![CDATA[nVidia]]></category>
		<category><![CDATA[OpenGL]]></category>
		<category><![CDATA[Tearing]]></category>
		<category><![CDATA[V-Sync]]></category>
		<category><![CDATA[XV]]></category>

		<guid isPermaLink="false">http://blog.mymediasystem.net/?p=89</guid>
		<description><![CDATA[Well, let&#8217;s start with the conclusion: setting XV_SYNC_TO_VBLANK has no effect, if a second monitor is attached. But let&#8217;s start at the very beginning: What is tearing? Well, this is how Wikipedia defines it: Screen tearing is a phenomenon in video where a previously rendered frame overlaps a newly rendered frame, creating a torn look [...]]]></description>
		<wfw:commentRss>http://blog.mymediasystem.net/my-media-system/tearing-with-nvidia-dirvers-and-mplayer-with-vo-xv/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

