Lightroom 2.0 Public Beta Released

[PixelMagic]

The Lightroom 2.0 beta is now available and can be downloaded here:

http://labs.adobe.com/technologies/lightroom/


The announced feature set looks really good:

* Localized corrections — Enhance specific areas of an image for unsurpassed nondestructive flexibility and control reminiscent of the traditional darkroom dodge and burn experience.
* Improved organizational tools — Find the images you need quickly and easily.
* Multiple monitor support — Add an additional monitor to efficiently manage photographic workflow and presentation.
* Flexible print package functionality — Create custom layouts containing multiple sizes of a photograph on a single page.
* 64-bit support — Lightroom 2.0 now takes advantage of the latest hardware architectures with improved memory handling and performance.

[motion_projekt]

yay! dl-ing now!

[xmacvicar]

Also downloading! yeowwwwww

[davidcrebelxt]

Retouch tool very impressive (even at just 10 minutes of use on a jpeg, I was able to use it to recover a blown out sky, and add some saturation to it without affecting other areas.)

Still no checkboxes next to keywords. :(

In fact, it appears that displaying images based on keywords actually got more difficult than before...

Not to mention version 2 already? I'm quite surprised... (or am I? :rolleyes: ) Hope we beta... ahem... version 1 users get a discount.

[Victoria Bampton]

As usual, I've done a long list of changes:
http://www.victoriabampton.com/lightroom20beta1whatsnew.htm

And there are updated shortcut sheets for download at the bottom of that page too.

[Victoria Bampton]

Version 2 BETA David. It will change further before full release.

[xmacvicar]

Wow,

Playing for 30 mins now and I must say I am impressed. I like it - it feels 'snappier' or faster.

The local corrections are very neat, dodging and burning selective at a RAW level - tinting and color changing locally, clarity!!

This could be big for wedding and portrait photographers (well anyone reallY).... reverse the clarity slider to produce a 'soft focus' effect and then paint clarity back into the eyes and mouth!!! MADNESS

As well, the Vignetting is alot slicker, and feels 'better' (hard to make sense of this so soon). The post crop vignette fix is a long time coming.

Great Beta release Adobe

[col4bin]

layout still looks cluttered.

[FlyingPhotog]

layout still looks cluttered.

I think dual monitor support (if one goes that route...I understand the $$$ involved) will help this...

Dual Monitor (actually dual display..you can have a second window open on one monitor) is aimed at making LR more like Aperture(?)

[col4bin]

I think dual monitor support (if one goes that route...I understand the $$$ involved) will help this...

Dual Monitor (actually dual display..you can have a second window open on one monitor) is aimed at making LR more like Aperture(?)

I have dual displays but one of those is amy laptop which is small. With Aperture's full screen edit mode, I do not need to even utilize dual displays. Real estate is maximized on my 23" monitor.

Any way, I am not here to bash LR. I hope that folks find LR a worthwhile tool and enjoyable to use. For me, Aperture 2 set the bar quite high and the chances of me switching tools again is quite slim.

[FlyingPhotog]

I have dual displays but one of those is amy laptop which is small. With Aperture's full screen edit mode, I do not need to even utilize dual displays. Real estate is maximized on my 23" monitor.

Any way, I am not here to bash LR. I hope that folks find LR a worthwhile tool and enjoyable to use. For me, Aperture 2 set the bar quite high and the chances of me switching tools again is quite slim.

Did you see the choices available on the second display?

One of them is simply a grid of photos which (with thumbnails sized as needed) could easily live on your laptop monitor leaving your main screen fully sized for editing...

[potato1]

looks very promising

[dave_bass5]

I notice the Beta program runs until Aug.
Guess there will be a lot of changes by then.

[Victoria Bampton]

It's basically feature complete at this stage, but there will be a lot more tweaking to do yet.

[PixelMagic]

Hmmm...the final release of Lightroom 1.0 had a few surprises that weren't in the beta.

[Victoria Bampton]

I did say BASICALLY feature complete. That's the official line at the moment anyway. And if that's all we're expecting, then anything else will be a bonus!

[TeeJay]

Victoria - does this version install "alongside" any existing version? - and do you know if this is any cost implication when it goes live?

Thanks for all your work, it really is appreciated.

TJ

[TeeJay]

Victoria - the link to the "lightroomforums" is giving a "cannot display" message.

TJ

[Victoria Bampton]

TJ, yes it'll install alongside any version.

It will be a paid upgrade, but no figure has been announced yet.

Which link isn't working? I've just checked the ones I can think of, so would you mind checking please? Might have just been down for a couple of minutes.

[TeeJay]

TJ, yes it'll install alongside any version.

It will be a paid upgrade, but no figure has been announced yet.

Which link isn't working? I've just checked the ones I can think of, so would you mind checking please? Might have just been down for a couple of minutes.

It's the link in your sig "Great new LR Forums http://www.lightroomforums.net/ (http://www.lightroomforums.net/) "
IE reports that it "...cannot display this web page". Just tried and it still doesn't work I'm affraid.

TJ

[Victoria Bampton]

Working here TJ, sorry! Maybe try again in a while? Perhaps the DNS server isn't picking it up.

You could try www.lightroomforums.com as well - both should work.

[datadump]

Reallyyy enjoying the localised editing

[Rellik]

Wow very nice features. It does seem to be a bit snappier. But that may be due to the small catalog size right now. The new features are awesome. Hopefully, this beta will be stable enough to use now, since it will be VERY hard going back to 1.3.1.

[cosworth]

The lack of guarantee that nothing could be carried over with the 2.0 release makes me want to import into 2 catalogues. I may "play" with 2.0 but truly edit with 1.3.1. We'll see.

[Victoria Bampton]

Editing with 1.3.1 and only 'playing' with 2.0 beta is the idea anyway Jason.

As a a thought though, for those who do want to use it for slightly more serious playing, there is some rough backwards compatibility, which should mean forwards compatibility too.

Edits made in 2.0 with sliders that currently exist in 1.3.1, revert backwards and forwards as you'd expect, when transferred via xmp. Same applies to keywords and suchlike. No guarantees offered as it's a beta, but in all the tests I've done, they do appear to transfer correctly.

The sticky issue will mainly come with the new functionality - local corrections will likely undergo a lot more work, so are not necessarily going to upgrade nicely, and are just ignored if you revert the file to 1.3.1. Edit with Photoshop doesn't carry the metadata back and forth quite right yet. Things like that. The catalog format also may change between beta and release, so make sure you write to xmp before you upgrade.

So whether you trust any real files to it is up to you. I will quite happily do standard processing on 2.0, on the condition that my originals are backed up. I don't expect any local corrections to carry over to the final version in exactly the same manner, so those will be exported as I go, and if they do carry over ok, then great.

It's just useful to know which areas are more risky than others.

[dave_bass5]

It's basically feature complete at this stage, but there will be a lot more tweaking to do yet.

It looks great and so far ive not had any crashes.

Are any tutorials on the localised editing going to be uploaded?
It seems logical enough but would like to know more.

[partsman]

It looks great and so far ive not had any crashes.

Are any tutorials on the localised editing going to be uploaded?
It seems logical enough but would like to know more.
This link has tutorials on local enhancements along with other videos. you can even buy scott kelbys lightroom 2.0 book. http://www.photoshopuser.com/lightroom2/

[dave_bass5]

This link has tutorials on local enhancements along with other videos. you can even buy scott kelbys lightroom 2.0 book. http://www.photoshopuser.com/lightroom2/

Cool, thanks very much.

[cosworth]

Editing with 1.3.1 and only 'playing' with 2.0 beta is the idea anyway Jason.

Yes, but I was hoping to encourage people to not fully switch. You KNOW there will be people that do.

[pads69]

I see a lot of threads about this software is it a stand alone or do you need photoshop?
do you use it in place of photoshope?

[Victoria Bampton]

Are any tutorials on the localised editing going to be uploaded?


Loads will appear over the next few weeks I'm sure.

Ian Lyons has just posted a bit more information http://www.computer-darkroom.com/lightroom_2_beta/lr-2_2.htm

[Strick]

I was playing around an just imported some pictures that are in my 1.3 and I beleive they had the edits applied. I just imported them from and kept them int "the same location" and they are now in both LR's. I assume that is the right way to do it.

[Kadath]

Great list Victoria! I see one of my most hoped for features (Output to video) hasnt happened yet but this got most of my other big ones! Can't wait to get home and try the new stuff.

[Epix]

Will this require a fee to upgrade to from Lightroom 1.3.1 once the beta is over?

[davidfig]

Well if these local corrections are good enough for what I want. I will be purchasing 2.0.

Now to print wedding albums from lightroom. ;) I know that's asking to much, but Aperture can do it.

[davidcrebelxt]

Will this require a fee to upgrade to from Lightroom 1.3.1 once the beta is over?

Very likely. If they weren't intending on charging, I think they'd go with a 1.x version release. I just hope they refine keyword searching a little more (AND searching is a bit better, as you can create multiple "keyword" columns, and select between them... but that's STILL clunkier than ability to have a single list with check marks next to them, rather than scrolling up and down through the lists to enable/disable keywords... for my use at least.)

Question is how MUCH will they charge? Apple lowered the price of Aperture, and its upgrade price is $99... will LR follow suit? Only time will tell. Sub $100 for an upgrade would be reasonable for me... although still think its awfully early for 2.0; esp. with all the initial problems, ongoing bugs, and lack of the full sdk.

[tomd]

I'm downloading the 64 bit version now.

Did anyone actually read the license agreement?

[René Damkot]

I did. ;)

Downloading the Mac version.

[Kadath]

The Lightroom site Kelby and Kloskowski put up today shows the official release date as June on the front page.

[Kadath]

The Lightroom site Kelby and Kloskowski put up today shows the official release date as June on the front page and in the Faq
"When is the real version of Lightroom 2.0 shipping?
Sometime in June 2008.".


http://www.photoshopuser.com/lightroom2/faqs.html

[Bumgardnern]

Wow that sounds amazing. I can't decide if I want to go ahead and download the beta or wait awhile. Has anyone had problems with the beta yet?

[FlyingPhotog]

Wow that sounds amazing. I can't decide if I want to go ahead and download the beta or wait awhile. Has anyone had problems with the beta yet?

Played with it for about an hour last night and didn't crash it or lock it up...

[Bollan]

The BETA seem to be really stable so far.

I'm really impressed with all the new features. There are so many major brilliant improvement's it's almost hard to believe.

I guess the major update of Aperture will serve us LR users good in the feature :-). Now it's probably matter of time before they open the door for third party plug ins.

[xmacvicar]

Under the file menu of lightroom is the Plug in Manager.... so the 3rd party stuff will be all over the place soon!

[ooo]

Downloading mine right now =D, well installing.

[Bumgardnern]

It wont let me register to download it. It keeps saying an error occured.

[Epix]

Just got done playing with it. The new localized changes feature has tons of potential. The only thing missing now is a proper watermarking feature.

[Epix]

It wont let me register to download it. It keeps saying an error occured.I was having the same problem. Try creating a new account through this (https://www.adobe.com/cfusion/membership/index.cfm?nl=1&nf=1&loc=en%5Fus) link.

[Tsmith]

I just uninstalled the app as twice now its crashed WinXP (forcing a reboot) while working with the Tone Sliders. This is on a perfectly stable E6700 rig with 4 gigs of RAM that runs LR 1.3 and CS3 flawlessly.

[Yohan Pamudji]

Dual monitor is a welcome new feature, but permanent docking of panels at fixed positions on the primary monitor makes it not that great. Better than nothing, but that's not saying much.

[FlyingPhotog]

Dual monitor is a welcome new feature, but permanent docking of panels at fixed positions on the primary monitor makes it not that great. Better than nothing, but that's not saying much.

So you can't actually drag the "second display" to another monitor?

[Curtis N]

Can someone explain why there is both a 32-bit and a 64-bit version and what are the differences? Pros and cons?

[daveftm]

So you can't actually drag the "second display" to another monitor?

Nope, not at the moment. It looks like a case that you just "turn it on" for your secondary display -

http://farm3.static.flickr.com/2244/2385076326_7ddc29ebed_o.jpg

mind you, its rather nice once its working -

http://farm3.static.flickr.com/2055/2385066924_29c58a2ecc_b.jpg

[Grizz]

I'm pretty impressed with the new features (the ones I've played with anyway). I really like the dual monitors! So far so good. :)

[ooo]

But when you have two different dual monitors... =(

Anyways, I was playing around with it a bit and I couldn't figure out that brush feature. Regardless, the changes are still nice.

[Victoria Bampton]

So you can't actually drag the "second display" to another monitor?

Take it out of full screen mode (Window > Secondary Display > Fullscreen) and it becomes a window, which you can use on a single display, or put on whichever monitor you like.

[Bobster]

Can someone explain why there is both a 32-bit and a 64-bit version and what are the differences? Pros and cons?
because those who run 64bit OS usually have over 4GB of RAM and work with larger files etc.. LR2 flies on my rig! (instant previews/updates) i just find the interface too clunky and prefer C1

http://www.pbase.com/bob_hall/image/95055501/original.jpg

[Dermit]

Is the Mac version 64-bit? i noticed the choice between 32 and 64 is only listed for Windoze, and then for Mac there is only one choice and it does not list if it is 32 or 64. I would assume it is 64, but does anyone know for sure?

[Dan-o]

Windoze

You misspelled Windows. :rolleyes:

[Bumgardnern]

Wow I just downloaded 2.0 and love it. I really can not wait till the final release. I hope that Adobe has some more tricks up its sleeve for the final version.

[Dermit]

You misspelled Windows. :rolleyes:

Nope. That's the way I spell it. Because I feel that when it comes to operating systems Microsoft is dozing/sleeping through all the complaints/bugs/etc.

[narlus]

i don't have lightroom, only CS 3. can i download and play w/ the beta version if i don't have a full copy of LR1?

my new PC (should be here next week) is 64 bit Vista, so i am seriously thinking about getting this version.

[René Damkot]

yes, but only for 30 days instead of a few months...

[Dermit]

yes, but only for 30 days instead of a few months...

....unless you get someone who owns LR pre-2.0 to invite you to download and use 2.0 beta, then you can use it until Aug. I just did this last night for a friend of mine. As a LR owner I simply went to the LR2.0 page and they have a link named 'invite a friend'. Once you go there (LR owners) you are prompted to enter your serial number and once it is verified you can invite up to 5 friends by entering their email addresses. This send them an email with the instruction on how to get the extened use version of 2.0 beta.

[René Damkot]

Tried that, but the link didn't work for me (neither FF2 or Safari on my Mac)...

[Yohan Pamudji]

Take it out of full screen mode (Window > Secondary Display > Fullscreen) and it becomes a window, which you can use on a single display, or put on whichever monitor you like.

Correct. The problem I'm having (short version) is that I can't configure the primary and secondary output to permanently have the panels and a grid view on one monitor. Whichever monitor shows the panels will also show the loupe/zoom view when you switch from Library to Develop mode. Blech. I want to have my 2nd monitor be the place for the panels and grid view permanently, but there's no way to do this.

[Victoria Bampton]

Is the Mac version 64-bit? i noticed the choice between 32 and 64 is only listed for Windoze, and then for Mac there is only one choice and it does not list if it is 32 or 64. I would assume it is 64, but does anyone know for sure?

It's dual 32/64 bit Dermit. You select the app, right click, Get Info and there's a checkbox (as long as your Mac is 64-bit compatible - early Intel's weren't). It defaults to 32 bit but it's an easy switch.

[Dermit]

It's dual 32/64 bit Dermit. You select the app, right click, Get Info and there's a checkbox (as long as your Mac is 64-bit compatible - early Intel's weren't). It defaults to 32 bit but it's an easy switch.

I am hoping this is a one time setup? i'd hate to have to right click (Ctrl-Click) and select 64-bit everytime i want to launch the app.

Anyone here running it in 64-bit on a Mac Pro 2008 dual quad machine? Does it scream?

[Victoria Bampton]

Yep, it's one time.

And yes, that's my spec, and yes it's fantastic!

[Yohan Pamudji]

Ooh, dual quad. *drool*

One day... one day.

[adblink]

dual monitor whaaaat! so awesome

[Epix]

Related to Lightroom's new ability to merge directly into Photoshop's HDR, what do you guys prefer for your HDR processing, CS3 or Photomatix?

[Curtis N]

I'll probably get addicted to this and be forced to upgrade when it's released. Dual monitor support is a giant leap forward, and the output sharpening will cut a step out of my workflow. These two functions really should have been there from day 1.

[weegee]

Figures. I literally just ordered the "old" version 2 days ago.

What's next, 5d kit price cut in half because I ordered it a few weeks ago? : )

[tkcom]

Can I ask for an invite here?

[canon shooter]

Editing with 1.3.1 and only 'playing' with 2.0 beta is the idea anyway Jason.

As a a thought though, for those who do want to use it for slightly more serious playing, there is some rough backwards compatibility, which should mean forwards compatibility too.

Edits made in 2.0 with sliders that currently exist in 1.3.1, revert backwards and forwards as you'd expect, when transferred via xmp. Same applies to keywords and suchlike. No guarantees offered as it's a beta, but in all the tests I've done, they do appear to transfer correctly.

The sticky issue will mainly come with the new functionality - local corrections will likely undergo a lot more work, so are not necessarily going to upgrade nicely, and are just ignored if you revert the file to 1.3.1. Edit with Photoshop doesn't carry the metadata back and forth quite right yet. Things like that. The catalog format also may change between beta and release, so make sure you write to xmp before you upgrade.

So whether you trust any real files to it is up to you. I will quite happily do standard processing on 2.0, on the condition that my originals are backed up. I don't expect any local corrections to carry over to the final version in exactly the same manner, so those will be exported as I go, and if they do carry over ok, then great.

It's just useful to know which areas are more risky than others.Let me know if I am missing something or not. But I now do basic editing in LR 1.3.1 and then export to hard drive and do final editing in CS3. Assume if I do this in the new 2.0 beta and export to hard drive and finish up in CS3 it will not affect by original RAW file and I could just always go back to that to do any re-editing.

[Yohan Pamudji]

I'll probably get addicted to this and be forced to upgrade when it's released. Dual monitor support is a giant leap forward, and the output sharpening will cut a step out of my workflow. These two functions really should have been there from day 1.

I agree--both features were sorely missing from version 1. But "giant leap forward" would be stronger praise than I'd give to the dual monitor support. It's not nearly flexible enough to be a giant leap for me. Still, considering anything is infinitely more than nothing, I guess in that sense you're right :lol:

Is there soft proofing available in the print module, or is that still AWOL?

[deletedpenguin]

Few questions from a novice here:

1. I have a 64 bit processor, but I'm running a 32 bit version of Vista (installed the hardware after the Vista install). So, since I can't upgrade to a 64 bit version of Vista without doing a complete overhaul, do I have to run the 32 bit version of LR, or can you run 64 bit programs in a 32 bit version of Windows?

2. Can someone explain the purpose of "Auto Mask"? Does it literally try to figure out different parts of the photograph, and try to mask automatically? (ie. sky and ground)

[yunaiseng]

2. Can someone explain the purpose of "Auto Mask"? Does it literally try to figure out different parts of the photograph, and try to mask automatically? (ie. sky and ground)

Check out Scott Kelby's "Localized adjustments" video. It shows the auto mask in action at about 1:30

http://www.photoshopuser.com/lightroom2/

[Victoria Bampton]

Let me know if I am missing something or not. But I now do basic editing in LR 1.3.1 and then export to hard drive and do final editing in CS3. Assume if I do this in the new 2.0 beta and export to hard drive and finish up in CS3 it will not affect by original RAW file and I could just always go back to that to do any re-editing.

In that way, 2.0 works exactly the same as 1.3.1. Warning though - work on duplicates or backed up files, as it's still a beta and there could be a bug that messes up your raw files. It's unlikely, but it is possible.

[lowcrust]

Few questions from a novice here:

1. I have a 64 bit processor, but I'm running a 32 bit version of Vista (installed the hardware after the Vista install). So, since I can't upgrade to a 64 bit version of Vista without doing a complete overhaul, do I have to run the 32 bit version of LR, or can you run 64 bit programs in a 32 bit version of Windows?


You should install the 32 bit version. I'm guessing you can freely download the other version should you upgrade Vista to 64bit version.

[Epix]

Few questions from a novice here:
2. Can someone explain the purpose of "Auto Mask"? Does it literally try to figure out different parts of the photograph, and try to mask automatically? (ie. sky and ground)It attempts to constrain localized changes to pixels of the same shade of color.

[deletedpenguin]

You should install the 32 bit version. I'm guessing you can freely download the other version should you upgrade Vista to 64bit version.

Ya, I'd assume I would be able to, but wasn't sure if you can still run 64 bit programs in a 32 bit operating system, since I've got a 64 bit processor.

[echo]

because those who run 64bit OS usually have over 4GB of RAM and work with larger files etc.. LR2 flies on my rig! (instant previews/updates) i just find the interface too clunky and prefer C1

Off topic... Is that Mike Oldfield?

On topic... I am loving the Beta. Wow!

:)

Mike

[Yohan Pamudji]

For those still running a 32-bit OS (like me), it's time to start seriously considering the move to 64-bit, because not only is Lightroom 2 going to be available in 64-bit, but if I'm reading this John Nack blog post (http://blogs.adobe.com/jnack/2008/04/photoshop_lr_64.html) correctly then Photoshop CS4 will be 64-bit ONLY on Windows with no 32-bit version being offered (still 32-bit only on Mac, which is sparking a huge catfight in the comments section of this blog post and I assume elsewhere in the Mac universe). Did I read that right? If you're running Windows you'll have to be running a 64-bit version (XP64 or Vista64) to run Photoshop CS4. Or am I misunderstanding what John Nack is saying?

But back to LR2, is anybody running the 64-bit version on Windows XP 64-bit? Everywhere Adobe mentions 64-bit the only reference is to Vista 64-bit. Is there a reason why LR2-64 wouldn't work on XP 64-bit when the 32-bit version works on both XP 32-bit and Vista 32-bit?

[Epix]

The 64bit CS4 version will only be available initially on Windows. The 32bit version will be available on Windows and Mac.

[canon shooter]

The 64bit CS4 version will only be available initially on Windows. The 32bit version will be available on Windows and Mac.We are getting off the subject of this thread, but since it came up, I hope CS4 is not coming any time soon. Seems like I just laid out the money for CS3.

[Jannie]

I downloaded it yesterday into my Mac; then I went out and shot a bunch of photos under really flat overcast sky and had my 5D. The images immediately have a better look of overall sharpness and all I've messed with so far is the custom settings and auto in the Library section and I'm impressed; they gave me a real quick idea regarding what I can expect when I really go to work on them, but a lot of them looked great right there without doing anything more.

Okay I just worked with it some more and the Brush Stroke thing is ticking me off, I can't seem to get it to do anything but lock little heavy white circles over the area I click on no matter what size I set it at. I've had enough for tonight, need instruction before I mess with the brush anymore, I haven't been this irritated in a while. It makes me want chocolate!

Everything else I've tried is much better but what really stands out is the sharpness, I also like the Hue, Saturation and Luminance slides, I don't know why they seem really different, I can see in more detail what I'm doing. I kind of am amazed by what I could do with cutting through some glare around some geese in shallow water, never been able to do that before.

But what's the deal with the picture window above the noise reduction, for what? it's too small on my 17" monitor to be useful and even though the image seems identical in closeness as what I've clicked into on the main image, it's harder to tell what I'm looking at in the smaller image (re-noise) will probably close that window from now on, it seems useless unless there's something I'm not noticing.

[deletedpenguin]

I believe that the small window is there for a quick 1:1 preview, so you're not jumping back and forth all the time.

[Victoria Bampton]

But what's the deal with the picture window above the noise reduction, for what? it's too small on my 17" monitor to be useful and even though the image seems identical in closeness as what I've clicked into on the main image, it's harder to tell what I'm looking at in the smaller image (re-noise) will probably close that window from now on, it seems useless unless there's something I'm not noticing.

It's useful as a quick double check if you HAVEN'T zoomed in. You're quite right, it's a 1:1 view as per your main image zoomed in. If you don't like it, click the little arrow above/right to hide it. Or you can click the little TAT tool next to it and click on the image to define which area of the image it's showing (an eye is good!)

[Jannie]

Thanks, I hid it.

[mantra]

to me works great above all, mostly the library module

the only leak are the sliders in the develop module that more slow to reply if i compare to 1.3.1 (that is amazing fast) , i'm a pc user and run on xp sp2 last patches


by the way great improvements

[René Damkot]

Q on the secondary display:

I have a Radeon8500 as main video card, and a second video card for my secondary monitor.
LR thinks the (empty) second output of the Radeon has my secondary display.

Any way to get the "third" display output to be seen by LR, or to drag the window to my secondary monitor?

PowerMac G4, OSX 10.4.11 by the way.

[Victoria Bampton]

You should be able to take it out of full screen mode (cmd-shift-F11 or window menu > secondary display > full screen) and drag it where you like Rene.

[Bobster]

Off topic... Is that Mike Oldfield?

nope, Perfect Alibi is a Floyd tribute band.. ;)

[René Damkot]

You should be able to take it out of full screen mode (cmd-shift-F11 or window menu > secondary display > full screen) and drag it where you like Rene.

That did the trick...
Now if only something useful could be put on the second monitor, like all the palettes...

On a side note:
- Why does the clarity slider run from -100 to +100 now?
- Why are the icons (and settings) for crop, dust removal and such moved out of the tool bar to the right side panel (and is there any way to get them out of there)?

[Victoria Bampton]

LOL Rene. The new dual monitors ARE useful, they're just not quite what you were looking for! ;)

Clarity - find a nice closeup headshot and drop it to -100 - beautiful effect! Then try using it in the Local Corrections - it's a lovely softening ideal for skin.

The icons/settings - the new top right panel was added for the local corrections, so the options for the other tools moved up there too (more space to add more options in future), and then it looks odd with tools icons in the toolbar and the options elsewhere, so it all moved up there. It takes a bit of getting used to, but it's growing on me - they may move again by the final release, depending on public opinion.

[cosworth]

I hope to see these in CS4's ACR or a new ACR release...

[lowcrust]

I'm with René, the dual monitors are one of the most sought after features in 2.0 for me. Sadly what they implemented is nowhere near what I had hoped for. Maybe I'll accept it for what it is and come to enjoy it later but at this point I'm really disappointed with the lack of customizations.

I like the move of the toolbar icons, although I usually use shortcuts for those functions so it doesn't matter much.

The dodge and burn stuff is amazing, only played with it for a couple of minutes and instantly love it. Hopefully it will become really intuitive (unlike, for instance, the first spot removal tool that I never got comfortable with).

I still think left panel should be "Library" and right panel "Develop". This Beta seem like a baby step towards such a solution. I just don't see the point in switching back and forth between them, or the use of having half of the tools available in library and then always having to switch to develop just to add some vignetting (or something). Keywording would then be moved entirely to the top.

Lastly; My opinions rule and are super interesting for all!


=)

[Victoria Bampton]

Local Corrections have taken the majority of the team's time this time round. I'd really like to see an option to split modules off onto the different screens (complete Library on one, Develop on the other) but that's apparently WAY more complicated than it sounds!!!

[echo]

nope, Perfect Alibi is a Floyd tribute band.. ;)

Amazing likeness, and I did a set of portraits of Mike last year. :)

[canon shooter]

I hope to see these in CS4's ACR or a new ACR release...In this thread I keep seeing reference to CS4.

Is there a date for CS4. Should be about a year away, shouldn't it??

[Victoria Bampton]

On an 18 month schedule, I'd be expecting about August.... but who knows!

[Curtis N]

Now if only something useful could be put on the second monitor, like all the palettes...I think y'all just need to think outside the box a little here.

Move the main LR window to your second monitor, and the secondary display to your first monitor and set it to loupe view.

Or vice-versa.

Either way, you have your real estate on one monitor fully utilized for viewing the image, while all your adjustment panels are on the other.

I don't see how this is worse than detachable panels/palettes.

[Epix]

How to video for LR2:

http://media.libsyn.com/media/cspodcast/podcast-LR-LR2Overview.mp4

[canon shooter]

WOW, tried the localized adjustments and that is great. Works well on some shots I took at zoo where there are shadows around the eyes of animals. A few quick stokes and the shadows are gone.

Much easier than using a layer mask in CS3 and faster too. But in CS3 if I made a mistake and say got too light I could just drag that item in the history area to the trash can. Is there a way to do that in LR?

[canon shooter]

Also when using the localized adjustments (or for that matter any editing in LR) is there a way to copy a image in LR and edit. So if later I decide I don't like the effect I still have an untouched image in LR?

[Grizz]

You can make a Virtual copy in Lr and then you will have both the original and the virtual with your tweaks. But reallly LR does nothing to the original so its still there in its original form. You can use the before/After views in the develop module to see your changes.

Or go into the History panel and see your tweaks step by step.

[canon shooter]

You can make a Virtual copy in Lr and then you will have both the original and the virtual with your tweaks. But reallly LR does nothing to the original so its still there in its original form. You can use the before/After views in the develop module to see your changes.

Or go into the History panel and see your tweaks step by step.I understand that LR does not effect or make any changes to the original RAW file, but the changes I make in LR and then later come back to LR those changes will still be in LR. Guess at that point if I wanted to start all over I could still press reset (even after the program had been closed and reopened)?

[Grizz]

Yes you could press reset or just go to the History panel (Develop) and click on the bottom selection (import with date and time) to get back to your original image.

Thats why I like virtual copies. You make your changes on the VC and stack it with the orig. Then later you can change/delete the VC or create another and make different changes. One image, many variations all in one stack.

[S.E.V.]

I have v1.4 already up and running will this install over version 1.4 or as a separate version. should i uninstall v1.4 then install the beta or can i have both, just direct the 2.0 beta to a different path? I want to give it a whirl, just want to know the best way.

Thanks

[deletedpenguin]

^ I'm curious as well. To import my 1.4 library, it says I have to upgrade it. But if I do...


...will my computer explode? :p

[Victoria Bampton]

2.0 beta shouldn't blow up your machine, but it won't upgrade a 1.x catalog either. It's just available for 'playing' and 'testing', not serious work. There is always the potential with a beta to damage your files. It shouldn't do, but you are better using duplicate files with it.

[deletedpenguin]

Ya, just worried that I would import my catalog into 2.0, and then it wouldn't be compatible with 1.X anymore.

[René Damkot]

I think y'all just need to think outside the box a little here.

Move the main LR window to your second monitor, and the secondary display to your first monitor and set it to loupe view.

Or vice-versa.

Either way, you have your real estate on one monitor fully utilized for viewing the image, while all your adjustment panels are on the other.

I don't see how this is worse than detachable panels/palettes.

Well, for starters; my main display is a 22" LaCie CRT, my secondary is a 17", ancient, ColorSync.

Your solution would work if I'd have 2 big, high quality, monitors. I don't.
I use the second screen for PS palettes and such, and would love to be able to do the same in LR...

Moving the loupe view to monitor 1, and the main window to the smaller monitor, would still leave me scrolling up and down through the adjustments. (like it does now, thanks to the addition of the "crop tool" to the right panel)

I'd like to be able to move the palettes to where I want them. Scalable would be nice.
Big histogram off to the side (since I don't need to click it) of the screen, most used palettes close to the main window on the second screen, less used panels off to the side; I work in PS and DPP the same way: like this (http://photography-on-the.net/forum/showpost.php?p=2544062&postcount=10)

I'd prefer not to have more space on the desk taken upp by a second 22" screen, not to mention having to pay for one ;)

[Yohan Pamudji]

I'm with René, the dual monitors are one of the most sought after features in 2.0 for me. Sadly what they implemented is nowhere near what I had hoped for. Maybe I'll accept it for what it is and come to enjoy it later but at this point I'm really disappointed with the lack of customizations.

...

I still think left panel should be "Library" and right panel "Develop". This Beta seem like a baby step towards such a solution. I just don't see the point in switching back and forth between them, or the use of having half of the tools available in library and then always having to switch to develop just to add some vignetting (or something). Keywording would then be moved entirely to the top.

Probably won't happen, since the LR development team seem set on the idea that Library functionality should be separate from Develop functionality. Displaying both sets of panels at the same time doesn't fit into that philosophy.

I think y'all just need to think outside the box a little here.

Move the main LR window to your second monitor, and the secondary display to your first monitor and set it to loupe view.

Or vice-versa.

Either way, you have your real estate on one monitor fully utilized for viewing the image, while all your adjustment panels are on the other.

I don't see how this is worse than detachable panels/palettes.

Need to think out of the box--we certainly do, especially with the extremely small box that they've given us :) I'm starting to have a sneaking suspicion that the main reason that Library and Develop are 2 separate modules are so that we wouldn't have an overload of palettes if the 2 were combined into one module. Either that, or they designed LR for super-organized people who always keyword tag, color tag, and rate everything first, then develop said photos; as opposed to those of us (dare I say most of us?) who switch back and forth a lot between Library and Develop. I fear the "G" (grid/library module) and "D" (develop module) keys on my keyboard will get worn out before the rest because of this :lol:

My point is, in designing LR they seem to be married to a very rigid workflow (very small conceptual "box"), whereas a more fluid approach where Library and Develop functions aren't so tightly compartmentalized and separated would've suited a much larger audience. The highly organized people could continue using LR the way it's currently designed, while the scatter-brains like me could tag then develop then color code then tag then develop, etc., etc. Photoshop let's me pretty much work the way I want to, while LR forces me to work they way they want me to. That's the key difference for me.

On a positive note since they really have improved the layout (just not as much as some of us would've hoped), I like that they moved the filters from the filmstrip to the top of the grid view. I use filters all the time in LR 1.3--filter by color code or flag status being the most common--which meant that I had to at least occasionally open the redundant filmstrip at the bottom to access the filters. Now I can just keep that filmstrip closed forever and have the grid view and filters display on the 2nd monitor--nice. And as rudimentary as the 2nd display implementation is, it sure is nice to not have to switch between loupe and grid views, since I can just permanently have the grid up on the 2nd monitor.

[mjm80]

WOW, tried the localized adjustments and that is great. Works well on some shots I took at zoo where there are shadows around the eyes of animals. A few quick stokes and the shadows are gone.

Much easier than using a layer mask in CS3 and faster too. But in CS3 if I made a mistake and say got too light I could just drag that item in the history area to the trash can. Is there a way to do that in LR?

I found the local adjustment can be changed afterwards. If you click on the adjusted area a small circle appears, click on thus and it opens the adjustment sliders which you can change as you like.

[opus13]

What's the speed like so far for everyone? i find 1.4 to be dog-slow at anything (heaven forbid you update the library), and generally unusable.

v2 so far seems like its going to be good stuff!

[Victoria Bampton]

What's the speed like so far for everyone? i find 1.4 to be dog-slow at anything (heaven forbid you update the library), and generally unusable.

v2 so far seems like its going to be good stuff!

It's getting faster with every release... and 2.0 hasn't been optimised yet.

You shouldn't be finding 1.3.1 / 1.4 *that* slow though - how many pictures in your catalog? Have you optimised the catalog recently? Machine specs?

[deletedpenguin]

2.0 is definitely faster, but 1.4 isn't terribly slow either, at least for me. I've got a couple thousand photos in my catalog.

[lowcrust]

2.0 is definitely NOT faster on my machine (Quad core at 3Ghz with 4GB ram on XP).

I guess some people will find it faster because they start out with a smaller catalog on the Beta.

[darktiger]

2.0 is definitely faster than 1.3.1 on my machine. I have it installed on a Raptor 150Gb, Quad overclocked to 3.6ghz with 8gb of memory.

[Epix]

Can someone explain the new "Flow" and "Feather" sliders under local corrections?

[opus13]

It's getting faster with every release... and 2.0 hasn't been optimised yet.

You shouldn't be finding 1.3.1 / 1.4 *that* slow though - how many pictures in your catalog? Have you optimised the catalog recently? Machine specs?

Home built Workstation:

Dual Opteron 285
4 gb ram
1x 15,000rpm U320 boot disc
4x 300gb 7200rpm sata raid 10
4x 400gb 7200rpm sata raid 10
1x geforce 8800gt
1x geforce 5200

I alternate between 3x and 4x 24" displays depending on project needs.

The disc spaces fluctuate depending on the project i am working on. I also have 2 fibre attached storage arrays (8 drives in each) in the server room that only get booted up for backup or overflow.

I am pretty sure that it isn't the machine specs dragging me down ;) i get about 220MBps read and 170MBps write speeds on the disc arrays, and memory (RAM) performance is quite high with all 8 slots occupied. NUMA is enabled . I always operate with the extended virtual address space flag enabled.

The catalog is at about ~35,000 images right now (not at the office at the moment). It is down from ~55,000 after trimming some chaff. I have never optimized the library beyond rescanning and removing adding images automagically --I have never actually seen the library complete it's scanning. I cant run it during the day, as it just takes too long. i have noticed that lightroom has never automatically removed folders that have been deleted. That is always done manually (yuck).

[deletedpenguin]

Can someone explain the new "Flow" and "Feather" sliders under local corrections?

Correct me if I'm wrong, but I believe these are essentially the same options as in Photoshop, under the brush setting. Flow allows you to adjust the amount of brush pressure, or amount of change that is taking place, while feather is changing the edge of the brush area from a hard edge to gradients.

[trudgy]

I've been using the 64 bit LR 2.0 for a couple days now on my XP 64bit machine

quad core 3.6ghz 8gig RAM and it's running really nice, it's utilizing up to 4.8gb of my RAM(it seems to stay at that number as I have never seen it go over that but gotten very close)

so far so good!!

[canon shooter]

Yes you could press reset or just go to the History panel (Develop) and click on the bottom selection (import with date and time) to get back to your original image.

Thats why I like virtual copies. You make your changes on the VC and stack it with the orig. Then later you can change/delete the VC or create another and make different changes. One image, many variations all in one stack.Has anyone found a way to go to the history and just delete the last item done. Like in CS3 where you can just drag the last item (in history panel) to the trash. This would be great, so when editing you go too far with one feature you don't have to start all over.

So far I have not found a way to do this.

[Victoria Bampton]

Just click on the previous step. It'll overwrite that next step when you next do something.

[Yohan Pamudji]

Ctrl-Z on Windows (the universal "undo" shortcut key combo for Windows). No need to even go into the history panel.

[canon shooter]

Ctrl-Z on Windows (the universal "undo" shortcut key combo for Windows). No need to even go into the history panel.WOW, I will have to try that. Does it only undo the last item.

[Yohan Pamudji]

Yes, just the last action you took, and you can do Ctrl-Z repeatedly to keep going down the list and undoing each step. Unfortunately Lightroom records changing modules as an action as well, so if say while developing you changed to Library mode then back to Develop, one of the "undo" steps will be going back to library mode if you go far enough down the queue. In other words, it doesn't just undo develop actions but also changing modules (and maybe other actions too like rating and flaggin--haven't tested). Irritating. Another reason why the segregated Library and Develop modes are a pain to work with.

[Epix]

Just click on the previous step. It'll overwrite that next step when you next do something.
Is there a way to remove something from the middle of the history list and effectively remove just that step's contribution to the current file?

[Victoria Bampton]

Is there a way to remove something from the middle of the history list and effectively remove just that step's contribution to the current file?

No, because the adjustments are stored relative to each other. You can see what the adjustment was (i.e. exposure +1.0) and do the opposite though, which will do the same job.

[Tapeman]

Victoria, at 468 posts you must be the champion of most helpfull posts per poster ratio.

[FlyingPhotog]

Correct me if I'm wrong, but I believe these are essentially the same options as in Photoshop, under the brush setting. Flow allows you to adjust the amount of brush pressure, or amount of change that is taking place, while feather is changing the edge of the brush area from a hard edge to gradients.

Flow = Brush Transparency
Feather = Edge Hardness/Softness

[deletedpenguin]

Hehe, ya. That's what I was trying to say. I think. :)

[V8Rumble]

Painting a layer mask to drop the exposure of a bright window in a test shot I did at 1:1 made LR 2.0 run like a dog. After every click it took a couple seconds to update the preview.

They better add a selectable marquee, or not update the preview until done. Automask sucks too on edges with not enough contrast

[Victoria Bampton]

Thank you Tapeman!

[hickory]

I'm running this on my intel macbook pro and what i disliked about it is that when you create a slideshow and assign a soundtrack to be played it will not start the music unless i've first started itunes and cued up the music i want to be played then pause it and go back to LR. Am i missing something here, this is the same on 1.3.1 as well.

Also being able to export the slideshow with the music would be really great but I suppose there are copyright issues involved by doing so.

tom

[BoySpot]

Has anyone tried adding large amounts of iamges to the database on the beta yet? I am interested to know whether V2.0 can handle more files without getting sluggish. If so, I will be able to recombine some of my existing catalogs.

[Richard_Miami]

Has anyone tried adding large amounts of iamges to the database on the beta yet? I am interested to know whether V2.0 can handle more files without getting sluggish. If so, I will be able to recombine some of my existing catalogs.

BoySpot:
If you don't get a quick answer to this, wait a few hours. I will be importing about 7,000 images (over half are RAW from my 5D) to the beta tonight (EST). I will post the timing info here if it helps!

[gkas]

It's probably a bad idea to import large volumes of images into the BETA database. I think that the code had not yet been optimized. Thus, any test on volume would be worthless.

[Richard_Miami]

It's probably a bad idea to import large volumes of images into the BETA database. I think that the code had not yet been optimized. Thus, any test on volume would be worthless.

I will give it a try anyway. The way I understand it, LR doesn't actually move the images, just builds the catalog to their current locations.

[Victoria Bampton]

It's not optimized yet, that's true. That said, I've got it running pretty well on some big catalogs. There are a few possible memory/caching issues, but that just comes of it being a beta.

[BoySpot]

I previously started breaking catalogs when they were over 10k images or so and that seemed to keep version 1 running okay. If I could have something over 50k images in a catalog, that would be more handy. I am not so bothered about whether the beta does well but whether version 2 will be set up to run smoothly on very large catalogs without bogging down.

Rob

[Tsmith]

There are a few possible memory/caching issues, but that just comes of it being a beta.

I suppose thats why it crashes using some of the adjust sliders I suppose. ... :confused:

[Victoria Bampton]

I suppose thats why it crashes using some of the adjust sliders I suppose. ... :confused:

Er.... yes. Betas crash. And this is an early beta build so they crash even more.

Which sliders are you having trouble with? Mac or PC?

[Tsmith]

Er.... yes. Betas crash. And this is an early beta build so they crash even more.

Which sliders are you having trouble with? Mac or PC?

PC - Intel E6700 4 gigs RAM and WinXP 32 bit. It was with the Tone Curve adjustments.

Thanks Victoria

[nutsnbolts]

ok who is using this fully as opposed to 1.4.1.

[Victoria Bampton]

Thanks TSmith. I'll keep an eye open for anyone else seeing the same problem - I haven't come across it but I'm Mac based these days, and so the bugs are different.