Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About richardplondon
since
Jul 07, 2008
Online
richardplondon
Mentor
1869
Posts
490
Likes
193
Solutions
Oct 08, 2020
11:56 AM
Another suggestion for overlaying small relative tonal tweaks: Tone Curve. This works independently of (and, on top of) Basic adjustments whatever those may be. You can apply, revisit, and perhaps later re-zero, a consistent adjustment across a whole batch of photos (e.g. using AutoSync) without touching their individualised Basic panel settings. So long as you are not already applying Tone Curve adjustments variably to these images, which would be disrupted. A similar idea might be done with a local adjustment, say a gradient filter set to cover the entire image area. That can be overlaid as a consistent adjustment "overlay" (more accurately, "underlay") onto many images whose other processing otherwise varies. Again, not so good if you are already using this tool onto these images.
... View more
Oct 08, 2020
04:13 AM
You shouldn't need to go and find Collapse All each time. Click in the heading for any panel that's taking up too much screen space, to collapse that, then again to open that up. Ctrl+click (Cmd+click) on any one panel, to do this to them all. You should still always see the Collections panel when you scroll down beyond Folders, though. Unless it has been concealed (un-checked from appearing at all).
... View more
Oct 07, 2020
05:09 AM
As a tip: rather than needing to re-check all the import options every single time, you can set up known import settings and then save those as a named import preset. Aside from annually changing the copyright year applied by metadata preset, one can employ the exact same import preset over many years. Recalling that (tried and tested) preset, each time, ensures with a single click that there will never be any surprises. No leftover keywords or other unwanted import settings. I have LR auto-file by capture date, hence the Copy destination never requires any input from me whatever. And I have another import preset suitably set up for Add imports. My only involvement is to recall the preset, (optionally) type in whatever batch keywords are appropriate for this particular new set, and click Import. Hence the opportunities for pilot error are few, and the user effort is minimal.
... View more
Oct 06, 2020
08:35 AM
2 Likes
If you lay out the overall photo in the Print module, on a right sized "page" as you would want to eventually print it - and if you turn off any output PPI resolution override, and enable "Dimensions" in the Rulers, Grid & Guides panel - the photo reports what is the effective native PPI coming from the source image, as well as the page dimensions of this, under this particular printing scenario. You can save this as a print collection to preserve the current print settings, and come back to those. Now you can make a virtual copy of that same photo; crop it down to show just your ""test extract" area; then lay that image out in the Print module onto a suitably smaller page size; turning on the same "Dimensions"info. Resize this cropped extract on the small page, watching the effective native PPI figure change after you do so. Repeat by trial and error, fiddling with the crop boundary as needed so it still fits, until the effective native PPI figure that's reported, is reasonably close to the same figure for this, that you saw for the whole photo. This extract is now sized to print at (near-enough) the same physical scale, as the full photo would. So that can act as a representative test print.
... View more
Oct 06, 2020
05:21 AM
edit: I meant, "what you can make use of for filtering or for a SC (smart collection)"
... View more
Oct 06, 2020
05:19 AM
If making a Smart Collection, a text search on "Copy" will not reliably find every Virtual Copy since the Copy Name metadata is not necessarily always filled in with "Copy1", or 2 etc. That may have been edited to something different and more informative, also each Proofing Copy gets automatically named according to the output being soft-proofed for. It will also not reliably find only Virtual Copies - but, anything that happens to show the character string "C O P Y" incidentally, somewhere. Could be in a Caption, or in the folder name, or within a keyword. What you can make use of (for filtering or for a VC), is that Master copies tend not to have any text showing in their Copy Name field. A Virtual Copy pretty much always does. Only if you have gone out of your way to fill text in for a Master, or remove auto-created naming from a VC, or if you have switched master and copy status between two image versions, will that method be unreliable. For example, below are Smart Collection criteria selecting for images with the keyword "france", that (according to the above assumption) are probably virtual copies, and that also are rated two stars minimum:
... View more
Oct 05, 2020
11:48 AM
Just as a general observation, I've noticed that some people can relax into LR's flow, while others find themselves constantly swimming against that! I do find the former way is far less tiring (also more productive, in my experience) 😄
... View more
Oct 05, 2020
11:18 AM
Yes they are taking up some disk space. They are effectively snapshots of how the Catalog was at that moment: if you accidentally do some unintended actions or your Catalog becomes corrupted in some way, they offer some ability to "go back in time" to before this unwanted thing happened. I suggest, retain only a few, but avoid ONLY having very recent ones. Because if you discover that you accidentally deleted or messed up a lot of images two weeks ago - but the only backups available are all from the last few days - all those backups will show the same (undesired) content so far as those images. But if you have always got one from a month or two ago, and one from a week or two ago, and a few from recent days - you are very well covered against any nasty surprises. It is far better policy if possible, to have these backups saved into a different storage drive, than the one where your main working Catalog lives. That way if this storage drive ever fails, those backups won't have been made useless. Alternatively, if you make a regular backup of your image files (the imported Raws, camera JPGs, Photoshop edited files...) onto a separate drive - that is then disconnected and stored separate from your computer - then by including some Catalog backups with that, you have got the means to re-create your entire image library with all work preserved, even after something catastrophic happens to your entire computer.
... View more
Oct 05, 2020
11:03 AM
2 Likes
These options about "overwrite" when exporting: they only refer to what happens if a prior export is encountered, with the same filename and in the same place, as a new export is about to be saved. That is a quite different matter, than overwriting the original source file. Lightroom is always working FROM that source file (in order to create varying separate outputs, using that as a fixed basis); it is not working ON that source file (to change it directly). The imported file, and any exported output files, serve entirely different purposes and are therefore treated differently. It's like a film negative, vs a particular enlarged print made from that negative. Or like a musical composition, vs a particular performance of that piece of music. Two very different things: one is the (fixed) basis for creating the other (variably); they are not interchangeable. Even if both happened to be JPGs: one would be an original camera JPG, the other a derived output JPG, and that is a very significant difference so far as workflow. To re-create one you would have to go and take the identical photo again; while to re-create the other, is trivially easy. I advise: always make your exports into a different place than your imported files; do not confuse matters by re-importing those exports back to your LR Classic Catalog; make them with a particular usage in mind; regard them as otherwise and thereafter, disposable.
... View more
Oct 05, 2020
07:14 AM
aargh .. edit post not working. not aware of any plugin that would help DO this.
... View more
Oct 05, 2020
07:12 AM
There is no hidden secret interface for achieving such things, just those options that you currently see. I am not aware of any plugins that would help di this, nor whether the SDK even permits such a thing. In the case of "Edit in PS" there is an opportunity to override the saving name later, when the image first gets written to disk, and have that be the filename that is then made known to the Catalog. But with all other external editing, the saving / re-importing name has already been established by LR before the external editor sees anything. So changing the saving name later, merely creates an extra copy that LR knows nothing about. One workaround may be to use an Export preset which appends the desired text to the file-naming, sets the location to be the same as that of the relevant source file, calls the desired external application in Postprocessing options, selects the desired kind of TIFF format, and selects to re-import the exported file to the current Catalog. But this is not as well integrated IMO, and does not offer all the same options, as the Edit In... function does. Or how about, a few workflow keywords that you can apply in LR onto the newly made externally edited file version, to flag up which tools have been employed? Otherwise, various metadata fields can hold editing notes, if that is important to you. Sometimes e.g. the Nik tools may be employed as smart filters inside the PS environment, alongside other operations 0 rather than as separate external stand-alone applications requiring a separate save. In that case such per-editor suffixes would not discriminate - but keywords or notes could still do so. This forum is just a user-to-user area but if you want to make a Feature Request, you can click through to a separate Feedback forum that is monitored more closely by Adobe AFAIK. On this forum's main page, that's the lowest link in the right hand sidebar.
... View more
Oct 05, 2020
05:06 AM
1 Like
Collapsing stacks hides those images and removes them (temporarily) from consideration. Attribute filtering searches only on whatever is currently visible, and then narrows that further. If you don't want to expand all stacks before filtering, you could use a Smart Collection approach instead. That always starts from the entire image library, and narrows down to fewer images only as its own inclusion criteria dictate.
... View more
Oct 05, 2020
03:48 AM
Hmm. I do notice "..Asia's longest highways..." and know that MS Word's autocorrect often substitutes a true 'curly' apostrophe character, when a 'wedge' single quote mark characterhas been typed. And some 'control' or 'format related' characters from MS Word might have become included in the copy-pasted data. LR should ignore these but who knows. Might it be worthwhile to try pasting keywords into LR out of a plain-text editor (such as Notepad), instead?
... View more
Oct 04, 2020
01:43 PM
Can you post an example of the keywording text you are pasting, and explain where that has come from? I just wonder whether there might be some bad syntax / characters in that (how the keywords are separated, how keyword nesting, synonyms etc are expressed). If you just want to make a number of selected images share the same keywords as a chosen image, you can highlight that one along with the others, and use the "Sync Metadata" feature. I am unclear from your description whether your Collection contains virtual copies, or instances of the master copies. The idea of "at the folder level" vs "in the collection" being any different, so far as the attributes a given image has, did suggest that to me also. Just to recap this, a virtual copy starts out with whatever keywords its master copy possessed at that moment, but these are thereafter independent.
... View more
Oct 04, 2020
03:21 AM
1 Like
When AutoSync is turned off in the Library module (this is independent, of whether AutoSync is turned on or off in the Develop module) - anthing you do in the Keywording panel applies only to your active image (the one that shows in Loupe view; the slightly brighter-highlighted image, if you have got several highlighted). Changes are not applied to other highlighted images. So if you have got several keyworded images highlighted, then delete keywords and put in new ones - only this image is affected - the other images still show the same keywords as before. If you turn on AutoSync for the Library module, the keywording panel now reflects that multiple images may be affected by an alteration. There's an additional bit of syntax: where a particular keyword is assigned to only some images in the current set, it has an asterisk after it. Editing out this asterisk causes that keyword to be present on all of the set, instead of only some. Deleting the keyword altogether removes it from the whole set. And typing in a new keyword applies it to the whole set - because of AutoSync.
... View more
Oct 01, 2020
03:37 PM
1 Like
Not for each individual photo, not with individual printing settings. One core principle of Lightroom, is not to treat images as output-specific. But: in the print module you can create a "print collection" which remembers a particular set of photos, and also recalls a particular setup for printing those. This setup can if you want produce JPG output, saved into a folder, rather then sending a print job to hardware. Or: if you want to use Export instead, you can save desired export settings as a named preset. Then any photos that you want to associate with this particular export preset can be gathered into a special collection, or be given a special keyword, or.... whatever. That way you can later find them all, and batch output them using this export preset.
... View more
Sep 29, 2020
10:20 AM
Lightroom Classic does not much mind where the Catalog is stored. On the external drive would be the simplest to implement: LrC will regard that as a local drive. At the same time, the addressing of the images themselves will remain the same for either context. What would not work, for opening a Catalog from, is a networked location (though that would be OK for images).
... View more
Sep 28, 2020
08:32 AM
Click on "Submit Product Feedback" in the main page for this forum, right sidebar, at the bottom.
... View more
Sep 28, 2020
07:50 AM
Gary: to explain, I am merely a user - as nearly all the people here are. This is a mutual-support area so we can learn as much from the questions, as we do from the answers 😄 . There is a separate area for formal feature requests, which IS monitored by Adobe employees (AFAIK). This idea of user editable shortcuts has (I believe) been suggested there many times already - but you could add your vote too if you wanted.
... View more
Sep 27, 2020
04:00 AM
1 Like
Provided you have got the Raw files that is the main thing: you don't need to take the photographs again! [What you've really lost is some time and effort. But often re-processing a shot, having learnt the lessons from before, can turn out for the better. More decisive, less laboured. Of course if you did seek to exactly match the prior edits, that would be extremely difficult to do. But why would anyone set such an aim...? 😄 ] There are a number of ways XMP sidecars can have come into existence. One way is through the involvement of another program than Lightroom Classic, at some point. ACR for example, or various non-Adobe products. Or it may be that Lightroom Classic wrote a copy of (some of) its Catalog metadata out to file, at some moment. That may have been your most recent edits (for example when LrC's set to write out copies of each change as it happens), or some earlier image statewritten on demand. If the only record of latest edits turns out to have been within the Catalog, those latest edits are now lost (unless a Catalog backup is available). But whatever is in the XMP, that is understandabe to Lightroom Classic: you should be able to recover at least that during import (which is automatic at import). Just make LrC is not immediately overriding that, with settings coming from an at-import preset). Virtual copies only have any existence inside a Catalog hence XMP can be of no use with those. Snapshots - even when saved from a virtual copy - are included in XMP (if written to disk). Collections and collection sets, picks, prior editing History are not included in XMP when written. Keywords etc, and then-current Develop adjustments, are included when written. Derived files such as pano merges and external edits to Photoshop, are by default created into the same folder as the Raw / other source file or files on which they were based. So provided it's the same folder of Raws that your previous Lr catalog was referring to, those files should normally be found intermixed.
... View more
Sep 27, 2020
01:10 AM
correction: recent sources at LEFT end of the filmstrip
... View more
Sep 25, 2020
09:13 AM
2 Likes
As advised, filter presets are great. You don;t have to return to Library grid view, nor have the Filter bar open, in order to use them thereafter. So for example, you can be in Develop with the contents of a particular folder or collection showing in the Filmstrip. Then you decide you want to filter that in some frequently used way, that you have previously recorded as a filter preset. Pick this preset off the right hand end of the Filmstrip and the number of images shown reduces accordingly. Include making a preset which cancels all filters, or use key shortcut Ctrl+L / Cmd+L and you can return to showing the whole Folder / Collection again. In your recent sources at right end of the Filmstrip, are the last few folders or collections you have visited. You can switch to one of those, right inside Develop (or wherever), and then decide how you want to filter that. There's a padlock icon on the Filter bar in Library which controls LrC behaviour with filtering. When locked, any filters you have got applied to the folder or collection you are viewing, will persist the same when switching to a different folder or collection. When unlocked, that different folder or collection view will appear however it was last seen / as default, if this is the first time you've ever viewed it. So each view is then remembering, and returning to, its own particular filtering.
... View more
Sep 24, 2020
06:29 AM
The setting for treating JPGs imported alongside Raws as separate images, is in Lightroom preferences - General tab as screenshot below.
... View more
Sep 11, 2020
03:48 AM
Making edits to images within Lightroom Classic, is the same thing as updating your Catalog: change is instantly written to the database on disk. Hence no Save Changes action is needed when you close the application, and it picks up again where it was, when you restart it. Also since all individual images within a Catalog remain constantly available for futher editing: no Open, Save Changes nor Close action is needed for those. There is a command (Ctrl+S / Cmd+S shortcut) which may look a bit like saving changes in the usual sense. In fact this is writing a duplicate of latest edit metadata, out to the file system. Also this can be made to happen automatically after each edit change. But as described above, the Catalog itself always remembers everything anyway. Lightroom Classic workflow depends only on that, plus the original file that you imported.
... View more
Sep 08, 2020
01:01 AM
Sure: once you have located the Raw based profile in the Adobe as-installed profiles area - for Windows, that is under "C:\ProgramData\Adobe\CameraRaw\LensProfiles\1.0" - that can be opened into a text editor. Looking down the profile data you will come to a line stCamera:CameraRawProfile="True" and by changing "True" to "False" the whole profile will hereafter support that different class of image. This same statement may repeat further times below, but editing just that first instance seems to be enough. Non-Raw profile support includes TIFF as well as JPG, but these corrections will only be suitable for un-cropped, un-corrected bitmap data - since Raw image data would have been unmodified in those ways. The edited profile then needs to be saved - I would append "non-Raw" to the filename - into the user profiles area: for Windows, that is "C:\Users\[username]\AppData\Roaming\Adobe\CameraRaw\LensProfiles\1.0". It should not be saved (nor overwritten) into the as-installed profiles area, since that wouldn't get recognised by LRc. The user profiles area is only re-checked when LRc next starts up, and from that point on this lens profile becomes available. If not auto-recognised, it can get added as a user lens assignment in the same way as for a Raw-correcting lens profile.
... View more
Sep 02, 2020
12:42 AM
Whether export sizing will actually be constrained to reflect the use of a smart preview, depends both on the availability of the original, and on whether "Don't Enlarge" is checked in the Image Sizing settings for the export. Whenever the original is not available but a smart preview is, a warning message notifies you that only that limited quantity of picture information will be used towards export processing. You can still select whatever export pixel dimensions you choose, and (if "Don't Enlarge" is turned off) LR is just as ready to upsample, as it more typically would be to downsample. The available source / the output settings are two independent upper limits, on the picture detail within the output.
... View more
Aug 30, 2020
05:00 PM
I find the balancing of global and local simply works well. Employing two 'yin-yang' masks as you describe, what happens when you later want to alter their common boundary? Very hard to re-achieve that perfect "seam" line without any gaps or overlaps. You'd probably have to modify one mask, and then delete and re-make the other one. The global / local method avoids this altogether. It's also relevant that local and global adjustments differ in their processing logic / sequence. The global adjustments modify the outcome of any local adjustment, not only areas that haven't had such. This should be made strategic use of. Personally I've come over time to heavily dislike the whole approach, and the results, of dividing an image up along strict boundaries like a patchwork - and then addressing its parts separately. However well and cleverly that's done, the tendency - perhaps the intent - is always to address whatever's supposedly unsuitable about each part. And thus the photo's natural overall coherence, its surprising distinctiveness, gets very soon "improved"... out of existence.
... View more
Aug 26, 2020
05:31 AM
Just to clarify, your files are locally stored and your Catalog is locally stored. Lightroom Classic does not depend on the cloud except for some optional functions, and for verifying your current subscription status each time you sign in or out.
... View more
Aug 26, 2020
05:25 AM
Quite often this happens because the local adjustments panel is collapsed down (compact). There's a little triangular icon to toggle that. In collapsed mode you can only see local adjustment presets, an Amount slider and a few brush controls, but not the full interface. Just below this you will still see the full Basic panel, which remains active, and it is easy to mistake those Basic (global) adjustment sliders, for the (local) adjustment sliders which you will see when the local panel is in its expanded mode.
... View more
Using the Community
Experience League
Terms of Use
Privacy Policy
Cookie preferences
AdChoices
Language:
AdChoices
Language:
- Deutsch
- English
- Español
- Français
- 日本語コミュニティ
- Português
Copyright © 2020 Adobe. All rights reserved.