Process Version

What is the effect of updating the process version used with LR 3 to that used with LR 4 on an image already processed in LR 3?

I would recommend that you not follow the 'save XMP in LR3' advice just given as it is incomplete and will potentially cause loss of data.
Rob Cole wrote:
You can save xmp in Lr3, then import those photos using Lr4b1 to play.
I have also imported almost everything else from my Lr3 catalog to Lr4, but Adobe does not recommend it, and most vocal forumers agree its a *very* BAD idea, and I should be ashamed of myself for even mentioning it...
1. Save your XMP Data for you LR3 Files. Select CTRL S
2. Export as a catalog and include the negatives a small subset of your images you wish to try in LR4.
3. Import into the LR4 PB, only those negatives which exported in Step 2 so that you are working on just the copies and not your originals. They should be segregated inside a folder with the name you gave your export as catalog in Step 2.
4. Realize that none of your 'testing' work may be usable in the final LR 4 release.

Similar Messages

  • Applying presets causes filter settings to get corrupted if process version updated

    I have an ongoing problem with Lightroom 5.7 including earlier versions.  The problem occurs when editing photos which use previous process versions (ie, 2010).  My presets all have the Current Process version checked (as they should).  Whenever I apply any preset to a photo, the settings for existing filters get corrupted (reset to 0).  This includes my Graduated Filter settings, Adjustment Brush settings and Radial Filter settings.  Those filters and their masks remain on the photo but their parameters have all been set to zero.  I keep falling into this trap since it's natural to use my presets when making updates to photos.  Often I don't realize this occurred until it's too late. 
    As a work-around (inconvenient) I can first manually update to the current process by right-clicking the photo and saying Settings/Update to Current Process (2012).  Or by clicking the Lightening Bolt button in the upper right corner.  But this must be done prior to applying any presets and I typically for get as my database has tens of thousands of pics. Even a preset with just the Process Version set will cause the filter settings to be corrupted.  I'm not interested in applying a batch or Quick Develop process to all at once since I need to inspect each one as the process is updated.  It would be great if this could be fixed in a maintenance release since it keeps biting me.  I think it's important that this be fixed in LR 6.0 also.  No doubt it's messed up many user's photos without them realizing it.  Does anyone know a work-around so Presets can be used?
    System: Win7 pro 64 (current), 4.2 GHz i7, 12GB, Lightroom 5.7.

    In my opinion: not a good idea to convert old photos en-batch.
    Recommend: convert (hand-selected photos) one at a time, or just use PV2012 on new photos.
    There are more than one reason:
    * As you know, process conversion yields very different results (if photo has been substantially edited).
    * It takes some time to polish your PV2012 editing skills.
    * Often when you are comparing PV2012 results to previous PV2010 results (which you've become familiar with, and like...), you may interpret differences in a more negative light, than if you were using PV2012 without comparing to a previous PV2010 version.
    This last one can not be over-stated. Numerous times I have converted and been disappointed, at least initially. Recovered highlights can seem like loss of contrast. Detail in shadows can be distracting after initial conversion, until you step back for a while, then re-look at it...
    Also, the process version itself (results I mean) takes some getting used to (even when not comparing to a previous legacy-pv edit). e.g. if you've become attached to the over-saturated shadows in previous process version, the shadows seem under-saturated in PV2012, etc...
    Rob

  • Process version 2010 to 2012 update differences...why?

    I am a retired computer professional and I have used LR since V3 first came out and have recently updated my photos from process version 2010 to PV2012.  I used the batch process as I have ~200 GB of photos. My batch process is as follows:
    In the Library module, I clicked on > Library> select Show Photos in Subfolders. I then selected the Develop module, opened a folder and selected the first photo and manually clicked on the ! icon to Update to Current Process (2012).  I then added all the photos in the filmstrip to my selection.  I then clicked on Sync button to open the Synchronize Settings dialog and clicked on Check None and then check marked only Process Version and clicked on Synchronize.
    I noticed that the batch process zeroed out all my settings in the Develop module Basic dialog.  I no longer have my previous 2010 settings listed for the photo and in some cases it looks like some of the images have defaulted to an unprocessed state (under or overexposed, lack of color saturation).  If  I select a photo in the Develop module and go History and select the setting just prior to the "Synchronize Settings"  to render it back to PV2010 and click on the image ! icon to update just that one photo, I get a totally different result.  I retain the previous settings in the Basic tab and only the new LR4 tool settings are changed.and the History then states "Update to Current Process (2012)".
    1.  Why the different labeled result in History for the two processes? 
    2.  Why are completely different results achieved in Develop module between the batch vs the manual update processes?
    3.  Have the photos really been updated from process version 2010 to PV2012 using the batch process listed above?  As far as I know, I did the batch process correctly, as I even double checked online prior to processing in batch.
    4.  Can the images be "batched" back to PV2010?   Would they change the photos that have been added since acquiring LR4 that are in PV2012?  I can load last weeks backup PV2010 LR4 catalog, but I have added new photos since then and it would be a hassle to process them over again.
    I am NOT happy with the results of my process update due to the loss of  Develop Module Basic settings and in the completely different results achieved between the batch vs the manual update processes.  I would like to keep my old settings that are not impacted by the PV2012 change and now they are gone in my current catalog. 
    Adobe, is this a BUG or a FEATURE?

    In my opinion: not a good idea to convert old photos en-batch.
    Recommend: convert (hand-selected photos) one at a time, or just use PV2012 on new photos.
    There are more than one reason:
    * As you know, process conversion yields very different results (if photo has been substantially edited).
    * It takes some time to polish your PV2012 editing skills.
    * Often when you are comparing PV2012 results to previous PV2010 results (which you've become familiar with, and like...), you may interpret differences in a more negative light, than if you were using PV2012 without comparing to a previous PV2010 version.
    This last one can not be over-stated. Numerous times I have converted and been disappointed, at least initially. Recovered highlights can seem like loss of contrast. Detail in shadows can be distracting after initial conversion, until you step back for a while, then re-look at it...
    Also, the process version itself (results I mean) takes some getting used to (even when not comparing to a previous legacy-pv edit). e.g. if you've become attached to the over-saturated shadows in previous process version, the shadows seem under-saturated in PV2012, etc...
    Rob

  • How to get current process version when photos imported?

    I have Lightroom 5 but my photos are still imported with the old process version (2010)  How can I get the current process version (2012) to be applied automatically on my imported photos?

    Hi Andreas,
    Did you ever get an answer to your problem?
    I am facing the same issue now and i cannot get a lead.
    Thanks,
    Dimitris

  • Process version filter request

    I would like to suggest that a filter for process version be added, either in the metadata filter or as an option for creating smart collections

    Yes. And now you point that out I see a "Previous Process Version" option under catalog in the left sidebar.

  • Missing Process Version warning icon in LIghtroom 5

    Since converting from LIghtroom 4 to 5 I the Process VErsion warning icon does not appear in the lower right of the preview panel when the file was processed using a 2003 or 2010 version.  How can I re-establish the icon?  Norm

    It changed in LR5 to a "Lightning Bolt" which you'll see under the Histogram in the Develop module.

  • Tether & Develop Settings in LR3 always get the 'Update Process Version'

    I am using tether with develop settings in LR3. I keep getting the 'Update Process Version' and it won't apply the filter unless I click the (!). It does this with newly created presets. Please help.

    awimaging wrote:
     bit of a waste of £78!
    Erm, 2 words... free trial? 
    Anyway, let's get you sorted out.  Are you the same hania on the POTN forums, or do you just have the same problem?
    First things first, when you mention repairing permissions, I guess you're a Mac user.
    First, hold down Opt while starting LR and see if you can start a clean catalog ok.  That'll determine whether it's catalog specific.
    Then go to Macintosh HD / Users / [your username] / Library / Preferences /  and move or delete any com.adobe.lightroom*.plist files.
    And while you're there, I'd also go to Macintosh HD / Users / [your  username] / Library / Application Support / Adobe / Lightroom / and move  that Lightroom folder somewhere else for the moment.
    Then see if it works.  Could be a few things - most likely are a problem with the catalog, corrupted preferences file, or a preset that it doesn't like.  We can exclude those quite easily using the above.

  • Develop Settings - Process Version

    The process version in the develop settings is sometimes nil, sometimes '5.0'(2003), and sometimes '5.7'(2010). - Begging the questions:
    (I haven't checked every one but so far if its read as nil by plugin, they're shown as 2003 in Lightroom UI)
    1. Why isn't it consistent?
    2. Is it safe to treat nil as PV2003?
    Thanks,
    Rob

    In my opinion: not a good idea to convert old photos en-batch.
    Recommend: convert (hand-selected photos) one at a time, or just use PV2012 on new photos.
    There are more than one reason:
    * As you know, process conversion yields very different results (if photo has been substantially edited).
    * It takes some time to polish your PV2012 editing skills.
    * Often when you are comparing PV2012 results to previous PV2010 results (which you've become familiar with, and like...), you may interpret differences in a more negative light, than if you were using PV2012 without comparing to a previous PV2010 version.
    This last one can not be over-stated. Numerous times I have converted and been disappointed, at least initially. Recovered highlights can seem like loss of contrast. Detail in shadows can be distracting after initial conversion, until you step back for a while, then re-look at it...
    Also, the process version itself (results I mean) takes some getting used to (even when not comparing to a previous legacy-pv edit). e.g. if you've become attached to the over-saturated shadows in previous process version, the shadows seem under-saturated in PV2012, etc...
    Rob

  • Changing Process Version adds +/- icon

    Something I found really annoying when upgrading to LR3.
    I asked LR 3 to update the process version to 2010 for all pictures. It worked. However, all my pictures are now being considered has having being modified, thus having the little +/- icon on the thumbnail.
    I was using this "visual help" in order to know which images were post-processed, and which are not. Now, all are considered as being modified, even if changing the process version did not in fact add any post treatment.

    The default values of all of the development parameters get applied when you import an image - they all have a value/setting.  No badge is displayed when the defaults (whatever you've decided you like as defaults) are applied.
    However, change one of them and the badge comes on.  That's what you're doing when you change the process version.
    Selby

  • Lightroom 4 Defaults to 2010 Process Version

    Mac OS X
    Creating a new catalog, drag and drop a raw file into it, go to develop module, it is in 2010 process version by default. I want 2012. Help!

    Geoff; How do I check import presets? When I go to the import window I can't find anything wrong, it seems everything is at its default but I could be wrong.
    Check the Develop Settings drop down menu in Apply During Import panel of Import window (right side of window). Ideally, it should be none.
    If you're saying for sure that everything is at default then it's possible that you've altered the default for your camera. Again, if this is the case then it's fairly easy to fix. Select one of the offending images, switch to Develop module, open 'Set Default Settings' dialog from Develop menu, then click on 'Restore Adobe Default Settings' button. You'll then need to select all of the images with wrong process in Library Grid view then click on 'Reset All' button (see Quick Develop panel).

  • Changing between process version 2012 to 2010 in LR4

    I know that the sharpening and noise reduction was improved for the 2010 process version.  Were they improved more for the 2012 version?  I would love to swich back to 2010 but I just want to make sure I don't loose the better quality of the sharpening and noise reduction.  Thank you for any insight!!

    Lauren424 wrote:
    I would love to swich back to 2010
    I realize you didn't ask for help with PV2012 (or a lecture about how it's better...), but I can't help but wonder: Why?
    But to answer your question more specifically:
    * Clarity was improved in PV2012, but sharpening and NR are same as PV2010.
    Rob

  • 2012 Process Version Alters Exposure/Contrast/Tone Curve

    In working with the LR4 beta, I've come across a couple odd results.  I imported some image folders containing raw, tiff and jpeg.  The images were updated to the 2012 Process Version on import.  I noticed that I had not saved out the metadata on the raw files for earlier edits in LR3.  I closed LR4, opened LR3, saved out the metadata, reopened LR4, read the metadata from the files and this, unsurprisingly, reverted them back to the 2010 Process Version.  When I update the raw images to the 2012 Process Version, the Exposure is reduced by 1 stop and Contrast is set to -33.  Additionally, a significant Tone Curve adjustment is made.  No such alterations occur to tiff or jpeg files in toggling back and forth between 2010 and 2012.
    Please advise.
    Thanks.

    Eric, I guess what I'm trying to figure out is if they aren't going to 'look' the same then why would that be.  Further, if no changes to the file were made (i.e., exposure, recovery, curves, etc) then why would there be such a radical change to the image on updating to a new process version? 
    As I noted earlier, I don't recall that updating to the 2010PV from the prior made such a change to images.  In fact I just tried it.  I switched back to 2003, then to 2010 then to 2012.  No change to the image going from 2003 to 2010.  Big change going from either 2003 to 2012 or 2010 to 2012.  To my way of thinking, if I take an image processed with the 2010PV and am happy with the way it looks (it's displayed on my website, I've printed and sold it, etc.) then I update to the 2012 PV I shouldn't have to re-edit the image to get the same 'look'.  I understand that due to the different controls some of the positions of the sliders may be different.  But the two images shouldn't 'look' different.  Take another example.  If I've got a set of images from a commercial shoot, have edited them in LR and provided to the client, then I update those images to the 2012PV in LR 4 and the resulting images aren't the same, I've got to spend time (and money) re-editing to get back to what I had before.  Does that seem right?  It sure doesn't to me.  It seems, actually, the exact opposite of what should be. 
    In the screen grabs above, this is a marked change to the image.  It's categorically not just a difference in slider/control positions to get the same 'look'.  It's a completely different image with a completely different look.  The file has been radically altered.  To me, that shouldn't be the case.
    EDIT:  I guess we were posting at the same time, Eric.  Sorry, I understand the explanation but it just doesn't make a lot of sense. 

  • Process Version 2012 - LR5

    Button in the lower-right corner of the photo to update to Current Process 2012 is gone in LR5?

    Thank you very much for your kind and insightful response.
    Could you help me with this other question:
    I noticed a odd behavior with regard photos imported em February 2013 with
    previous version or LR4:
    •             photos already adjusted have a new history step line: "From
    Metadata";
    •             photos not yet adjusted have the new history step line "Reset
    Settings" after the "import (dd-mm-yy hh:mm:ss)".
    Thanks in advance for your help.
    Daniel Bastos
    2013/8/24 ssprengel <[email protected]>
       Re: Process Version 2012 - LR5  created by ssprengel<http://forums.adobe.com/people/ssprengel>in
    Photoshop Lightroom - View the full discussion<http://forums.adobe.com/message/5623364#5623364

  • Update Process Version Dialog Box (2010 Process)

    How do I get this box back (it seems to have disappeared) only allowing me to update one photo at a time? I also tried copying the development setting by applying only the process setting check box (for an updated photo) but that doesn't seem to work either.

    Go to Preferences, in the General tab, and click on "reset all warnings".  That should make the Update Process Version dialog appear again.
    You can also select all your images in Library grid and go to the Photo menu, choose "Develop Settings" then "Update to Current Process (2010)" to update multiple images at once.

  • Process Version 2010

    I'm just curious how many other people out there are like me and still use Process Version 2010?  I find that I cannot achieve the same quality results using PV 2012 - those controls simply do not offer me the flexibilty and overal tonal control that I have with PV2010.  I shoot and edit fashion photography professionally, and I have very specific needs regarding tonality adjustments. I find I am reliant on Recovery, Fill Light, Blacks and Brightness sliders in order to fine tune lighting falloff on skin and clothing.  I have tried numerous times to use PV2012 but the results are far inferior to PV2010 for my needs.  Anyone else out there feel the same?  In case you're wondering, you can see examples of my PV 2010 work on pretty much all the photos on my website (davidwalden dot com). I just can't get these results with PV2012. 
    Out of curiosity, is there a technical reason why Adobe can't combine both process version controls, and offer all sliders from both versions in one layout?
    thanks,
    d

    trshaner wrote:
    Combining PV2012's and PV2010's controls would be like adding a 10-band audio frequency equalizer to your sound system and then still using the Bass and Treble controls. They simply wouldn't play (pun) together very well and would make PV2012 even more difficult to use.
    That's one way of looking at it, but I don't think the difference is that straighfroward. It's more like they've replaced some controls with other controls that they deem "superior", but honestly the 2 sets of controls yield completely difference results.  Based on the results that you want, you might prefer one set of controls over the other.  I definitely do not think that having both sets in one interface would make it more difficult - it would be the best solution.  That would be the 10-band equalizer you mentioned
    Highlights and Whites is supposed to be a more refined version of Recovery. I get that, and probably in some situations it is superior (architecture and nature photography). Btw, I looked at the Siggraph paper and yes, once again they are using architecture and naturally lit environments to show how much detail can be recovered.  Recovering detail, in a very basic sense, is only one (limited) use of a photo editing toolset.  Another (more important imho) use is controlling color and contrast on human skin at different tonality ranges.  This is my primary concern during photo editing, and architecture and nature photo editing does not address these concerns. I find that the contrast that I get in highlight regions using Recovery gives me better results. Also, I use this in combination with the ToneCurve - Lights and Highlights sliders - to tweak the highlight ratios.
    It is interesting that the 2012 Basic controls nearly mirror the ToneCurve sliders - Highlights, Lights, Darks and Shadows.  Now we have 2 sets of controls in 2012 - Basic and ToneCurve - that affect similar regions.  Is this redundant at all?  Perhaps.  I find that the ToneCurve and 2010 Basic controls actually compliment each other better, because they have distinct functional differences.   For example, the Blacks slider is more akin to setting a black points using a Levels adjustment in Photoshop.  This is different from using the Shadows slider in the ToneCurve, and different from setting the ToneCurve black point manually - these things yield different results. From my experience it is better to use the Blacks slider for this, and then tweak the value using the ToneCurve black point manually (although I typically use the the manual ToneCurve points for adjusting contrast, not for setting black points - that's why an additional Levels adjustment widget would be a superior solution imho).
    Also, getting back to my earlier point about contrast at different tonalities, one thing that I have historically used Blacks and Fill Light in PV2010 is for adding/controlling *mid-tone* contrast.  Increasing these together has the effect of increasing contrast in mid-tonal regions where previously no contrast was perceptible. This is an important part of color correction process. I have tried to replicate this effect in PV2012, but the mid-tones loose the contrast and detail. Adjusting the PV2012 Shadows and Blacks sliders from my experience produces "smooth" results, but not "desireable" results. Meaning that, the darker tonalities are lifted, but the contrast and detail is lost.
    I will try to post one or more examples showing some of these concerns.  I appreciate all the feedback you guys give.
    -d

  • Update to process version 2010 & smart collection "has adjustments"

    Buying the new Lightroom 3 version ofcourse I wanted to profit of the new process version. So I selected all images I had "not adjusted" before and selected Update to Process version 2010. This works great.
    However I now have one problem.
    I had and have a Smart collection which helps me in my workflow to find all images that have not been touched, so have no adjustments.
    This Smart collection has become worthless because of the update to process version 2010 all images have been adjusted.
    Ok, this is correct and yet I miss my ability to select images which I have not adjusted.
    Once I have set the default process version to 2010 all new images are correctly shown.
    Question: how can I select all those images which have only the process version updated, but have no further adjustments?

    Changing the process to version 2010 is considered as an adjustment; it will appear in the photo's history in the same way as any other development adjustment. The smart filter condition "Has Adjustments" only has a true or false setting so you can't distinguish the process version adjustment from any other. Instead of using this method to spot the photos I need to work on, I find that I have more control over my workflow by using keywords such as "review", "develop", "print"; you can make these keywords not exportable so that they are not part of the keyword list in exported photos.
    Interestingly, when one or more photos are selected in the  film strip and the reset button is clicked in develop mode the photo  will revert back to its original state, the "Has Adjustments" condition  will become false, but the process version will remain at 2010.
    If you have a backup of your catalog that precedes the step where you updated the process version of all photos, open this backup, add a keyword of your choice to all the photos that have not been touched, then apply the process version change. You can then change your smart catalog to use this keyword as opposed to the "Has Adjustment" condition and remove the keyword you have set on photos that have not been touched as soon as you are done editing them. IMPORTANT: Any changes you have made following the date and time of the backup will be lost.
    If you don't have a backup to go to, you will have to manually identify which photos, which from your point of view, have not been touched.
    Some ideas:
    If you did not make other edits following the change of the process version, and have not made other edits on that date, you could built a smart collection based on the 'Edit Date" and then reset the develop settings of all the photos in that collection.
    Another possible condition is a "Capture Date" range where you know photos haven't been touched yet.
    There may be other options, there may be a plugin that can help you, or ultimately there would be means to access the database outside of Lightroom - contact me if you get that desperate to fix this!
    http://www.BDLImagery.com

Maybe you are looking for

  • Emulating HTTP POST for file upload with J2ME

    I have search through a lot of site and couldn't find the actual code. I try to emulate below html with J2ME. <form method="POST" enctype="multipart/form-data" action="Insert.asp"> <td>File :</td><td> <input type="file" name="file" size="40"></td></t

  • How to avoid form submitting ?

    All, I have a form that gets submitted when I press a button, and I need to prevent the submitting of the data on the database, which in our case is an update of the record. In the bean I want to get the user inputs, so I need the submitted values of

  • Can't click inside td or tr ???

    This is annoying. When I click inside a cell or a row on SOME tables, the entire table is selected. I just want to place the cursor inside the <td> so I can either enter text or insert a graphic. I know there are machinations I can accomplish this (c

  • Modifying result of the output of the search help

    Hello Experts, I am creating search help on field FUNCID in table EQUZ. Thing is I need to only display those values of FUNCID which has some values.. i.e if there is blank entry FUNCID in table EQUZ it should not be gettin displayed. Thanks in advan

  • First high performance PC buy..thoughts for CS6

    I am looking to buy a Dell PC to run Production Premium. I will be editing HD DSLR footage of my wedding using CS6. I want a system that will handle this media but do not want to go overboard highend. Here is what I found so far. BASE XPS 8500 Chassi