Skip navigation
Currently Being Moderated

I'm not feeling it

Jan 10, 2012 12:00 AM

It's been a while since anything in Adobe's Creative suite got me excited. I upgrade to get compatibility with new hardware or an OS... reluctantly. Lightroom, of course, exists outside the CS framework, and it's been the singular bright light that hasn't failed to please me with each release. As a working sports photographer it IS my workflow.

 

I watched all the L4 preview stuff from Scott and Michael, and I'm sorry to say I'm a little non plused.

 

The new Book module really looks well implemented, I create a number of books each year for clients. I would have liked to see two or three vendors represented, but Blurb obviously has done a fair bit of work on their end to make this happen, so full credit to them. Head to head I'd still give MyPublisher the edge in terms of final printed quality (and they have a bigger landscape size). MP however, seems intent on catering to the hobbyist market... admittedly where most of the money is.

 

I'm sure Maps will make landscape photographers chasing sun and moon down lonely roads happy when it comes time to find that special spot again. Perhaps I'll preview some stages of this year's TDF and use it to mark key vantage points. Might turn out to be the sleeper feature that surprises me.

 

For such a simple feature, Email Photo will probably save me a fair bit of time when clients request the straggler single image after a major FTP transfer, or someone needs something quickly for a blog post.

 

Other than that, I was looking for some real UI optimization this time around. There's a gold mine of productivity to be extracted from better support for multiple monitors, and modular customization. Personally I'm frustrated by the separation of the Library and Develop. Quick Develop controls are practically useless, and you can't edit metadata in Develop where I've got to go before I can fully evaluate an image.

 

I know we all recognize that Lightroom has an awkward family dynamic with Photoshop (the naming is ridiculous), but I don't like the fact we can't get a proper clone tool or healing brush (I didn't miss it did I?) because PS can't stand to let the kid out from under it's shadow. Cloning is really the last function that necessitates a trip to PS with any regularity.

 

Perhaps I'm just burned out from all the endorphins released by the 1DX (on order) and the D4 (the grass on the other side of the street).

 

The net for me is I don't see this version saving me any time, that's what I was hoping for. I will upgrade of course, it's just a shame I didn't get anything at the top of MY list. I hope you faired better.

 
Replies 1 2 Previous Next
  • Victoria Bampton
    4,831 posts
    Apr 1, 2008
    Currently Being Moderated
    Jan 10, 2012 12:27 AM   in reply to VeloDramatic

    Have you tried the new Develop controls yet?  Even if you don't use Books or Maps, they're a pretty major upgrade.

     

    Hopefully next time round we'll get some more JDI's and little usability tweaks rather than so many headline features.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2012 12:44 AM   in reply to Victoria Bampton

    It's finally taken the PS5 away from my landscapes which is very welcomed.  Lightroom 4 develop module is simply stunning for general landscape.  However my commercial work is beauty and it's not even close to managing that when used to PS5 tools like liquify, clone, healing etc but the new colour channels in the tone control are great for looks that i would usually resort to NIK software to achieve eg: cross process and other fashion looks.

     

    GUI is still the worst out there of any software and surprised it didn't get a makeover like elements or bridge.  Such a waste of space.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2012 1:31 AM   in reply to Victoria Bampton

    i fully agree to veloDramatic. its not all about the "big things" that makes a software like LR great or not. its how efficently you are able to work with it. I am still using LR 2.5 because i have to use the ajustementbrush on nearly ever picture and the changes in the UI from 2.5 to 3 makes it nearly impossible for me to work fast. no changes there in LR 4 so i will stick to 2.5 till i have to switch to captureone or something else (if adobe dont make up its mind on that point - which i would prefer instead of switching because i think LR is a good tool). or another example focal point. my co-worker has to check every pic for sharpness. I think you can imagine how much time she could win if LR would display the FPs. But Adobe constantly refuses to listen. But to be fair, adobe made a great job on the engine.

     
    |
    Mark as:
  • Victoria Bampton
    4,831 posts
    Apr 1, 2008
    Currently Being Moderated
    Jan 10, 2012 1:45 AM   in reply to VeloDramatic

    LR3 presets will still work with PV2010.  With 2012, it'll be hit and miss, depending on how the preset was created.  There is no direct translation of settings between 2010 and 2012 as the look is so different.

     
    |
    Mark as:
  • Victoria Bampton
    4,831 posts
    Apr 1, 2008
    Currently Being Moderated
    Jan 10, 2012 1:47 AM   in reply to xirta

    xirta wrote:

     

    I am still using LR 2.5 because i have to use the ajustementbrush on nearly ever picture and the changes in the UI from 2.5 to 3 makes it nearly impossible for me to work fast.

     

    Which UI changes?

     

    It's not that they're not listening - there are just limited hours in the day, and different priorities.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2012 2:40 AM   in reply to Victoria Bampton

    IN LR 2.5 you can choose how the brush is working (remember the +/- "bubbles" which remembered the values of the brush or that you get a new, "nulled" brush each time you change the subject of what to brush (e.g. saturation or brightnes)), since LR 3 you can not.This means "just" one to three clicks more each brush you use. Sounds not  worth speak about, but lets do a little math: i am editing 200 weddings a year with an average of 500 pics a wedding, makes 100.000 pics a year. 2 seconds timeloss because of the changes makes up to 200.000 seconds a year, which are 3.333 minutes or 55 hours or as nasty as its sounds 2.3 days (24h each) more work each year. If you calculate that i work 10 hours a day and if i would use LR 4 (or 3) i would spend more than 5.5 workdays only to use the "new" brush UI. So you have taken a little bit of your limited time to change a thing that no one was harmed of but helped the frequent users of it very much. I very much think that my time is spent much better on a holiday trip than to click throu a software, but that may be just my opinion!

     
    |
    Mark as:
  • Victoria Bampton
    4,831 posts
    Apr 1, 2008
    Currently Being Moderated
    Jan 10, 2012 2:43 AM   in reply to VeloDramatic

    I need to do a full blog post on this, but in the meantime, here's the rundown.

     

    Images processing in LR3 will come into LR4 set to PV2010.  They will still look the same, and they can remain in that state indefinitely.  That's why we've got process versions.

     

    If you update those photos to PV2012, it will try to convert the settings, but there's such a difference in the basic look of PV2010 vs. PV2012, that they won't match. 

     

    So, you either leave them as PV2010, or you reprocess.  Most people will leave as PV2010, and when they want to update a specific photo to PV2012 because they want to do something extra, then they'll reprocess.

     

    So your PV2010 presets will still work as normal on existing photos, and on any photos that you switch to PV2010 (or are automatically switched by the preset).  They may not work so well on new photos or ones that you've updated to PV2012.

     
    |
    Mark as:
  • Victoria Bampton
    4,831 posts
    Apr 1, 2008
    Currently Being Moderated
    Jan 10, 2012 2:48 AM   in reply to xirta

    xirta wrote:

     

    IN LR 2.5 you can choose how the brush is working (remember the +/- "bubbles" which remembered the values of the brush or that you get a new, "nulled" brush each time you change the subject of what to brush (e.g. saturation or brightnes)), since LR 3 you can not.This means "just" one to three clicks more each brush you use.

     

    I remember the buttons, but I'm not sure I'm following which bit it was that you preferred, that's changed.  I have been up since just after 4am for this release, so it might be me!!  The changes Adobe make aren't up to me, but I'd love to find a workaround for you if I can.

     
    |
    Mark as:
  • TK2142
    404 posts
    Jan 20, 2010
    Currently Being Moderated
    Jan 10, 2012 3:05 AM   in reply to VeloDramatic

    I'm hoping better cloning/healing support (<- click on this link to vote for better support) support may still make it into LR 4 final.

     

    Softproofing may be a big thing for some (as was lens corrections) but I'd prefer better retouching support over softproofing and lens correction combined.

     

    Hopefully the new photo book feature is not tied to just one vendor. It wouldn't be of much use for anyone living in an area not covered by that vendor. Still downloading LR4 beta.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2012 3:20 AM   in reply to Victoria Bampton

    I know that and i appreciate your afford. My problem is, that in LR 2.5 each +/- button had its own (remembered) value and additionaly a click on an item like lets say contrast brought up a new brush pin. You click on "brightness +"  and you get a brush with lets say plus 50 brightness.you paint over lets say a face. then you click on  "contast -" and get a NEW brush (with NO brightness value any more) with minus 20 contrast and paint over a dress and so on. asuming you used the brushes bevore and gave them the values you like. In LR those two adjustments needed 4 clicks at all. one click choose the contrast, second click use the brushtool, third click choose brightness and last click use the brightness brush. Pls. try this with LR 3/4, count your clicks and keep in mind that every click takes an certain amount of time. I do not need a brush with 2 or more values applied and if i think i am faster to apply the brush twice in the old way. And if you say others do use the brush like you have to now, than i can only say: no problem, it was possible in LR 2.5. Both methods were there. One has gone - without any need from my point of view!

    that is my problem with LR 3/4. if there is a workaround i would be greatful if you can tell me.

     
    |
    Mark as:
  • Victoria Bampton
    4,831 posts
    Apr 1, 2008
    Currently Being Moderated
    Jan 10, 2012 3:23 AM   in reply to VeloDramatic

    VeloDramatic wrote:

     

    I assume in a catalog of mixed PV2010/PV2012 images a preset action of the wrong model would trigger a warning. Seems best to avoid the mixed catalog approach.

     

    This time round is going to be complicated whichever we look at it.

     

    The simplest approach is to say anything from now on is done with PV2012.  You can see whether you're on 2010/2012 by the exclamation mark in the Develop module, so old ones don't really get mixed up.

     

    As far as presets go, there's no warning about which PV the preset uses, but there's a way of combining 2010/2012 presets using a text editor - that'll be the cleanest solution I think.  That's one for a blog post though.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2012 3:25 AM   in reply to xirta

    i have forgotten so say, that my workaround would be to edit all pics in LR 2, thant export the raws and reimport in LR3, and export with the new engine. This will not work any more since LR 4 out of the same reason why presets may not work properly.

     
    |
    Mark as:
  • Victoria Bampton
    4,831 posts
    Apr 1, 2008
    Currently Being Moderated
    Jan 10, 2012 3:31 AM   in reply to xirta

    I'm with you.

    xirta wrote:

    In LR those two adjustments needed 4 clicks at all. one click choose the contrast, second click use the brushtool, third click choose brightness and last click use the brightness brush.

     

    I can get that down to 2 or 3 clicks, depending on how you're counting. 

     

    If it's a new photo, select brush (which is automatically on new) then select your preset from the pop-up, then use the brush.

     

    If it's a photo you're already working on, press new, select your preset, then use the brush.

     

    I know the pop-up's probably not as convenient as the buttons were for you, but if you get tempted by the new features, it may be close enough.

     
    |
    Mark as:
  • Victoria Bampton
    4,831 posts
    Apr 1, 2008
    Currently Being Moderated
    Jan 10, 2012 3:32 AM   in reply to xirta

    xirta wrote:

     

    i have forgotten so say, that my workaround would be to edit all pics in LR 2, thant export the raws and reimport in LR3, and export with the new engine. This will not work any more since LR 4 out of the same reason why presets may not work properly.

     

    That'd still be fine, they'd just be set to PV2010 instead of the new sliders.

     
    |
    Mark as:
  • Victoria Bampton
    4,831 posts
    Apr 1, 2008
    Currently Being Moderated
    Jan 10, 2012 3:36 AM   in reply to VeloDramatic

    VeloDramatic wrote:

     

    A text editor Victoria... no one should be that masochistic ;-)

     

    Then we have to all gang up on Matt Dawson and convince him to write a plug-in to do it.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2012 4:03 AM   in reply to Victoria Bampton

    thanks for the hint, you are totaly right with that. in case i need it i would do it with PV2010!!! But I am not convinced with the brush issue ;-)) i gave it a try but it is not the same. not even close. i see that this is hard to understand but i showed it to a few people ( 5 or 6) and when they saw the difference in the workflow ever single one said kind of: Ahh ok, now i see why this is annoing to you.  ;-)) but thank you anyway for your kind help!!!!

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2012 5:45 PM   in reply to Victoria Bampton

    Victoria Bampton wrote:

     

    I need to do a full blog post on this, but in the meantime, here's the rundown.

     

    Images processing in LR3 will come into LR4 set to PV2010.  They will still look the same, and they can remain in that state indefinitely.  That's why we've got process versions.

     

    If you update those photos to PV2012, it will try to convert the settings, but there's such a difference in the basic look of PV2010 vs. PV2012, that they won't match. 

     

    So, you either leave them as PV2010, or you reprocess.  Most people will leave as PV2010, and when they want to update a specific photo to PV2012 because they want to do something extra, then they'll reprocess.

     

    So your PV2010 presets will still work as normal on existing photos, and on any photos that you switch to PV2010 (or are automatically switched by the preset).  They may not work so well on new photos or ones that you've updated to PV2012.

     

    I think this is explaining the problem I'm having.  I've opened up LR4 imported some photos and tried to muck around with the new highlights and shadows.  Excpet they aren't there.


    The photos that I imported are also in my LR3 catalog.  Which is why I assume I can't see the spots to edit with Highlights and Shadows?

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2012 5:50 PM   in reply to ChromaticDramatic

    Yes...you'll have to upgrade them to PV2012 before you see the new tools.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2012 6:15 PM   in reply to VeloDramatic
     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2012 11:11 PM   in reply to VeloDramatic

    I'm honored

     

    First impressions:

     

    I never expected Adobe to redesign anything, so no surprise that they didn't - e.g. I wasn't expecting Lib/Dev module integration, or layers...

     

    I must say I didn't expect the reworking of the Basics. I thought Fill-Light and Brightness were here to stay... - I thought wrong.

     

    Anyway, it seems Lightroom now takes the liberty to recover highlights and shadow detail by default, and if you don't want that, you have to work to undo it. It used to be that you had to work to recover the highlights and shadow detail.

     

    The highlight recovery algorithm still leaves the top end a bit flat and desaturated, but it really does reduce the amount of time and effort required to make nice shots that have an extended dynamic range.

     

    NX2/active-d-lighting ain't got nuthin' on Lr4...

     

    Definitely there is far more control in the basic panel to shape the left and right ends of the histogram. which is a very good thing.

     

    It's like Eric took the Fill-Light algorithm and distributed it to all four sliders (whites, blacks, shadows, highlights).

     

    I miss the brightness slider, but it never did anything that can't be done with the tone curve.

     

    Love the RGB curves!

     

    Clarity: Digs a little deeper into the top end, and *way* deeper into the shadows. Although I like the ability to open shadows for detail, I wish there was a way to control the relative weight of clarity in the tonal regions, like Nik's tonal contrast tool. Sometimes I just want to clarify the midtones and leave the shadows dark, like Lr2&3. i.e. maybe 3 separate clarity sliders for each major tonal region would be better.

     

    Locals: The new locals are awesome, what can I say? - Still wish I could have HSL instead of just WB, and brush a tone curve, and vary sharpen radius locally (although I must admit, combining noise reduction with sharpening does allow one to sharpen things up locally without making 'em too scratchy). Local highlight & shadow control are already becoming two of my favorite new features. - all good stuff...

     

    Summary: So far I've only briefly evaluated the develop module.

     

    - Clarity is improved and creates an almost HDR-like effect - nicely done, high quality, but I desparately want to be able to tone down its effect in the shadows sometimes.

     

    - Basic tone adjustments - still getting used to these, but I think they're going to be awesome once I get the hang of it a little better (highlight recovery still leaves flattening).

     

    - RGB curves - didn't realize how much I missed this capability until having it again.

     

    - Locals: gotta love more color control, and especially highlight/shadow targeted tonal adjustment. local noise adjustment very welcome too.

     

    Overall I'm stoked about it, although worried about clarity and still adapting to missing fill & brightness sliders...

     

    PS - Like almost everybody, disappointed about no improvements to distraction removal, nor masking.

     

    This story still unfolding,

    Rob

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2012 11:24 PM   in reply to Rob Cole

    Rob -

     

    we're not worthy

    we're not worthy

    we're not worthy..

     

    (well at least im not)-

     

    You always seem to put stuff perfectly.  Thank you for speaking for the majority - again.

     

    And I fully agree on the fill light/brightness sliders.

     

    I just really wished to have seen new clone/heal capabilities - I HATE having to go to Photoshop JUST for that.  (me thinks this is done on PURPOSE though..) think of all the revenue Adobe would lose if they did incorporate killer clone/heal capabilities with LR...)

     

    peace -

    Kim

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2012 11:37 PM   in reply to xirta

    @xirta

    When you say Adobe refuses to listen, I think you mean they are not listening to you

     

    It is pretty unlikely after 4 versions that the modular interface will be changed massively, Maps does kinda break down the Library a bit (as does Import in some ways), but the original vision for the software remains intact.

     

    I rarely worry about the distinctions between modules because of the shortcut keys, I realised the other day that I almost never use the Module picker links.

     

    As for viewing Focal Points, the main reason for that is that Adobe doesn't use the Camera manufacturers' SDK, which (sometimes) offers that information. There are a couple of disadvantages to not using the SDK, but it does allow Adobe much more freedom to innovate - hence Process Versions.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 11, 2012 10:05 AM   in reply to RusticLightPhotography

    Thanks Kim.

     

    There's always an adjustment period, so to speak (pun not originally intended).

     

    PS - I don't think Adobe purposely denies Lightroom stuff as a ploy to get people to buy Photoshop, but I DO think Photoshop's capabilities weigh heavily into the decision making process of what to add to Lightroom. ACR is first and foremost a front-end to Photoshop - Lightroom was an afterthought...

     

    So, it may be a while before we see layers in Lightroom, or even content-aware fill... (hope I'm wrong).

     

    Cheers,

    Rob

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 11, 2012 10:25 AM   in reply to VeloDramatic

    VeloDramatic wrote:

     

    ... As a sports photographer, I process far too many files to delve into areas like RGB curves routinely...

     

     

    Indeed, RGB curves nearly always take a lot of fiddling, which often needs to be done on a per-photo basis.

     

    I mostly shoot landscapes and macros, mostly low volume, and having RGB curves keeps me from trying to get split-toning to do more than it was designed to do (or process externally).

     

     

    VeloDramatic wrote:

     

    ...I had my hopes set on speed and productivity enhancements. Time will tell whether I can wring a little improvement in those areas from LR4.

     

    I hear ya - not too many enhancements of this type in Lr4 - maybe Lr5... I assume you have registered ideas for improvement that might help you in this regard, eh?

     

     

    Cheers,

    Rob

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 11, 2012 11:18 AM   in reply to VeloDramatic

    Hi Michael,

     

    I'm not sure what to say here, sounds like Lr4b1 was not your release...

     

    Sorry I'm not being much fun...

     

    Cheers,

    Rob

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 11, 2012 11:27 AM   in reply to MethodPhoto

    MethodPhoto wrote:

    As for viewing Focal Points, the main reason for that is that Adobe doesn't use the Camera manufacturers' SDK, which (sometimes) offers that information. There are a couple of disadvantages to not using the SDK, but it does allow Adobe much more freedom to innovate - hence Process Versions.

     

    That's not really true -- Aperture shows focus points and they don't use manufacturers SDKs.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 11, 2012 11:46 AM   in reply to Tom-Rockwell

    Yeah, the data is readily available in exif metadata.

     

    But you have to be willing to read it, despite lack of documentation / support as standard... - something Adobe has not yet been willing to do.

     

    And it may be different for every class of cameras... - Adobe just hasn't wanted to bother with it, yet. Luc Renambot *almost* finished a plugin that could do it - not sure what happened to that project...

     

    http://luc.lakephoto.org/journal/viewfinder-plugin/

     

    I often keep NX2 open when running Lightroom, and just shoot a photo over to it for focus point viewing (NxToo plugin makes this a single click, but one could do the same thing using JB or JF's openamous in anythingamous plugins, or just right-click -> show in explorer -> double-click).

     

    Rob

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 12, 2012 12:55 AM   in reply to Tom-Rockwell

    "That's not really true -- Aperture shows focus points and they don't use manufacturers SDKs."

     

    It does use the camera makers' SDKs.

     
    |
    Mark as:
1 2 Previous Next
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points