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.

Similar Messages

Can I remove process version warning in LR4?

I work in a studio where we use a DNG workflow - delivering DNG files to prepress. We are currently upgrading to LR4 to support some new cameras. Long story short, our prepress provider is using PSCS5 (and ACR 6.7) which means we'll need to keep our work in process 2010 for the forseeable future.
Given that I'll be sticking with process 2010 for a while, is there a way to turn off/disable the little exclamation point version warning?

Thanks Jim,
Even if it's not the answer I hoped for, it's good to know I should stop poking around menus and prefs.
Given my workflow and all of the variables at play, we'll just live with the little exclamation point in the corner. We'll be fine.

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

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

Warning icon on Engineer to Relational Model screen

Engineer to Relational Mode l shows warning icon on Attributes, Entities and Logical labels. I don't see the reason.
Do you know what this warning icon is about and how to tackle it?
Thanks,
Prakash

Hi Prakash,
Engineer to Relational Mode l shows warning icon on Attributes, Entities and Logical labels. I don't see the reasonThis mean something is changed. You can click on object and should look at details tab. Entity is composite object and it'll get warning mark also if some of components are changed.
At "compare/copy options" tab you can exclude some properties from compare process if you don't want them to be considered.
Philip

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

Error when installing OpsMgr reporting (Attempted to add warning icon to item OMREPORTING but since this was as NONVITALFAILURE case, we added an Error icon instead.)

Hi
I have the following scenario:
Two Management Server, the first
Management Server has the following functions:
- Management Server
- Operations Console
- Web Console
My second Management Server has the following
functions:
- Management Server
- Operations Console
A SQL Server with the
OperationsManager and OperationsManagerDW
bases.
My second Management Server, I installed the
service report server SQL,
created the foundation in my remote SQL
Server (ReportServerOpsMgr and
ReportServerOpsMgrTempDB). By adding the
feature of Reporting Server
it starts the installation process, but
at a certain point it gives me the following error message
in the Reporting Server log: Attempted
to add warning icon to
OMREPORTING item but since
this was the NONVITALFAILURE
case, we added an Error
icon instead.
Has anyone been through
this problem and can help me?
Thanks a lot!
Wilsterman Fernandes

Seems this is either a permissions issue or the it is a restriction configured for running external stored procedures
I suggest you remove the Reporting portion from the server, then remove the Reporting Service completely. After doing this, reboot the SQL and Management server=>install Reporting again.
Juke Chou
TechNet Community Support

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.

Camera Process 2010 not working in Lightroom 3

i can not use noise reduction in Camera Process 2010 on scanned images in lightroom 3 but camera process 2003 working fine.
I am using scanned tiff images and converting them to adobe DNG.
also camera process 2010 and 2003 work with camera raw iamges wiht my camera or wiht any other camera raw iamge but not with scanned one.
does anybody know the difference between Camera Process 2010 and 3?

do some reading on the new version like the readme etc. There is a lot of difference between the process version, mainly on denoising and demosaicing
What kind of scanner are you using?

POPUP_TO_DISPLAY_TEXT but with warning icon

Hi there ABAP-people, I've got simple question ...
... how can I do simple popup window with:
- warning icon
- message
- button (OK, proceed or sth)
I see there is a 'POPUP_TO_DISPLAY_TEXT' but it has 'INFO' icon...
there is a 'POPUP_WITH_WARNING' but ahve no warning ...
maybe You have some tip? I'd be thankful for help. Greetings. P.

hi piotr,
al are having options for your question.
use the best suitable for you..
POPUP_TO_CONFIRM_STEP - Create a dialog box in which you make a question whether the user wishes to perform the step.
POPUP_TO_CONFIRM_WITH_MESSAGE - Create a dialog box in which you inform the user about a specific decision point during an action.
POPUP_TO_CONFIRM_WITH_VALUE - Create a dialog box in which you make a question whether the user wishes to perform a processing step with a particular object.
POPUP_TO_DECIDE - Provide user with several choices as radio buttons
POPUP_TO_DECIDE_WITH_MESSAGE - Create a dialog box in which you inform the user about a specific decision point via a diagnosis text.
POPUP_TO_DISPLAY_TEXT - Create a dialog box in which you display a two-line message.
POPUP_TO_SELECT_MONTH - Popup to choose a month
POPUP_WITH_TABLE_DISPLAY - Provide a display of a table for user to select one, with the value of the table line returned when selected.
POPUP_TO_CONFIRM - Pop-up dialog confirm an action before it is carried out.
POPUP_TO_DISPLAY_TEXT - Displays a text in a modal screen
POPUP_TO_INFORM - Displays several lines of text. No OK or Cancel buttons.
Regards,
Prabhudas

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

Missing Process Version warning icon in LIghtroom 5

Similar Messages

Maybe you are looking for