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

Similar Messages

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.

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

How do I get read of before (or after) process version i Develop module?

Hi.
Going through my photos in the develop mode, I am given the opportunity to upgrade to process version 2012. As I want to decide pictures individually before updating, I check the box Review Changes Before/After before I click Update. Sometimes I want to keep the old profile, sometimes I prefer the 2012 version. Either way, I use the bottom left arrows to copy the changes one way or the other. But whenever I get back to that photo i Develop mode, it will keep appearing side by side. I thought it would be possible to keep only my updated changes, and make it the only one to appear in my Develop window?
Ole K

Fine (although I was aware of those things above)! So the procedure should be
1) Open a picture in Develop Mode
2) Click the exclaimation mark (if there is any)
3) Click "Update"
4) Copy the new settings/version to the old one (or vice versa), and - back to my original question -
5) Click "Y" to decide that the preferred version will be the one that appears (on top) the next time I open this picture?
Am I getting it? So far, I've only just found Julieanne Kosts video on this, but if someone out there could point me to a more detailed step-by-step tutorial, I'd appreciated it, as this seems to be a rather important issue in LR4:
Ole K
(Did I really write "read of"?)

I have a dual monitor setup. When I paste develop settings from one image to another, Lightroom switches the active window.

Strange problem. Lightroom 5.5. Windows 8.1. Dual monitor setup.
I'm processing a large batch of photos. I have Monitor #1 set as my main develop window, with Monitor #2 set only to display a larger version of the image I'm working with. If I copy the develop settings off of one image and try to paste them onto another image, Lightroom will switch from Monitor #1 to Monitor #2 as the main develop window, and will not display anything on Monitor #1.
If I then try to paste develop settings onto another image on Monitor #2, LR will then display a larger version of the image I'm working with on Monitor #1.
To work the way I want to, I have to continually drag my develop window back to Monitor #1 every time I try to paste develop settings onto a new image. How can I make this stop?

I just tried what I think you’re saying you’re doing and I don’t have the problem with LR 5.5 on Windows 7 SP 2.
Does the same thing happen whether you use the key shortcuts vs the Settings / Copy/Paste options on the menu?
I ask this because if you’re using the keyboard shortcuts, maybe you have some display-manager program that has bound itself to the Ctrl-Shift-V (paste settings) to the function of move-to-other-monitor which would do at least part of what you describe.
You can also test this theory by doing a Ctrl-Shift-V with an application other than LR as the active window and see if it moves. I suppose Ctrl-Shift-C might also play into it so try both of these hot-key combinations with a program that isn’t LR.
If none of this sheds any light on the situation, then give a more detailed description of the low-level functions you’re doing to accomplish the copy-paste of settings, so someone else could replicate the steps exactly.
Specific detailed steps, like:
left-click on source photo’s thumbnail in the filmstrip
press Ctrl-Shift-C to copy the settings
click Check-None
enable the white-balance and calibration checkboxes
click Ok
left-click on destination photo's thumbnail in the filmstrip
click on Settings / Paste Settings in LR’s menus to paste the settings to the selected photo

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

Multiple photo develop settings paste not working

Hi all keen photographers out there.
Using Lightroom V5.7. I adjust one photo aka highlights, shadows etc..then copy and paste to many many photos.sometimes over 1000 shots.
Only some of the photos will have the develop setting pasted.
Any ideas why some work and some don't.
Do it in Library grid view or through the filmstrip. Doesn't matter.
It used to work in V4..but has recently died.
Seems if you do over say 20-30 it just dies.
Any workarounds?
Thanks in advance.

Hi F, Yes they are all from the same Canon camera and all the same process version 2012.
I have PV checked with copy and paste. I also tried doing it without PV checked and still same results.
Such is the life of computer software! it is very frustrating, because once the settings are pasted (I have to do individually..not even small batches) the photos look so much better..as you can appreciate.
Thanks for your input too. It was very helpful and appreciated.
Cheers

Develop Settings

I have a PC, and I just upgraded to Production Premium 5.5 and bought Lightroom 4
Do develop settings applied in ACR show up in Lightroom 4?
Develope settings applied in Lightroom 4 do not appear in Bridge......
Are they the same "devlop settings"?

Ian Lyons wrote:
The new Process Version 2012 develop settings will not be available in any version of Camera Raw prior to version 7.
I thought that ACR 6.7 will able to interpret PV 2012. The only drawback in ACR 6.7 will be that the new PV 2012 settings will not be changeable in the ACR GUI. And this is already the case for ACR 6.7 RC (with a few rendering differences compared to LR4).
Quote from the lightroom journal:
The correct plug-in for Lightroom 4 and Photoshop CS5 compatibility is Camera Raw 6.7, currently available on Adobe Labs Please keep in mind that currently Camera Raw 6.7 is a a Release Candidate version of the plug-in.
...or did I misunderstand something?

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

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.

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

Bug Report: Process Version sometimes reports "nil"

I think this occurs mostly if not always when Process Version is 2003 - sometimes I read "nil" as process version develop setting, sometimes it reads "2003"(i.e. 5.0, if I remember right) - seems to be sort of random / intermittent.
I'm talking about the photo:getDevelopSettings function, 'ProcessVersion' key.
Rob

Post Author: Bandi
CA Forum: Crystal Reports
Hi Shannara,
It sounds like your patience with Crystal 11 is running thin
Not sure if this will help, but I had a similar issue a while ago. Speed was woeful to say the least. The way I fixed it was to right click on the desktop, then go to properties -> Settings tab -> Advanced button -> Troubleshoot tab and fiddled with the Hardware acceleration slider. Not sure what was causing the issue, but that sorted it for me.
Hope it helps, Anthony

LR2 - Auto Import develop settings won't stick.

As the subject says, in LR2 changes made to the develop settings preference in the auto import settings dialogue do not stick. I can select a different develop preset, but after closing the settings dialogue, new images import with the original preset. If I open the settings window again, the develop settings preference has been reset to their original state.
I've tried two computers and have the same result on both. Trashing prefs does nothing, but creating a new catalog seems to reset the auto import prefs dialogue, but whatever develop settings I select becomes fixed and unchangeable.
I use LR's auto import feature to work tethered with my MF digital setup on every project - it is crucial to my current workflow. This bug is small, but significant and will probably have me going back to V1 until I can find a fix so any help is appreciated.
Thanks,
Andy
(oh yeah, both systems are intel macs -- an iMac and a macbook pro -- and are up to date running osX 10.5.4)

Yes, I get the same thing with the sliders being greyed out. Funny thing is that the sliders *are* set exactly as in my preset and when I click 'yes update' to 2010 standards, the settings don't change but only the sliders become accessible. The thing is that I really don't want to be doing that with every import, even if you can do the whole batch at once. What I don't understand is that when I import with the preset turned off and apply it in Lightroom's Develop Module, it accepts it without a problem but that when I use the same preset on import, it won't work properly.
Now what the poster in the other thread said was:
"When I saved a new preset and selected to also save the process version, a line in the preset was created: ProcessVersion = "5.7". When I cut and paste that into all my other presets then the sliders were all active when I used them."
I have no idea what he is talking about or how one would do that. When I create a preset I simply click the + sign and in the pop up window select what I want, give it a name and that's it.
Edit: Sorry, I apparently overlooked the Process Version box in the preset panel! Must have been a case of not seeing the forest for the trees. Problem solved. Thanks.

Do LR3.5 develop settings (xmp) transfer to LR4?

I subcontract a lot of event work. I'm still using an older MBP which is 32bit so I can't upgrade to LR4 yet which requires a 64bit processor.
The studio that contracts me is running LR4 and they don't seem to think that the develop settings I make in LR3.5 are transferring to LR4. Is this possible?
If so, what's the solution?
I'm thinking an easy work-around would be to export all the files as DNGs? This would automatically include all changes that I make wouldn't it?
Thanks,
Dennis

Yes, they are transferring to Lr4, although Lr4 has different develop tools than Lr 3.5.
Lr4 gives you a choice of updating an image to the Process Version (PV) 2012, or leave the image at PV 2010 (or even PV 2003).
When an image that has been developed in Lr 3.5 is opened in the Develop Module of Lr 4 an exclamation mark appears in the bottom right corner, see screen shot:
When you click on the exclamation mark you will be asked if you want to update this photo (or alternatively all photos in the filmstrip) to PV 2012.
If you do, the Develop Panel on the right side changes to the new version of Lr4. If you don't update the right panel presents itself in the same way it did in Lr 3.5.
I suspect that your studio did not click on the exclamation mark and did not update the image to PV 2012.
Having said that: It is by no means mandatory that you update an image to PV 2012. Some images benefit from it, with other images it will deteriorate the image. It should be decided for each image individually.
That goes only for images that have been developed in Lr 3.5. If you i mport new images in Lr4 you generally would choose PV 2012.

Importing development settings from JPG

Hello everyone,
I have a JPG file that I've created in Lightroom from a RAW file.
My computer has crashed at some point, and I lost everything, but I managed to save the original RAW file.
Is it possible to recover the development settings from the JPG file, in order to re-edit the orignal RAW file (so I could make changes right from where I left off)?
Thanks for all of your help in advance,
Dan

Hey Dannyboy,
Dannyboy103 wrote:
I typed exactly what you wrote when you suggested I use the exiftool.
Right. I since amended that on Phil Harvey's recommendation, but to be frank, I don't understand it all perfectly, so bear with me.
Dannyboy103 wrote:
To your question, if I have the same settings tools - the Temp starts with 0 and can move between -100 to +100.
This is what's known as "incremental temperature" adjustment, not raw (kelvin), i.e. standard baked rgb file (e.g. tiff, jpeg).
Dannyboy103 wrote:
The other profile calibrations are the same.
I assume you mean sliders. What's on the camera calibration profile drop-down menu?
Dannyboy103 wrote:
I noticed that when working on a dng file, there is a slight change in the calibration profiles (no "white or "highlights" and there is a "fill light" option. Maybe other changes, but haven't really taken a real close look at it).
fill light is for photos utilizing process version 2010 (or 2003), i.e. legacy process versions. whites & highlights are for PV2012 photos (current process version).
Dannyboy103 wrote:
Why do you think that having the lens correction option available is a bad thing?
Using profile-based lens corrections is a bad thing if baked rgb file (e.g. tiff, jpeg) already has lens corrections applied, or is cropped... Such is the reason Adobe does not support profile-based lens corrections for rgb files, only raw files.
I'm guessing you weren't actually using profile-based lens corrections on your tiff, right? e.g.
As I said, it is possible to finesse metadata such that raw (profile-based) lens corrections can be applied to rgb files, but one needs to be careful, since it could make things worse instead of better (e.g. applying lens corrections when already applied, or applying them wrongly due to crop). I thought at first this is what was happening to you, but I think now I was wrong - what do you think?
Rob

Develop Settings - Process Version

Similar Messages

Maybe you are looking for