<?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/"
xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:media="http://search.yahoo.com/mrss/"
> <channel><title>Comments on: More pano testing&#8230;</title> <atom:link href="http://www.canonblogger.com/2010/03/10/more-pano-testing/feed/" rel="self" type="application/rss+xml" /><link>http://www.canonblogger.com/2010/03/10/more-pano-testing/</link> <description>Home of the Learning Digital Photography Podcast with Jason Anderson</description> <lastBuildDate>Fri, 10 Feb 2012 18:10:37 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.2.1</generator> <xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" /> <item><title>By: Thom</title><link>http://www.canonblogger.com/2010/03/10/more-pano-testing/comment-page-1/#comment-5012</link> <dc:creator>Thom</dc:creator> <pubDate>Thu, 11 Mar 2010 12:36:28 +0000</pubDate> <guid
isPermaLink="false">http://www.canonblogger.com/?p=3108#comment-5012</guid> <description>Thanks to all for the response. It makes sense now..</description> <content:encoded><![CDATA[<p>Thanks to all for the response. It makes sense now..</p> ]]></content:encoded> </item> <item><title>By: Jason</title><link>http://www.canonblogger.com/2010/03/10/more-pano-testing/comment-page-1/#comment-5008</link> <dc:creator>Jason</dc:creator> <pubDate>Wed, 10 Mar 2010 17:29:37 +0000</pubDate> <guid
isPermaLink="false">http://www.canonblogger.com/?p=3108#comment-5008</guid> <description>Burt&#039;s reply below is a pretty good one and what I would have suggested the same.  You can increase the size by scrolling in.  If you want to see the full size, you would have to decrease the resolution to the point where the monitor can display the entire pano across the screen.  Since most monitors are only 1028 or 1280 wide, that means reducing the width to one of those in order to see a full size view without having to scroll left and right.</description> <content:encoded><![CDATA[<p>Burt&#8217;s reply below is a pretty good one and what I would have suggested the same.  You can increase the size by scrolling in.  If you want to see the full size, you would have to decrease the resolution to the point where the monitor can display the entire pano across the screen.  Since most monitors are only 1028 or 1280 wide, that means reducing the width to one of those in order to see a full size view without having to scroll left and right.</p> ]]></content:encoded> </item> <item><title>By: Burt</title><link>http://www.canonblogger.com/2010/03/10/more-pano-testing/comment-page-1/#comment-5007</link> <dc:creator>Burt</dc:creator> <pubDate>Wed, 10 Mar 2010 17:26:21 +0000</pubDate> <guid
isPermaLink="false">http://www.canonblogger.com/?p=3108#comment-5007</guid> <description>Thom - your problem is that the image is being reduced in size on the screen so that the entire horizontal image can be seen.  The result is that the height is reduced to the point of not being usable.That reduction is only the default view though.  Zoom in (command +) and you will see tons of detail in the image.  My Canon 5D MK II would give me a 7 image pano of 39,000 X 3700 pixels, or 147 MB image.  In normal preview, it looks tiny. Zoom in though and it is massively huge.Of course, all that assumes you did not make the pano with the trial version of some programs that restrict the output size.</description> <content:encoded><![CDATA[<p>Thom &#8211; your problem is that the image is being reduced in size on the screen so that the entire horizontal image can be seen.  The result is that the height is reduced to the point of not being usable.</p><p>That reduction is only the default view though.  Zoom in (command +) and you will see tons of detail in the image.  My Canon 5D MK II would give me a 7 image pano of 39,000 X 3700 pixels, or 147 MB image.  In normal preview, it looks tiny. Zoom in though and it is massively huge.</p><p>Of course, all that assumes you did not make the pano with the trial version of some programs that restrict the output size.</p> ]]></content:encoded> </item> <item><title>By: MariaV</title><link>http://www.canonblogger.com/2010/03/10/more-pano-testing/comment-page-1/#comment-5005</link> <dc:creator>MariaV</dc:creator> <pubDate>Wed, 10 Mar 2010 13:45:17 +0000</pubDate> <guid
isPermaLink="false">http://www.canonblogger.com/?p=3108#comment-5005</guid> <description>I would also like to know your response to Thom&#039;s question.  Would having more shots make a difference?</description> <content:encoded><![CDATA[<p>I would also like to know your response to Thom&#8217;s question.  Would having more shots make a difference?</p> ]]></content:encoded> </item> <item><title>By: Thom</title><link>http://www.canonblogger.com/2010/03/10/more-pano-testing/comment-page-1/#comment-5004</link> <dc:creator>Thom</dc:creator> <pubDate>Wed, 10 Mar 2010 12:39:04 +0000</pubDate> <guid
isPermaLink="false">http://www.canonblogger.com/?p=3108#comment-5004</guid> <description>JasonI took some pano shots in the fall.. when I got it stiched together (using Adobe Elements 6) it was very small to see. I think my originals were 7 shots horizontally. This is not the 1st time this has happened to me.. what am i doing wrong?</description> <content:encoded><![CDATA[<p>Jason</p><p>I took some pano shots in the fall.. when I got it stiched together (using Adobe Elements 6) it was very small to see. I think my originals were 7 shots horizontally. This is not the 1st time this has happened to me.. what am i doing wrong?</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Object Caching 735/756 objects using apc

Served from: www.canonblogger.com @ 2012-02-11 21:22:10 -->
