<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Building an Optimized, Graphics-Intensive Silverlight Application</title><link>http://blogs.msdn.com/tims/archive/2009/03/24/building-an-optimized-graphics-intensive-silverlight-application.aspx</link><description>Seema Ramchandani works on performance as a Program Manager on the Silverlight team. She gave a fast-paced talk at MIX09 covering the graphics and media that contained some helpful tips for performance profiling, debugging and optimization. Silverlight</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Summary of the 20min perf talk</title><link>http://blogs.msdn.com/tims/archive/2009/03/24/building-an-optimized-graphics-intensive-silverlight-application.aspx#9506021</link><pubDate>Wed, 25 Mar 2009 04:30:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9506021</guid><dc:creator>SilverLite</dc:creator><description>&lt;p&gt;The 20 minute talk is posted here . I spoke till the speaker timer started to flash at me (giant flashing&lt;/p&gt;
</description></item><item><title>Building an Optimized, Graphics-Intensive Silverlight Application - Tim Sneath</title><link>http://blogs.msdn.com/tims/archive/2009/03/24/building-an-optimized-graphics-intensive-silverlight-application.aspx#9506360</link><pubDate>Wed, 25 Mar 2009 07:42:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9506360</guid><dc:creator>DotNetShoutout</dc:creator><description>&lt;p&gt;Thank you for submitting this cool story - Trackback from DotNetShoutout&lt;/p&gt;</description></item><item><title>re: Building an Optimized, Graphics-Intensive Silverlight Application</title><link>http://blogs.msdn.com/tims/archive/2009/03/24/building-an-optimized-graphics-intensive-silverlight-application.aspx#9510379</link><pubDate>Thu, 26 Mar 2009 13:34:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9510379</guid><dc:creator>Ann_developer</dc:creator><description>&lt;p&gt;Cool article! THANKS!&lt;/p&gt;
&lt;p&gt;Hope this article I like also help you to better understand graphic-intensive applications. Here is direct link &lt;a rel="nofollow" target="_new" href="http://techzone.enterra-inc.com/architecture/algorythm-of-defining-plain-polygon-signature-point/"&gt;http://techzone.enterra-inc.com/architecture/algorythm-of-defining-plain-polygon-signature-point/&lt;/a&gt; &lt;/p&gt;
&lt;p&gt;Good luck!&lt;/p&gt;
</description></item><item><title>re: Building an Optimized, Graphics-Intensive Silverlight Application</title><link>http://blogs.msdn.com/tims/archive/2009/03/24/building-an-optimized-graphics-intensive-silverlight-application.aspx#9548169</link><pubDate>Tue, 14 Apr 2009 11:13:59 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9548169</guid><dc:creator>Alex Zambelli</dc:creator><description>&lt;p&gt;Hi Tim,&lt;/p&gt;
&lt;p&gt;You say:&lt;/p&gt;
&lt;p&gt;&amp;quot;For maximum throughput, make sure you encode the video at the minimum framerate that you need (typically 18-20fps).&amp;quot;&lt;/p&gt;
&lt;p&gt;I understand what you're effectively trying to say (&amp;quot;Less frames to decode and render leads to lower CPU usage and smoother playback&amp;quot;), but it doesn't really work that way with video. You can't just arbitrarily decimate video frame rates to the point of &amp;quot;good enough.&amp;quot; 18-20 fps is not an acceptable frame rate for video. There are really only 2 real-world cases where frame rate decimation is acceptable in video encoding:&lt;/p&gt;
&lt;p&gt;1) Because film is shot at 24 fps and often converted to 60 Hz (30i or 60p) in the NTSC/ATSC world through the process of telecine, it is highly recommended that film-originated video content always be restored back to its original 24p cadence before being encoded for the Web.&lt;/p&gt;
&lt;p&gt;2) Video content is actually typically shot at 60 Hz (NTSC/ATSC) or 50 Hz (PAL), but for Web video it is an acceptable practice to decimate half the frames and encode video content at 30 and 25 frames per second, respectively, in order to avoid playback performance issues.&lt;/p&gt;</description></item></channel></rss>