<?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"
	>
<channel>
	<title>Comments on: Why does Quicktime suck so much?</title>
	<atom:link href="http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/feed/" rel="self" type="application/rss+xml" />
	<link>http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/</link>
	<description>Eric Cheng's Journal</description>
	<pubDate>Mon, 01 Dec 2008 17:47:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Matthew</title>
		<link>http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-2492973</link>
		<dc:creator>Matthew</dc:creator>
		<pubDate>Sun, 21 Sep 2008 21:58:04 +0000</pubDate>
		<guid isPermaLink="false">http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-2492973</guid>
		<description>&lt;p&gt;If you can successfully render 500 photos, why not simply render this amount 20 times and then combine the resulting video files into one? It may not be ideal, but rendering that many at one time is asking for trouble anyway in that a computer crash would destroy all progress.&lt;/p&gt;

&lt;p&gt;I tend to take the slightly longer approach when doing things such as this as it removes the stress factor.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>If you can successfully render 500 photos, why not simply render this amount 20 times and then combine the resulting video files into one? It may not be ideal, but rendering that many at one time is asking for trouble anyway in that a computer crash would destroy all progress.</p>

<p>I tend to take the slightly longer approach when doing things such as this as it removes the stress factor.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: stephen</title>
		<link>http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-133604</link>
		<dc:creator>stephen</dc:creator>
		<pubDate>Mon, 07 Aug 2006 14:33:09 +0000</pubDate>
		<guid isPermaLink="false">http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-133604</guid>
		<description>&lt;p&gt;While QuickTime works fine for me on a MacBook Pro, I sympathise with your export progress  niggles.&lt;/p&gt;

&lt;p&gt;Exporting 480x270 QT movies from Final Cut Express, while not reaching the dizzying heights of 144% progress, does sit at between 7-12% for around three quarters of the 15-20 minutes it takes to churn out the average 2-3 minute movie. If you haven't been there before, it can look like you're in for a long, long wait.&lt;/p&gt;

&lt;p&gt;So if (when!) you go Mac, be prepared...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>While QuickTime works fine for me on a MacBook Pro, I sympathise with your export progress  niggles.</p>

<p>Exporting 480&#215;270 QT movies from Final Cut Express, while not reaching the dizzying heights of 144% progress, does sit at between 7-12% for around three quarters of the 15-20 minutes it takes to churn out the average 2-3 minute movie. If you haven&#8217;t been there before, it can look like you&#8217;re in for a long, long wait.</p>

<p>So if (when!) you go Mac, be prepared&#8230;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: echeng</title>
		<link>http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-132767</link>
		<dc:creator>echeng</dc:creator>
		<pubDate>Sun, 06 Aug 2006 19:17:52 +0000</pubDate>
		<guid isPermaLink="false">http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-132767</guid>
		<description>&lt;p&gt;I always thought Quicktime Pro was that one trick pony, since it has an "open image sequence" option.  I'm sure Final Cut Pro does this very elegantly, and will probably go Mac if I start getting more serious about video.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I always thought Quicktime Pro was that one trick pony, since it has an &#8220;open image sequence&#8221; option.  I&#8217;m sure Final Cut Pro does this very elegantly, and will probably go Mac if I start getting more serious about video.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Nash</title>
		<link>http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-132509</link>
		<dc:creator>Adam Nash</dc:creator>
		<pubDate>Sun, 06 Aug 2006 15:29:54 +0000</pubDate>
		<guid isPermaLink="false">http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-132509</guid>
		<description>&lt;p&gt;I got it now.  If you want one picture per frame, then you'd need one of the movie applications, iMovie HD, Final Cut Express, or Final Cut Pro.&lt;/p&gt;

&lt;p&gt;I don't know the rendering times for those applications.&lt;/p&gt;

&lt;p&gt;I'm pretty sure your $700 Dell matches the recent Intel Macs in speed/architecture, so not sure you have a reason to be so fussy with Macs.  You did work for Apple, after all... :)&lt;/p&gt;

&lt;p&gt;This makes me think there must be a "one trick pony" application that does just this - it seems like a relatively simple task.  I'm suprised there isn't a shareware or other inexpensive program that just does this (pictures * fps -&#62; movie)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Adam&lt;/li&gt;
&lt;/ul&gt;
</description>
		<content:encoded><![CDATA[<p>I got it now.  If you want one picture per frame, then you&#8217;d need one of the movie applications, iMovie HD, Final Cut Express, or Final Cut Pro.</p>

<p>I don&#8217;t know the rendering times for those applications.</p>

<p>I&#8217;m pretty sure your $700 Dell matches the recent Intel Macs in speed/architecture, so not sure you have a reason to be so fussy with Macs.  You did work for Apple, after all&#8230; :)</p>

<p>This makes me think there must be a &#8220;one trick pony&#8221; application that does just this - it seems like a relatively simple task.  I&#8217;m suprised there isn&#8217;t a shareware or other inexpensive program that just does this (pictures * fps -&gt; movie)</p>

<ul>
<li>Adam</li>
</ul>]]></content:encoded>
	</item>
	<item>
		<title>By: echeng</title>
		<link>http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-132251</link>
		<dc:creator>echeng</dc:creator>
		<pubDate>Sun, 06 Aug 2006 08:24:39 +0000</pubDate>
		<guid isPermaLink="false">http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-132251</guid>
		<description>&lt;p&gt;Nash: iPhoto makes a slideshow, but will it automatically take a sequence of images and render it into a movie, with 1 sequential image per frame? (just curious)  I ultimately need it at 1920x1080 resolution.&lt;/p&gt;

&lt;p&gt;On my $700 Dell, 10,000 frames of 640x480 images takes hours, not days.  QT Pro finishes the renders; it just refuses to quit.  I can salvage the movie by copying the temp file before I cancel the job.&lt;/p&gt;

&lt;p&gt;I did a test at full HD resolution (500+ images, which took less than an hour), and it looks damn cool. And QT Pro even quits properly when only using 500 images. :)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Nash: iPhoto makes a slideshow, but will it automatically take a sequence of images and render it into a movie, with 1 sequential image per frame? (just curious)  I ultimately need it at 1920&#215;1080 resolution.</p>

<p>On my $700 Dell, 10,000 frames of 640&#215;480 images takes hours, not days.  QT Pro finishes the renders; it just refuses to quit.  I can salvage the movie by copying the temp file before I cancel the job.</p>

<p>I did a test at full HD resolution (500+ images, which took less than an hour), and it looks damn cool. And QT Pro even quits properly when only using 500 images. :)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: gilesshaxted</title>
		<link>http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-131548</link>
		<dc:creator>gilesshaxted</dc:creator>
		<pubDate>Sat, 05 Aug 2006 16:06:09 +0000</pubDate>
		<guid isPermaLink="false">http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-131548</guid>
		<description>&lt;p&gt;is this time frame of the building work at long last ?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>is this time frame of the building work at long last ?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Nash</title>
		<link>http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-131151</link>
		<dc:creator>Adam Nash</dc:creator>
		<pubDate>Sat, 05 Aug 2006 05:59:24 +0000</pubDate>
		<guid isPermaLink="false">http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-131151</guid>
		<description>&lt;p&gt;iPhoto 6 seems to have a mode that offers a variety of sizes, up to full resolution... I know, because I accidentally made the movie first in that mode, and it was 680MB.&lt;/p&gt;

&lt;p&gt;You were only trying to do 640x480 right?  It definitely supports that.  I lowered the size and added transitions just to produce a 60MB web version.&lt;/p&gt;

&lt;p&gt;I think you are trying to use the wrong product here.  If you want to bring over a drive, I'm willing to lend you my G5 to try doing it.  I have to admit, doing 10K photos sounds like it would take days...  the 78 photo movie, full size, took about 1/2 hour to render on my machine (although dual G5 is getting long in the tooth).&lt;/p&gt;

&lt;p&gt;I like your blog, it's fun to tease you in public.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>iPhoto 6 seems to have a mode that offers a variety of sizes, up to full resolution&#8230; I know, because I accidentally made the movie first in that mode, and it was 680MB.</p>

<p>You were only trying to do 640&#215;480 right?  It definitely supports that.  I lowered the size and added transitions just to produce a 60MB web version.</p>

<p>I think you are trying to use the wrong product here.  If you want to bring over a drive, I&#8217;m willing to lend you my G5 to try doing it.  I have to admit, doing 10K photos sounds like it would take days&#8230;  the 78 photo movie, full size, took about 1/2 hour to render on my machine (although dual G5 is getting long in the tooth).</p>

<p>I like your blog, it&#8217;s fun to tease you in public.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: echeng</title>
		<link>http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-130656</link>
		<dc:creator>echeng</dc:creator>
		<pubDate>Fri, 04 Aug 2006 18:04:44 +0000</pubDate>
		<guid isPermaLink="false">http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-130656</guid>
		<description>&lt;p&gt;Adam - that isn't the type of thing I want to do. I can make movies like that in about 5 minutes. :)&lt;/p&gt;

&lt;p&gt;This is a time-lapse with 10,000 sequential movies.  Quicktime can open a sequence of images.  It has to be high resolution as well, so iMovie isn't going to cut it!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Adam - that isn&#8217;t the type of thing I want to do. I can make movies like that in about 5 minutes. :)</p>

<p>This is a time-lapse with 10,000 sequential movies.  Quicktime can open a sequence of images.  It has to be high resolution as well, so iMovie isn&#8217;t going to cut it!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Nash</title>
		<link>http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-130592</link>
		<dc:creator>Adam Nash</dc:creator>
		<pubDate>Fri, 04 Aug 2006 16:10:58 +0000</pubDate>
		<guid isPermaLink="false">http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-130592</guid>
		<description>&lt;p&gt;Whoops... got the URL wrong:
http://web.mac.com/adamnash/iWeb/Alaska/Alaska.html&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Whoops&#8230; got the URL wrong:
<a href="http://web.mac.com/adamnash/iWeb/Alaska/Alaska.html" rel="nofollow">http://web.mac.com/adamnash/iW.....laska.html</a></p>]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Nash</title>
		<link>http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-130589</link>
		<dc:creator>Adam Nash</dc:creator>
		<pubDate>Fri, 04 Aug 2006 16:09:30 +0000</pubDate>
		<guid isPermaLink="false">http://echeng.com/journal/2006/08/03/why-does-quicktime-suck-so-much/#comment-130589</guid>
		<description>&lt;p&gt;Eric, don't whine like a baby.  :)  I think you are running into the fact that Quicktime is the lowest of the low end as far as authoring is concerned - rendering 10K images into a movie is not a small feat.&lt;/p&gt;

&lt;p&gt;Actually, iMovie and iDVD do this pretty well.  Why don't you just admit that you miss having a Mac, and get one for this type of thing.  Final Cut Pro would also do this easily for you.&lt;/p&gt;

&lt;p&gt;Have you seen my movie of my Alaska pictures (iPhoto generated, via export):
http://web.apple.com/adamnash/Alaska&lt;/p&gt;

&lt;p&gt;:)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Eric, don&#8217;t whine like a baby.  :)  I think you are running into the fact that Quicktime is the lowest of the low end as far as authoring is concerned - rendering 10K images into a movie is not a small feat.</p>

<p>Actually, iMovie and iDVD do this pretty well.  Why don&#8217;t you just admit that you miss having a Mac, and get one for this type of thing.  Final Cut Pro would also do this easily for you.</p>

<p>Have you seen my movie of my Alaska pictures (iPhoto generated, via export):
<a href="http://web.apple.com/adamnash/Alaska" rel="nofollow">http://web.apple.com/adamnash/Alaska</a></p>

<p>:)</p>]]></content:encoded>
	</item>
</channel>
</rss>
