<?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: What I&#8217;d Love to See in Lightroom 2.0</title>
	<atom:link href="http://www.scottkelby.com/blog/2008/archives/932/feed" rel="self" type="application/rss+xml" />
	<link>http://www.scottkelby.com/blog/2008/archives/932</link>
	<description>Scoops, tips and comments published exclusively for friends of Scott Kelby</description>
	<lastBuildDate>Thu, 18 Mar 2010 02:37:50 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Lynn Parpard</title>
		<link>http://www.scottkelby.com/blog/2008/archives/932/comment-page-7#comment-109352</link>
		<dc:creator>Lynn Parpard</dc:creator>
		<pubDate>Mon, 05 Jan 2009 05:11:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottkelby.com/blog/2008/archives/932#comment-109352</guid>
		<description>I would love to see you make a lightroom dvd
please
           respectfully  Lynn Parpard</description>
		<content:encoded><![CDATA[<p>I would love to see you make a lightroom dvd<br />
please<br />
           respectfully  Lynn Parpard</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Miles Nassah</title>
		<link>http://www.scottkelby.com/blog/2008/archives/932/comment-page-7#comment-105632</link>
		<dc:creator>Miles Nassah</dc:creator>
		<pubDate>Fri, 12 Dec 2008 08:20:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottkelby.com/blog/2008/archives/932#comment-105632</guid>
		<description>There are too many posts for me to check if someone already said this, but ... your wish list is the exact anecdotal evidence that Adobe needs to continue selling Photoshop as the needed complementary software to Lightroom. As a former film and now digital photographer, I hope Adobe listens to folks like you and us who want and deserve more well-rounded software solutions. I know wish lists will never end as we will continue to find things we want our software to do, but when you pay a substantial sum for software, you expect a more comprehensive solution.</description>
		<content:encoded><![CDATA[<p>There are too many posts for me to check if someone already said this, but &#8230; your wish list is the exact anecdotal evidence that Adobe needs to continue selling Photoshop as the needed complementary software to Lightroom. As a former film and now digital photographer, I hope Adobe listens to folks like you and us who want and deserve more well-rounded software solutions. I know wish lists will never end as we will continue to find things we want our software to do, but when you pay a substantial sum for software, you expect a more comprehensive solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.scottkelby.com/blog/2008/archives/932/comment-page-7#comment-104498</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Sun, 07 Dec 2008 15:03:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottkelby.com/blog/2008/archives/932#comment-104498</guid>
		<description>As to all your requests for the Slideshow, its in the ProShow Plugin for Lightroom.  I use Proshow Producer on the PC and it rocks slideshows. Check it out I think you will be impressed.</description>
		<content:encoded><![CDATA[<p>As to all your requests for the Slideshow, its in the ProShow Plugin for Lightroom.  I use Proshow Producer on the PC and it rocks slideshows. Check it out I think you will be impressed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: justin</title>
		<link>http://www.scottkelby.com/blog/2008/archives/932/comment-page-7#comment-94498</link>
		<dc:creator>justin</dc:creator>
		<pubDate>Tue, 21 Oct 2008 20:07:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottkelby.com/blog/2008/archives/932#comment-94498</guid>
		<description>I&#039;m with you buddy..
AWESOME ideas... 
Fingers crossed they come through..</description>
		<content:encoded><![CDATA[<p>I&#8217;m with you buddy..<br />
AWESOME ideas&#8230;<br />
Fingers crossed they come through..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Hawkins</title>
		<link>http://www.scottkelby.com/blog/2008/archives/932/comment-page-7#comment-89837</link>
		<dc:creator>Phil Hawkins</dc:creator>
		<pubDate>Thu, 02 Oct 2008 05:57:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottkelby.com/blog/2008/archives/932#comment-89837</guid>
		<description>for the &quot;Edit In&quot; feature, I shoot in RAW, and I use Capture One 4.0 for my conversions.  At present, it only allows &quot;edit in&quot; for TIFs of JPGs.  I cannot move to a RAW converter for a RAW conversion outside of Lightroom 2.0</description>
		<content:encoded><![CDATA[<p>for the &#8220;Edit In&#8221; feature, I shoot in RAW, and I use Capture One 4.0 for my conversions.  At present, it only allows &#8220;edit in&#8221; for TIFs of JPGs.  I cannot move to a RAW converter for a RAW conversion outside of Lightroom 2.0</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: j.pishnery</title>
		<link>http://www.scottkelby.com/blog/2008/archives/932/comment-page-7#comment-83860</link>
		<dc:creator>j.pishnery</dc:creator>
		<pubDate>Fri, 29 Aug 2008 13:56:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottkelby.com/blog/2008/archives/932#comment-83860</guid>
		<description>Sorry if this has already been discussed or is already in V2:

CMYK support for the library - I do a lot of conversions for clients and would really like to have them in the library.

3F / Hasselblad file support - I&#039;d also like to be able to find these in the library and convert to DNG thru Lightroom</description>
		<content:encoded><![CDATA[<p>Sorry if this has already been discussed or is already in V2:</p>
<p>CMYK support for the library &#8211; I do a lot of conversions for clients and would really like to have them in the library.</p>
<p>3F / Hasselblad file support &#8211; I&#8217;d also like to be able to find these in the library and convert to DNG thru Lightroom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dinesh.n.sharma</title>
		<link>http://www.scottkelby.com/blog/2008/archives/932/comment-page-7#comment-82740</link>
		<dc:creator>dinesh.n.sharma</dc:creator>
		<pubDate>Sun, 24 Aug 2008 13:24:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottkelby.com/blog/2008/archives/932#comment-82740</guid>
		<description>hi scott i would like to know something. I bought photoshop cs2 2 years back a licensed version in india through a authoroised distributor when the distributor installed it i did not have an e mail id so he registered it in his e mail instead. will this create a problem for me.</description>
		<content:encoded><![CDATA[<p>hi scott i would like to know something. I bought photoshop cs2 2 years back a licensed version in india through a authoroised distributor when the distributor installed it i did not have an e mail id so he registered it in his e mail instead. will this create a problem for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Burkholder</title>
		<link>http://www.scottkelby.com/blog/2008/archives/932/comment-page-7#comment-80662</link>
		<dc:creator>Jeff Burkholder</dc:creator>
		<pubDate>Fri, 15 Aug 2008 05:12:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottkelby.com/blog/2008/archives/932#comment-80662</guid>
		<description>LR 2 is an awesome Beta application. I love it! Hate it (see my blog: http://blog.lifeimagesproductions.com/ ).

After spending 3 days pulling my hair out (with LR2 crashing, hanging system) going through tech support, forums, Q&amp;A with many other photographers. I finally figured out the problem (again see my blog).

So, my question is. Is 2.0 worth paying for Beta software still? I say for the pros out there. Stick with 1.4 and wait for 2.1 update.
-jeff</description>
		<content:encoded><![CDATA[<p>LR 2 is an awesome Beta application. I love it! Hate it (see my blog: <a href="http://blog.lifeimagesproductions.com/" rel="nofollow">http://blog.lifeimagesproductions.com/</a> ).</p>
<p>After spending 3 days pulling my hair out (with LR2 crashing, hanging system) going through tech support, forums, Q&amp;A with many other photographers. I finally figured out the problem (again see my blog).</p>
<p>So, my question is. Is 2.0 worth paying for Beta software still? I say for the pros out there. Stick with 1.4 and wait for 2.1 update.<br />
-jeff</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Burkholder</title>
		<link>http://www.scottkelby.com/blog/2008/archives/932/comment-page-7#comment-79843</link>
		<dc:creator>Jeff Burkholder</dc:creator>
		<pubDate>Sun, 10 Aug 2008 17:35:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottkelby.com/blog/2008/archives/932#comment-79843</guid>
		<description>- Networking; YES! to have all my photos n a server, or networked storage device; like Buffaloâ€™s 2 TB network stations) and to have my assistant working on one project while I work on another. Now that&#039;s efficiency.

- Softproofing: most definitely! Proof for web, for printer driver. The ability is there, they just need to program that hookup. Photoshop does it pretty easily. The engineâ€™s built.

- Books: youâ€™d think the creators of packages, Adobe, would have done this. Photoelements 2 had it, as a separate app. Just get that team into the LR3 team. Though, lets also make this module NOT load with LR. Have it be a button to call out to. Because think of itâ€¦ youâ€™re loading all those templates. Which BTWâ€¦ lets do with the Web module. Have it load that stuff when we need it. Not into memory upon opening.

- Noise reduction;  Iâ€™m blown away that 2.0 vers. really doesnâ€™t approach it that great still. Must be a 3rd party contract deal that they have to work around.

- Light table: yes, I do say I miss the old slide days. Where Iâ€™d move my images to the top row which was my â€˜picksâ€™ and I can really compare better the 2nd, 3rd, 4th variables. Weâ€™re visual people, it works better for us that way.

- Shooting tethered: Iâ€™ve said in my lifeâ€¦ Why would I need to shoot tethered? Then I had a restaurant client where we were shooting over 200 food shots. I had two sets going and thatâ€™s when I said. BOY, sure would be cool to be able to be tethered. YES! This should be a feature. Or at least a downloadable updateâ€¦. It canâ€™t be that difficult to do. 

- Keyboard shortcuts change: how about the ability to change all the shortcuts. Or hey, edit your own sets. Thatâ€™s possible!

- Place able graphics: would be nice to have it like an object that can be moved and them you â€˜commitâ€™ to it when processed. Multiple objects would be awesome but, if not possible, I make my object in PS and then have it available to LR.

Slideshow options:
 Yes to everything. How about a simple timeline too. Something that every marker is the next photo and we can move that marker to the timing we want. Pull it from Premiere Elements, the cheap video app. That would solve 80% of everyoneâ€™s needs.

- That&#039;s my wish and agreement. It&#039;s geting there. Maybe LR2.5 will help us all.</description>
		<content:encoded><![CDATA[<p>- Networking; YES! to have all my photos n a server, or networked storage device; like Buffaloâ€™s 2 TB network stations) and to have my assistant working on one project while I work on another. Now that&#8217;s efficiency.</p>
<p>- Softproofing: most definitely! Proof for web, for printer driver. The ability is there, they just need to program that hookup. Photoshop does it pretty easily. The engineâ€™s built.</p>
<p>- Books: youâ€™d think the creators of packages, Adobe, would have done this. Photoelements 2 had it, as a separate app. Just get that team into the LR3 team. Though, lets also make this module NOT load with LR. Have it be a button to call out to. Because think of itâ€¦ youâ€™re loading all those templates. Which BTWâ€¦ lets do with the Web module. Have it load that stuff when we need it. Not into memory upon opening.</p>
<p>- Noise reduction;  Iâ€™m blown away that 2.0 vers. really doesnâ€™t approach it that great still. Must be a 3rd party contract deal that they have to work around.</p>
<p>- Light table: yes, I do say I miss the old slide days. Where Iâ€™d move my images to the top row which was my â€˜picksâ€™ and I can really compare better the 2nd, 3rd, 4th variables. Weâ€™re visual people, it works better for us that way.</p>
<p>- Shooting tethered: Iâ€™ve said in my lifeâ€¦ Why would I need to shoot tethered? Then I had a restaurant client where we were shooting over 200 food shots. I had two sets going and thatâ€™s when I said. BOY, sure would be cool to be able to be tethered. YES! This should be a feature. Or at least a downloadable updateâ€¦. It canâ€™t be that difficult to do. </p>
<p>- Keyboard shortcuts change: how about the ability to change all the shortcuts. Or hey, edit your own sets. Thatâ€™s possible!</p>
<p>- Place able graphics: would be nice to have it like an object that can be moved and them you â€˜commitâ€™ to it when processed. Multiple objects would be awesome but, if not possible, I make my object in PS and then have it available to LR.</p>
<p>Slideshow options:<br />
 Yes to everything. How about a simple timeline too. Something that every marker is the next photo and we can move that marker to the timing we want. Pull it from Premiere Elements, the cheap video app. That would solve 80% of everyoneâ€™s needs.</p>
<p>- That&#8217;s my wish and agreement. It&#8217;s geting there. Maybe LR2.5 will help us all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Fisher</title>
		<link>http://www.scottkelby.com/blog/2008/archives/932/comment-page-7#comment-79603</link>
		<dc:creator>Michael Fisher</dc:creator>
		<pubDate>Sat, 09 Aug 2008 13:40:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottkelby.com/blog/2008/archives/932#comment-79603</guid>
		<description>Something very infuriating is happening with Lightroom, and I am sure that I am not the only one running into this.

In a nutshell, if you edit an image in LR, even using the sRGB color space, the image will not look anywhere near as good when viewed on a browser like Firefox or Internet Explorer, especially with regard to color quality and saturation.

In other words, if you shoot in sRGB, edit in sRGB, and export in sRGB ... the image will look great in LR, will look great in Safari, will look great in iPhoto, will look great in Preview ... but will dramatically diminish in color quality if viewed in Firefox or Internet Explorer.

If I set my color space to &quot;Monitor RGB - iMac&quot; in PhotoShop, then I get exactly what I see on-screen if I export a JPG and view it in web browsers or any other software.

This makes sense, because I guess I&#039;m telling it, &quot;Use the same color  
space that my monitor uses.&quot;   So if I do my Photoshop work in  
that color space, my exported JPG&#039;s will look like they did to my eye  
when I created them.

The first catch: LightRoom has no such option.  It only has:
sRGB
Prophoto
Adobe RGB

The closest of those is sRGB, but we&#039;ve seen how that loses saturation  
and warmth when exported, compared to the monitor.  So as far as I can  
tell, there is no way to adjust something in LR and have it come out  
looking in a web browser like it does on-screen during editing.   This  
is infuriating.

The second catch:  If I did my work in Monitor RGB, and then later  
wanted to make a print of the image, I may have sacrified some of the  
potential quality by working in Monitor RGB which has less color range  
apparently than Adobe or Prophoto.   I could still convert it to one  
of those and make a nice print (I&#039;m assuming), but perhaps not quite  
as nice as I could have made if I worked in one of those modes all  
along.  On the other hand, if I worked in one of those modes, my web  
JPG&#039;s would suck and that&#039;s what I do with 99% of my images.  But this  
is a minor issue for me compared to the other.

I&#039;m starting to conclude:  There is no way to work on an image that is  
destined for both web and print without basically doing the work  
twice.  Once adjusted for the web, and once adjusted for print.

And if I am working on an image for the web, I can get a very accurate  
appearance in PhotoShop by using the Monitor color space.  But in LR I  
have no way of doing that.  That&#039;s the kicker. The best I can do in LR  
is sRGB, then export to PhotoShop and adjust it some more until I get  
the look I want.  Which kind of defeats the purpose of being able to  
do all this editing in LR!

I would love to hear from anyone who has an idea for how to fix this, or would love for Scott to work his magic with Adobe and get them to release an update that corrects this problem.</description>
		<content:encoded><![CDATA[<p>Something very infuriating is happening with Lightroom, and I am sure that I am not the only one running into this.</p>
<p>In a nutshell, if you edit an image in LR, even using the sRGB color space, the image will not look anywhere near as good when viewed on a browser like Firefox or Internet Explorer, especially with regard to color quality and saturation.</p>
<p>In other words, if you shoot in sRGB, edit in sRGB, and export in sRGB &#8230; the image will look great in LR, will look great in Safari, will look great in iPhoto, will look great in Preview &#8230; but will dramatically diminish in color quality if viewed in Firefox or Internet Explorer.</p>
<p>If I set my color space to &#8220;Monitor RGB &#8211; iMac&#8221; in PhotoShop, then I get exactly what I see on-screen if I export a JPG and view it in web browsers or any other software.</p>
<p>This makes sense, because I guess I&#8217;m telling it, &#8220;Use the same color<br />
space that my monitor uses.&#8221;   So if I do my Photoshop work in<br />
that color space, my exported JPG&#8217;s will look like they did to my eye<br />
when I created them.</p>
<p>The first catch: LightRoom has no such option.  It only has:<br />
sRGB<br />
Prophoto<br />
Adobe RGB</p>
<p>The closest of those is sRGB, but we&#8217;ve seen how that loses saturation<br />
and warmth when exported, compared to the monitor.  So as far as I can<br />
tell, there is no way to adjust something in LR and have it come out<br />
looking in a web browser like it does on-screen during editing.   This<br />
is infuriating.</p>
<p>The second catch:  If I did my work in Monitor RGB, and then later<br />
wanted to make a print of the image, I may have sacrified some of the<br />
potential quality by working in Monitor RGB which has less color range<br />
apparently than Adobe or Prophoto.   I could still convert it to one<br />
of those and make a nice print (I&#8217;m assuming), but perhaps not quite<br />
as nice as I could have made if I worked in one of those modes all<br />
along.  On the other hand, if I worked in one of those modes, my web<br />
JPG&#8217;s would suck and that&#8217;s what I do with 99% of my images.  But this<br />
is a minor issue for me compared to the other.</p>
<p>I&#8217;m starting to conclude:  There is no way to work on an image that is<br />
destined for both web and print without basically doing the work<br />
twice.  Once adjusted for the web, and once adjusted for print.</p>
<p>And if I am working on an image for the web, I can get a very accurate<br />
appearance in PhotoShop by using the Monitor color space.  But in LR I<br />
have no way of doing that.  That&#8217;s the kicker. The best I can do in LR<br />
is sRGB, then export to PhotoShop and adjust it some more until I get<br />
the look I want.  Which kind of defeats the purpose of being able to<br />
do all this editing in LR!</p>
<p>I would love to hear from anyone who has an idea for how to fix this, or would love for Scott to work his magic with Adobe and get them to release an update that corrects this problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nigel Heath</title>
		<link>http://www.scottkelby.com/blog/2008/archives/932/comment-page-7#comment-78727</link>
		<dc:creator>Nigel Heath</dc:creator>
		<pubDate>Mon, 04 Aug 2008 18:37:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottkelby.com/blog/2008/archives/932#comment-78727</guid>
		<description>Hi.
First, I want to express my appreciation of your books of which I have several and expect in time to buy more.
Second, I want to ask if you have considered writing some books on any of :-
       1. DxO Optics Pro with Lightroom &amp;/or CS3.
       2. HDR &amp;/or panorama photography with Photomatrix &amp;/or CS3
       3. Photoshop plug-ins in general
Perhaps you already have writen on these,if so please tell me where.
Regards
NRHeath</description>
		<content:encoded><![CDATA[<p>Hi.<br />
First, I want to express my appreciation of your books of which I have several and expect in time to buy more.<br />
Second, I want to ask if you have considered writing some books on any of :-<br />
       1. DxO Optics Pro with Lightroom &amp;/or CS3.<br />
       2. HDR &amp;/or panorama photography with Photomatrix &amp;/or CS3<br />
       3. Photoshop plug-ins in general<br />
Perhaps you already have writen on these,if so please tell me where.<br />
Regards<br />
NRHeath</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adobe Releases Lightroom 2 with Local Correction and Many Other New Features : The Imaging Buffet</title>
		<link>http://www.scottkelby.com/blog/2008/archives/932/comment-page-7#comment-77161</link>
		<dc:creator>Adobe Releases Lightroom 2 with Local Correction and Many Other New Features : The Imaging Buffet</dc:creator>
		<pubDate>Tue, 29 Jul 2008 06:38:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottkelby.com/blog/2008/archives/932#comment-77161</guid>
		<description>[...] Links: Great article by Scott Kelby with requests for Lightroom 2 from Jan. 2008. Quite a few of the requests found their way into LR 2. Thanks Scott (and your readers)! [...]</description>
		<content:encoded><![CDATA[<p>[...] Links: Great article by Scott Kelby with requests for Lightroom 2 from Jan. 2008. Quite a few of the requests found their way into LR 2. Thanks Scott (and your readers)! [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
