The GetDPI Photography Forum

Great to see you here. Join our insightful photographic forum today and start tapping into a huge wealth of photographic knowledge. Completing our simple registration process will allow you to gain access to exclusive content, add your own topics and posts, share your work and connect with other members through your own private inbox! And don’t forget to say hi!

lightroom 3.0 beta

geesbert

New member
I started to use it and it's nice, can't wait for the alpha version...but still no soft proofing!

I wonder now: I am using lightroom since V1 and bought the upgrade to v2, therefor I didn't need to download it for my m9.

So my thinking now is: once LR3 hit release, I will use my M9 Voucher, so I don't have to pay for the upgrade.

but then I just read in LFI, that you always get the current version, so does that include major otherwise chargeable upgrades?
 

Reynolds

Workshop Member
I have been with LR for a couple of years. They have always updated me to the current version since the initial purchase. I am now at LR2.5 and will upgrade, presumably at no extra charge, to 3.0 after the Beta. I would say go ahead and buy 2.5 now and expect no additional charges for 3.0. The more experienced here may have a different view??
 

jonoslack

Active member
I have been with LR for a couple of years. They have always updated me to the current version since the initial purchase. I am now at LR2.5 and will upgrade, presumably at no extra charge, to 3.0 after the Beta. I would say go ahead and buy 2.5 now and expect no additional charges for 3.0. The more experienced here may have a different view??
Hi Reynolds
Yes - you'll have to pay for the upgrade. Adobe always make you pay for full number upgrades. They aren't usually cheap either.

If you've just got an M9, and you want to use version 3, then I would have thought you were best to keep to the beta until the full version is released, then register your number.

Seems like a no- brainer to me!
 

Reynolds

Workshop Member
And, according to Luminous Landscape:

"LR3 Beta supports a number of new cameras, with not only raw support but profiles. This includes the recent Canon G11, Panasonic GF1 and Leica M9. M9 owners will be pleased to note that there is now an M9 profile, which does a very nice job with the new camera."
 

Diane B

New member
I think so too---the real extra goodies (like gradient and brush tool in 2.0) seem to come with final version.

My issue is still--can't open Print module. I've followed 2 suggestions but neither work. Too bad as print is important to me. Not sure what the issue is. I'm going to install it on my Vista laptop and see if I have the same problem (as on my XP Pro big machine built for photo editing).
 

stevem8

New member
I downloaded the beta and am a diehard adobe bridge/cs3 user. I find it much easier to browse my files in bridge and process in CS3 using ACR than using Lightroom so far. Lightroom seems much slower to me. Just took me 20 minutes to process one image.

I am going to mess with it more and see if it gets better as I learn more but for me, CS3 seems much easier and more versatile. Did anyone else feel this way when first using LR?
 

Robert Campbell

Well-known member
It did take a while to get the hang of LR; but once used to it, it is so much easier than Bridge>ACR>CS3 -- even if Bridge>ACR is essentially what happens after import into LR. Many people don't find much use for CS if they have LR -- except for localised adjustments that the gradient/spot/brush tools can't do.

LR3beta does seem slower than LR2.5, but I expect the final release will be better.
 

jonoslack

Active member
I downloaded the beta and am a diehard adobe bridge/cs3 user. I find it much easier to browse my files in bridge and process in CS3 using ACR than using Lightroom so far. Lightroom seems much slower to me. Just took me 20 minutes to process one image.

I am going to mess with it more and see if it gets better as I learn more but for me, CS3 seems much easier and more versatile. Did anyone else feel this way when first using LR?
HI Steve
It sounds like you might be missing the point rather. (or possibly I'm missing your point).

Presumably using CS3 you open the files using ACR, then make any adjustments and save them as TIFF or JPG files?

Forgive me if I'm being stupidly obvious, but so many people I've talked to just use Lightroom or Aperture as a converter program in their same workflow.

The idea is that you only convert the files when you actually need them, so you leave the files as raw, if you need to send a bunch of files to a client, you export them, burn them to a DVD, and then delete them - if you want web output you output as a web page.

When I was using photoshop, I used to have 4 or more folders:
1. original RAW
2. Print output files (after conversion)
3. web output files
4 thumbnails

One of the major problems was that if you revisit a raw file, then you have to decide whether to make another lot of versions (for instance for a black and white copy)


Nowadays I have one folder
1. originals

If I need web output then I do that, similar for printing - it means that the 'corrected' version is always based on the original RAW file.

If I need a 'fixed state' (for instance for a wedding) then I'll make up an album and put 'versions' in the album (but they still only reference the original raw file).

The point is that lightroom IS slow if you are using it in the same way as CS3 . . . but not if you make the adjustments and versions, and only do the output when you need it for a purpose.
 

Reynolds

Workshop Member
Thanks, Jono! That clears up the cost issue for me and Gees. BTW, I still have my WATE and am STILL waiting on the M9. Can you send me one of your spares?? LOL
 

ptomsu

Workshop Member
HI Steve
It sounds like you might be missing the point rather. (or possibly I'm missing your point).

Presumably using CS3 you open the files using ACR, then make any adjustments and save them as TIFF or JPG files?

Forgive me if I'm being stupidly obvious, but so many people I've talked to just use Lightroom or Aperture as a converter program in their same workflow.

The idea is that you only convert the files when you actually need them, so you leave the files as raw, if you need to send a bunch of files to a client, you export them, burn them to a DVD, and then delete them - if you want web output you output as a web page.

When I was using photoshop, I used to have 4 or more folders:
1. original RAW
2. Print output files (after conversion)
3. web output files
4 thumbnails

One of the major problems was that if you revisit a raw file, then you have to decide whether to make another lot of versions (for instance for a black and white copy)


Nowadays I have one folder
1. originals

If I need web output then I do that, similar for printing - it means that the 'corrected' version is always based on the original RAW file.

If I need a 'fixed state' (for instance for a wedding) then I'll make up an album and put 'versions' in the album (but they still only reference the original raw file).

The point is that lightroom IS slow if you are using it in the same way as CS3 . . . but not if you make the adjustments and versions, and only do the output when you need it for a purpose.
Jono,

I agree on this, but how would you handle then files coming from Hasselblad or Phase, which need vendor specific corrections (lens correction etc. Then you need to make a TIFF with the corrections and continue work in another preferred SW - say Photoshop.
 

jonoslack

Active member
Jono,

I agree on this, but how would you handle then files coming from Hasselblad or Phase, which need vendor specific corrections (lens correction etc. Then you need to make a TIFF with the corrections and continue work in another preferred SW - say Photoshop.
Hello Peter
Thank you for chipping in.
I'm not using either of these, but I do use Silver efex pro / Photoshop / Vivezza. and I'm sure that the procedure would be the same.

you can set a number of 'external' editors such as this in preferences. You can then choose to edit in whatever you need - LR (or Aperture) will create the tiff file for you (either including any variations you've already made, or not, as you choose). This is then saved with the original file, and then opened in whatever.

Obviously you then have the extra space for the tiff file (you can choose PSD or other formats if you choose). However, you see them together, and both 'versions' are available, and in your library.
 

jonoslack

Active member
Thanks, Jono! That clears up the cost issue for me and Gees. BTW, I still have my WATE and am STILL waiting on the M9. Can you send me one of your spares?? LOL
HI Reynolds - sorry it hasn't turned up yet (I'm still waiting for the one I ordered as well).
 

Diane B

New member
Hello Peter
Thank you for chipping in.
I'm not using either of these, but I do use Silver efex pro / Photoshop / Vivezza. and I'm sure that the procedure would be the same.

you can set a number of 'external' editors such as this in preferences. You can then choose to edit in whatever you need - LR (or Aperture) will create the tiff file for you (either including any variations you've already made, or not, as you choose). This is then saved with the original file, and then opened in whatever.

Obviously you then have the extra space for the tiff file (you can choose PSD or other formats if you choose). However, you see them together, and both 'versions' are available, and in your library.
I've not tried any of the 'round trips' (as many call them) to PS or other editing apps in 3.0--in fact, I think I read somewhere that its not available yet to set up in preferences for CS3 (which I use as external--first time since vs. 2 or 3 that I have not upgraded since I do so much in LR now). The round trip is useful for me to occasionally use plug ins, a bit more local work--and I do a trip to PS to use my frame action for Pbase--but I don't save the tiff and can just delete it (in fact, I think if I used CS4 it wouldn't even create the tiff unless I did save it--but can't remember). I don't output anything until I need it--a resized jpeg for export wtih appropriate sharpening to email, etc.--or a print--where sharpening again is done based on paper, size, etc. So--the RAW just sits there with the info but there is no additional file--until if and when you choose to use that file for output in some manner.

Besides the Develop module I find a lot of use for the Library (database)--collections, etc.--and search based on metadata or keywords (which won't work unless you input keywords LOL--but in 2.5 they made it even easier to do that on import). I haven't explored 3.0 in Library at all--and just a bit in develop so am basing this just on 2.5.

Diane
 

jonoslack

Active member
Hi Diane
I've not tried any of the 'round trips' (as many call them) to PS or other editing apps in 3.0--in fact, I think I read somewhere that its not available yet to set up in preferences for CS3 (which I use as external--first time since vs. 2 or 3 that I have not upgraded since I do so much in LR now).
They're all working fine on the Mac - first thing I did (as I use them often in Aperture), was to set up the 'round trips' to Vivezza, Silver efex pro and CS3.
The round trip is useful for me to occasionally use plug ins, a bit more local work--and I do a trip to PS to use my frame action for Pbase--but I don't save the tiff and can just delete it (in fact, I think if I used CS4 it wouldn't even create the tiff unless I did save it--but can't remember). I don't output anything until I need it--a resized jpeg for export wtih appropriate sharpening to email, etc.--or a print--where sharpening again is done based on paper, size, etc. So--the RAW just sits there with the info but there is no additional file--until if and when you choose to use that file for output in some manner.
I'm the same here - trying to keep to the original folder and as few files as possible.
Besides the Develop module I find a lot of use for the Library (database)--collections, etc.--and search based on metadata or keywords (which won't work unless you input keywords LOL--but in 2.5 they made it even easier to do that on import). I haven't explored 3.0 in Library at all--and just a bit in develop so am basing this just on 2.5.

Diane
Again - I've got presets setup in LR3, and it works okay . . . but it doesn't feel anything like as 'natural' doing selections as I found it in Aperture - especially selecting combinations of keywords . . . you know . . . People / Crete / Livaniana including all which have all keywords and none which don't. . . but perhaps I haven't really gone deep enough yet.
 

Robert Campbell

Well-known member
My round trips were automatically lifted from LR2.5, though the direct to SilverEfex gives a warning that it doesn't work -- but it does.

I don't understand your problem with the keywording, Jono. There are keywords sets you can make and LR usually offers suggestions.
 

Martin S

New member
Unfortunately, the new version 3.0 will only run on Intel based MACs. I have a PPC based MAC so no go with 3.0.

I hope that Adobe will make new versions of Camera RAW in PPC version so I can make use of the new camera profiles.

Do you think that the exclusive Intel version will be an indication for the rest of Adobe upgrades??

Martin
 

jonoslack

Active member
I don't understand your problem with the keywording, Jono. There are keywords sets you can make and LR usually offers suggestions.
Hi Robert
it isn't adding them (works fine) it's filtering on them which doesn't seem to be so good (correct me if I'm wrong).

without actually remembering the key words and typing them manually, how would I get to all the Chihuahua pictures that I'd taken in Cornish Beaches in Thunderstorms?
 

Robert Campbell

Well-known member
This should work -- it's how I do it, there may be easier ways:

In the keywords panel to the left, find Chihuaha, click on the arrow at the right -- all Chihuaha pix will appear [unless you have already filters active]

go to the very top panel [you may have to hit \ to view it], select metadata

In the filter bar at the top the left hand one will say Keywords, and have Chihuaha highlighted

Move to the next one along, select Keywords -- only those second keywords that you have entered for these pix will appear -- scroll to Cornish Beaches and select it -- all pix of Chihuahas on Cornish beaches appear

Move to the third, select keywords, scroll to Thunderstorms [again, not all keywords appear, only those that have been entered] select it -- only those pix of the dogs on the beach in a thunderstorm will appear

And you can use the fourth for more keywords, or to find which camera you used or whatever

I don't think it's easily possible to have more than 4 combinations -- you would have to make a quick selection [or a collection] of the 4, then open that and filter more.

BTW, I didn't think Blue was a Chihuaha -- am I missing something?
 

jonoslack

Active member
This should work -- it's how I do it, there may be easier ways:

In the keywords panel to the left, find Chihuaha, click on the arrow at the right -- all Chihuaha pix will appear [unless you have already filters active]

go to the very top panel [you may have to hit \ to view it], select metadata

In the filter bar at the top the left hand one will say Keywords, and have Chihuaha highlighted

Move to the next one along, select Keywords -- only those second keywords that you have entered for these pix will appear -- scroll to Cornish Beaches and select it -- all pix of Chihuahas on Cornish beaches appear

Move to the third, select keywords, scroll to Thunderstorms [again, not all keywords appear, only those that have been entered] select it -- only those pix of the dogs on the beach in a thunderstorm will appear

And you can use the fourth for more keywords, or to find which camera you used or whatever

I don't think it's easily possible to have more than 4 combinations -- you would have to make a quick selection [or a collection] of the 4, then open that and filter more.

BTW, I didn't think Blue was a Chihuaha -- am I missing something?
Thank you . . how could I have missed it :ROTFL: Still, if it works . .

understanding is a real issue . . and there's you not realising that Blue is a Chihuahua
 
Top