Lightroom Presets "process version"

I am creating lightroom presets to share (Lightroom 4)
I am confused about the box "precess version". Should I click it or not? What will happen if I click it and then there is a lightroom 5? Not sure what is the best choice and why there is even that option.
Thanks for any help!
Sarah

If Lightroom handled process version the way it should, that box would not exist. i.e. Lightroom would know whether there are process specific settings in it, and handle in an appropriate fashion.
However, Lightroom's handling of process version in presets is abysmal.
If I used presets, I would *never* check that box, and instead, keep presets with process-specific settings in a special folder, and/or give an indicative name.
Then manage process-specific presets without Lightroom intervention, until Lightroom handling is brought up to snuff, at which time existing presets could be retrofitted, if need be.
In any case, if preset is presently universally applicable, I recommend *not* checking that box, since there is no Lr5 yet. When Lr5 is released, you can revisit that decision, and consider retrofitting.
If preset is NOT universally applicable (*does* include process-version specific settings), then it's a tougher call. Either way, it won't do the right thing if you try and apply it to a photo with the wrong process version. So it's a matter of how you prefer it to fail. If you have the box checked, then it will convert PV and apply preset. Unfortunately, it won't let the conversion "settle" before applying the preset, so it won't work correctly, if at all, and anyway, it's usually not good to convert PV this way, especially if there are pre-existing edits. On the other hand, if you don't have the box checked, and you apply to photo with wrong process version, it will just ignore the process-version specific settings, which ain't much fun either... - it won't tell you about any of this, so you or your "clients" must take full responsibility for knowing whether they are applying a preset to compatibly edited photos or not.
If you decide you want to sometimes or always check that box, I would still handle presets in the aforementioned fashion, i.e. name and store so the scope of applicability of a preset is clear.
Maybe some other preset users will have a better idea for you.
Rob

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

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.

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).

Why Process 2003 when using Lightroom-Preset on Import?

Hi,
When I choose one of the predefined sharpening presets ("Sharpening - Narrow Edges (Scenic)" or "Sharpening - Wide Edges (Faces)") on import, then my process version gets set to 2003. When I choose "None" for the preset, then the process is 2010. When I choose one of these presets after import then the process remains at 2010. I did not try other presets yet. This seems to be independent from the catalog, I also tried this in a newly created catalog.
Since these presets are predefined I cannot even update them with the new process version.
Does anybody have the same experience? Seems like a bug to me.
Thanks, Robert

the-ninth7 wrote:
Hi,
When I choose one of the predefined sharpening presets ("Sharpening - Narrow Edges (Scenic)" or "Sharpening - Wide Edges (Faces)") on import, then my process version gets set to 2003. When I choose "None" for the preset, then the process is 2010. When I choose one of these presets after import then the process remains at 2010. I did not try other presets yet. This seems to be independent from the catalog, I also tried this in a newly created catalog.
Since these presets are predefined I cannot even update them with the new process version.
Does anybody have the same experience? Seems like a bug to me.
Thanks, Robert
LR 3.3 says this bug is fixed!
Bob Frost

A lightroom preset to produce a RAW conversion that always looks like the camera-processed JPG?

Hi,
Any tips on how to make a Lightroom preset that will render the RAW file in a manner that looks remotely the same as the picture displayed when shot?
I'm not talking about camera calibration > camera standed, portrait etc.
With Lightrooms clunky default adjustments the histogram looks correct; i.e. the way it did when it was shot. The image also looks horrible; clipped blacks, too contrasty etc. because it arbitrarily boosts Brightness +50, Contrast +25
When I zero the settings the histogram shifts completely away from the way it was shot, as if it was underexposed, which is not correct. I've tested this with perfect exposures using a GMB colour chart.
I guess the camera is showing me a histogram of the JPEG after it has been processed.
Is there a quantifiable way to replicate this other than playing with the sliders until the RAW roughly matches the JPG and then saving the preset?
Thanks.
Update - I'm using a Canon 5DMkII and a 1DsMkII

Good grief. When I photograph a color chart, under controlled lighting conditions, exposed perfectly, that is what I want to see as the default RAW conversion, with acurate values. In fact with camera calibrations that is pretty much how it works. It's not open to interpretation. Blacks have a certain value, neutral 8, neutral 6.8 etc.
If not, then give me the tools to accomplish this quickly. In Photoshop I can shoot a scene under controlled lighting, shoot a color chart in the first frame, create a custom curve and apply this to every subsequent shot. There is a rough way to do this in LR but it's quite a backward step.
THEN I can have a filed day, changing whatever I want, but I do not like randomly dragging sliders until it "looks ok". I stopped doing that my first year of Photoshop when I learned how to use the color sampler correctly.
"If you shoot raw (as opposed to JPEG) then YOU have the power and capability to decide what stuff is supposed to look like. "
I understand I have the power to decide what stuff looks like. Nothing I have said so far argues against this. I'm asking for an accurate baseline, from which I can let my creativity run wild.
" I encourage people to ignore the LCD and go with your guts", "If you are lazy and don't want to be bothered rendering the scene, yes, I can understand why you would want somebody else to control the interpretation of the scene"
The LCD and the histogram are a quick way of evaluating correct exposure for a shot, so that blacks are not clipped and highlights are not blown out and lost forever. They are standard TOOLs of modern photography. To not use them is illogical. It would be like instructing people not to use the camera's inbuilt light meter, because it's "more creative" without it.
It does not have to be one extreme or the other. People seem to be saying "reject the jpg - it means nothing. Let the artist in you decide" and yet they blithely accept the default settings Lightroom gives. My point is, the camera rendering is a good REFERENCE POINT, far more accurate to what you saw on the day, and far more relevant, than LR's adjustments.
Once I have an accurate rendering, quickly, THEN I can be creative and enjoy the power and flexibility of RAW. If nothing else, it's a much faster way to work.

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.

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

Can I convert a Camera Raw preset to a Lightroom preset?

I have number of presets in Camera Raw that I use in PS compositing. However, I'd like to use some of them in Lightroom now for my photography. Is there a way to convert them? The Camera Raw presets are saved in an .xmp file, while the Lightroom preset have a .lrpreset extension. They have similar information, but the formatting is a bit different (the .xmp looks more like an XML file). Any ideas?

Thanks David, that worked. I had been using Save Image in Camera Raw and didn't know why the .xmp sidecar wasn't being saved. I do wish there was a more automated way to do this, but my searches have come up empty. Lightroom puts a, presumably, unique ID at the beginning of each preset that the Camera Raw versions don't have, and who knows where it's generated from.

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

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 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

Problem: New photos in LR 3.3 but old process version

I have a strange problem when importing new pictures to Lightroom 3.3 (Mac, OSX 10.5.8):
Whenever I have imported some pictures and beging working on them in the Devleop module, I get the exclamation point with LR asking me if I want to upgrade the process version from 2003 to 2010.
The pictures are "brand new" and have not been imported in LR 2, so I really don't understand why LR thinks the images have been worked on with a previous process version. I have even uninstalled LR 2 from my system, hoping this would eliminate the problem. Not so...
Any suggestions?

Yeah, I think we all have somewhat different ways of doing things in our workfklows :-)
Just to clarify, let me explain what works for me (at least at the moment)
Copy all images from memory card to new, appropiately named folder on computer's hard drive
Rename all files in that folder according to year, month, client, project etc.
Back-up the folder to external RAID 1 hard drive (and later run Time Machine on another external drive to make a second back-up copy)
Browse through images in Bridge or Nikon View NX 2, select the ones I want to work with and apply rating
Use filter to only show rated images (i. e. selects)
Import selects to Lightroom and, most likely, narrow number of selections further down by using LRs flag rating
Edit final selects in Lightroom and Photoshop
My aim with this workflow is to things:
1) Make sure I always have ALL images captured during any shoot, (properly organised in a folder and with filenames that are easily identified) - but not necessarily all managed by Lightroom
2) Prevent the LR catalog file from growing to gargantuan dimensions and slowing down performance
I realise that LR is super powerful for renaming, rating, sorting, selecting etc. On the other hand, I see no need for LR to keep track of 100 RAW files from a shoot when I only need, say, 10 of those images for the client
If, at some point in the future, a client should want to review all the images from the shoot and maybe want some more than originally selected, I can still find all the original files quickly and import additional selects into LR to work on.
Well, that's just my way of doing things at the moment. I am sure it will change over time.
Oh, there is by the way one exception: When I am shooting in the studio, I almost always shoot tethered directly into LR. Which means that in these cases, all images from the shoot are obviously imported to and managed by Lightroom... :-)
Regards,

Missing print templates - Lightroom preset ones

All the preset Lightroom PRINT templates have disappeared. I see the folder on the left that says Print templates and Lightroom templates and user templates. If I import templates they show up in user templates as expected but the Lightroom Templates is completely empty - just pops up new folder box. I have checked preferences and looked for the template folder. I just has a folder for user templates which seems to be what the problem is. I have uninstalled and reinstalled several times to no avail. I also went back and deleted old versions (3,4) and the preferences files and every other file/folder I could find relating to lightroom including catalogs. I have lightroom installed on both my laptop and Imac. The problem is occuring on both so it seems that accidently deleting something is unlikely. I've never looked at the print module before so this may have been going on for a long time.
Any ideas on how to get these.
<moved by mod from downloading,installing,setting up - kglad>

I assume you mean, Edit / Preferences... [presets tab] Location: [Show Lightroom Presets Folder]. If you haven't yet saved any print presets of your own, then LR has not yet had any need of a User folder to contain such. So one may not yet have been made.
The easiest way to get LR to do that, (and to be sure that you are looking in the right place) : click the + icon next to Template Browser in Print module.
IOW: save a dummy print preset, doesn't matter about its contents, but enter some very distinctive name and then click Create. By default this should go into "User Templates", which is made as necessary, though you can choose to make a differently named folder if you prefer.
Full path on my Win8.1 is C:\Users\[username]\AppData\Roaming\Adobe\Lightroom\Print Templates\User Templates
Then take a look in Explorer and see what has changed - if there's any problem, you can always disk search for whatever distinctive template name you have just entered. Copy your other bought templates alongside this new dummy print preset, restart LR and you should be able to start using any of those. Delete the dummy preset in due course.
(Note that it is quite usual for built-in LR presets to be held somewhere quite different, than user created or user added items. The provided choices such as "(1) 4 x 6" and "custom 1 over 2" may not be findable anywhere on disk, for example.)

I am thinking about purchasing the CC for Photography monthly plan. Will I be able to use Lightroom Presets that I have already purchased previously?

I have Lightroom 4 and Photoshop CS2. I am thinking about getting the monthly plann for CC. I just wanted to know if I can use all the Lightroom Presets and Photoshop Actions that I have already purchased?

Yes, they will transfer across to the new version of Lr when you install it.

Lightroom Presets "process version"

Similar Messages

Maybe you are looking for