<?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: Proof Delay- w00t!</title>
	<atom:link href="http://blogs.smugmug.com/pros/2006/11/19/event-or-large-shoot-workflow/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.smugmug.com/pros/2006/11/19/event-or-large-shoot-workflow/</link>
	<description>Got sales?</description>
	<lastBuildDate>Sun, 15 Nov 2009 10:44:54 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9-rare</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: SmugBlog: Pro Corner &#187; Blog Archive &#187; Please leave room for customer cropping</title>
		<link>http://blogs.smugmug.com/pros/2006/11/19/event-or-large-shoot-workflow/comment-page-1/#comment-29691</link>
		<dc:creator>SmugBlog: Pro Corner &#187; Blog Archive &#187; Please leave room for customer cropping</dc:creator>
		<pubDate>Fri, 12 Dec 2008 21:36:13 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.smugmug.com/pros/2006/11/19/event-or-large-shoot-workflow/#comment-29691</guid>
		<description>[...] SmugMug&#8217;s cropping tool and proof delay, Steve&#8217;s customers get exactly what they [...]</description>
		<content:encoded><![CDATA[<p>[...] SmugMug&#8217;s cropping tool and proof delay, Steve&#8217;s customers get exactly what they [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brett</title>
		<link>http://blogs.smugmug.com/pros/2006/11/19/event-or-large-shoot-workflow/comment-page-1/#comment-29659</link>
		<dc:creator>Brett</dc:creator>
		<pubDate>Sun, 01 Jun 2008 05:53:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.smugmug.com/pros/2006/11/19/event-or-large-shoot-workflow/#comment-29659</guid>
		<description>I guess the large files take longer to upload...but if you just upload teh big ones...then there is no need for a &quot;print optimized&quot; file.  I like Proof delay for the reason that I can hopefully correct bad crops prior to shipping.</description>
		<content:encoded><![CDATA[<p>I guess the large files take longer to upload&#8230;but if you just upload teh big ones&#8230;then there is no need for a &#8220;print optimized&#8221; file.  I like Proof delay for the reason that I can hopefully correct bad crops prior to shipping.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Pannoni</title>
		<link>http://blogs.smugmug.com/pros/2006/11/19/event-or-large-shoot-workflow/comment-page-1/#comment-11947</link>
		<dc:creator>Rob Pannoni</dc:creator>
		<pubDate>Wed, 27 Dec 2006 19:53:15 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.smugmug.com/pros/2006/11/19/event-or-large-shoot-workflow/#comment-11947</guid>
		<description>Proof delay is an okay workaround.  But it doesn&#039;t solve the root of the problem, which is that print photos ALWAYS need to be optimized differently than photos intended for screen display.  As I understand proof delay, if you had ten customers who bought ten photos each, you would have to manually upload and replace 100 photos just to fill the print orders.  That&#039;s better than sending display files to print.  But still not a great solution.    

Most serious photographers already have a workflow that produces separate files optimized for screen and print.  Certainly if you shoot in Adobe RGB, separate print files are a necessity because A-RGB files don&#039;t display well in a browser.  Ditto if you optimize sharpening, saturation or curves for screen display, which is not uncommon.  

What Smugmug really needs is a way to permanently attach a separate print file to photos displayed in galleries.  When a smugmug gallery owner is logged in, the print version could show as a link under the photo as if the print version were another display size.  For visitors, the print file would never be visible.  But the fact that there is a print-optimized file behind the scenes would give visitors a better visual representation of what they will get before they purchase.  If you really want to go wild, you could allow separate print files optimized (cropped) for different print sizes.  

The need to manage separate files for display and print is one of the most vexing and time consuming parts of digital photography.  Providing the ability to automatically manage display and print versions from within a single gallery would put you WAY ahead of the competition (not that you already aren&#039;t :) )

--Rob</description>
		<content:encoded><![CDATA[<p>Proof delay is an okay workaround.  But it doesn&#8217;t solve the root of the problem, which is that print photos ALWAYS need to be optimized differently than photos intended for screen display.  As I understand proof delay, if you had ten customers who bought ten photos each, you would have to manually upload and replace 100 photos just to fill the print orders.  That&#8217;s better than sending display files to print.  But still not a great solution.    </p>
<p>Most serious photographers already have a workflow that produces separate files optimized for screen and print.  Certainly if you shoot in Adobe RGB, separate print files are a necessity because A-RGB files don&#8217;t display well in a browser.  Ditto if you optimize sharpening, saturation or curves for screen display, which is not uncommon.  </p>
<p>What Smugmug really needs is a way to permanently attach a separate print file to photos displayed in galleries.  When a smugmug gallery owner is logged in, the print version could show as a link under the photo as if the print version were another display size.  For visitors, the print file would never be visible.  But the fact that there is a print-optimized file behind the scenes would give visitors a better visual representation of what they will get before they purchase.  If you really want to go wild, you could allow separate print files optimized (cropped) for different print sizes.  </p>
<p>The need to manage separate files for display and print is one of the most vexing and time consuming parts of digital photography.  Providing the ability to automatically manage display and print versions from within a single gallery would put you WAY ahead of the competition (not that you already aren&#8217;t <img src='http://blogs.smugmug.com/pros/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  )</p>
<p>&#8211;Rob</p>
]]></content:encoded>
	</item>
</channel>
</rss>
