Lightroom 3 - WOW!!

[bigdazzler]

The noise reduction is possibly the best on planet!

ooooh ... big call mate.

[wattsgallery]

I also like the constrain file size on export feature which helps to meet website uplink requirements etc (just note that it seems to be a little out if you add watermark etc so just need to select a bit smaller than you need - ie. if the max file size you need is 250kb then maybe restrain to 200kb as I have noticed it can add a bit).

[kiwi]

Personally I still use Nik Dfine for NR - it's better in my opinion

[Lani]

The noise reduction is possibly the best on planet!

Hmmmm.....a little bit of an overstatement perhaps?

It is definitely much better than LR2, but 3rd party applications such as Neat Image have a lot more control, I reckon.

[Top]

Hmmmm.....a little bit of an overstatement perhaps?

It is definitely much better than LR2, but 3rd party applications such as Neat Image have a lot more control, I reckon.

Haha, definitely an overstatement, however I have tried numerous 3rd party applications including Neat Image, Noise Ninja, Topaz Denoise and Imagetonic Noiseware Professional.

Noiseware is the one I kept until recently after purchasing Photoshop CS5 and LR3

I agree they have more controls but IMHO their effects are not as good as the LR3.

Although I tend to use the noise reduction algorithm in ACR6 a lot more often now as it appears to be the same as the one in LR3.

[etherial]

I also like the constrain file size on export feature which helps to meet website uplink requirements etc (just note that it seems to be a little out if you add watermark etc so just need to select a bit smaller than you need - ie. if the max file size you need is 250kb then maybe restrain to 200kb as I have noticed it can add a bit).

I thought this feature was good, but I'm having a little trouble with it. I have set a maximum of 250kB for files to upload to AP but they come in at 255 or 260kB. Even dropping the setting to 200 still gave me the 255. The only way to get it down was to reduce the pixels on the longest edge from 1024 to say 800.

[Lani]

I thought this feature was good, but I'm having a little trouble with it. I have set a maximum of 250kB for files to upload to AP but they come in at 255 or 260kB. Even dropping the setting to 200 still gave me the 255. The only way to get it down was to reduce the pixels on the longest edge from 1024 to say 800.

Yep, I have noticed that with the export for email function last night, maybe it is including some exif info that is nudging up the file size?

[etherial]

It seems to me that it can only compress the original to a certain point when you specify 1024 pixels, hence you have to drop the dimensions to get the file size down.

Sometimes it comes up with an error to say "can't meet your settings" (or something like that) but not always. I'm not sure how I managed to get that. Anyway, it is a great program and I love it. To get around this I've set up an area in my Smugmug site for forum posts that his private/hidden from the public and I will just upload to there and link to photos, so the 250kB limit isn't an issue then.

[sanpedro667]

I'm thinking of upgrading to LR3, I current use noise ninja for noise reduction is the built in feature in LR3 equivalent? If it is would save heaps of time.

[AdamR]

I love LR2 I think its brilliant. Since LR2 came out 99% of my photos are edited only there. Looking forward to LR3

[kiwi]

I'm thinking of upgrading to LR3, I current use noise ninja for noise reduction is the built in feature in LR3 equivalent? If it is would save heaps of time.

I find it pretty good really, much improved anyhow. I think for the majority if uses it replaced the plug-ins incl ninja

The big difference probably is that it does not analyse the image for noise and then autoapply
Easy enough to download a trial and do some testing side by side

[dieselpower]

As kiwi said - no noise profiles so it doesn't auto detect what the noise levels should be. It's all dependent on the user touching up the sliders to suit. That said, you could set the noise levels for each ISO appropriately and save that into a preset and load that on to each image. Not as fast as noise ninja but should be quicker than manual adjustments.

[bigdazzler]

Im about to upgrade to LR3 shortly .... any issues with migrating your catalogues ??

[kiwi]

As kiwi said - no noise profiles so it doesn't auto detect what the noise levels should be. It's all dependent on the user touching up the sliders to suit. That said, you could set the noise levels for each ISO appropriately and save that into a preset and load that on to each image. Not as fast as noise ninja but should be quicker than manual adjustments.

You can actually use the ISO info in the EXIF on import to adjsut the default NR settings used

Im about to upgrade to LR3 shortly .... any issues with migrating your catalogues ??

No issue at all, of course the LR3 beta catalogues I had did not migrate and I had to export/import

[bigdazzler]

OK good ... I didnt install the beta so no issue there for me.

[dieselpower]

You can actually use the ISO info in the EXIF on import to adjsut the default NR settings used

Well, there you go. I will have to investigate this more thoroughly as that will make life easier for me!

[essaytee]

I'm a new user to LR3 and still to learn all the editing features, if that's possible. I was first looking for a catalogue type system and in the end LR won out.

I started a thread here regarding a file renaming bug. The below effectively summarises that thread.

Just be aware that there is a bug in the current version (LR3) regarding file renaming on import (I stress 'On Import' NOT when file renaming subsequently). In short, if you rename photos which incorporate a date, the date will be advanced by your time zone value. Therefore, here in Melbourne, 10 hours are added. So for any photos taken after 2 pm will in fact be renamed with a date one day later. To confirm this, import photos from a card, incorporate a time value in the name, this will clearly show an incorrect date/time in the file name. The solution or workaround is to rename after import. I'm hoping this will be addressed in the next update.