richardplondon
Community Expert
richardplondon
Community Expert
Activity
‎Apr 04, 2025
06:19 AM
Thanks, it is good to narrow possibilities down. In this circumstance, is Photoshop still running at the moment when you try to move the file within LrC? Or, might you be curently viewing this file using any other kind of utility - for example when you are clicked to highlight a particular file in your OS file browser, and when the browser is displaying that as a preview, that file can be accordingly considered "in use" so far as the OS is concerned - and therefore unable to participate in other file operations.
Also, is there any actual difference of behaviour because of the image being black-and-white / colour, or is that just incidental?
... View more
‎Apr 03, 2025
01:21 AM
Say (for example) your workflow was to make a virtual copy from each colour photo, and then convert this virtual copy to black and white. So now you see (at least) two different treatments holding in common - sharing in - one source file.
It would be possible to move the colour photo (as a master copy) into a different folder, but it follows that the other photo version (its virtual copy) must move also.
A virtual copy has got no independent file or folder location of its own. So it is not possible to move just the virtual copy into a different folder.
If you want to use folders to manage your workflow, the common advice is to seek more virtual sorts of organisation instead (metadata based, within the Catalog) which do not require files to physically move around. These LrC methods carry fewer logical and practical constraints, compared with the traditional files-and-folders paradigm. The question of virtual copies being just one such.
... View more
Community Expert
in Lightroom Classic Discussions
‎Apr 02, 2025
01:48 AM
1 Upvote
‎Apr 02, 2025
01:48 AM
1 Upvote
There are several statements there, which I advise people to take cautiously and to verify for themselves. At least in my software (UK localised) there is no "All Pictures" option presented, there is only an "All Photographs" option (which is definitely a - special, built-in - Collection and not a Folder). By definition All Photographs does begin with ALL images present in the Catalog including virtual copies, regardless of where their source files live, though can be filtered to show only a subset of those. It is true that by default images may be imported from / into a user folder named "Pictures" or "My Pictures" or some such - but images may also live elsewhere. In fact I feel it is better that they should live elsewhere than the user's 'Pictures' location.
Also in my experience current selections do not cancel when switching to a different view (collection based, or folder based). While in a view where not all the currently highlighted images are presented, naturally some of those will therefore not be visible - but can remain selected even so.
... View more
‎Apr 01, 2025
02:08 AM
The low-frequency detail comes from Marilyn, not from Albert!
... View more
‎Mar 31, 2025
07:32 AM
exactly so: I intended "large scale" features to convey essentially the same thing as "low frequency" features -
which reminds me of this famous artifically created image (not my copyright, linked for study only):
... View more
‎Mar 31, 2025
01:10 AM
One possibility is Stacking: if some images are currently invisible within the Collection (because collapsed out of view) the Filmstrip reports it is showing (say) "22 of 27 photos". Ctrl+A will duly highlight those 22 in this circumstance, not all 27.
Another possibility is that your collection is filtered in some way so that not all photos currently show up there. For this reason also, the Filmstrip will report that it is currently displaying only "XXXX of YYYY" photos.
And all the same applies for what you see when looking at the "All Photographs" collection.
... View more
‎Mar 31, 2025
12:32 AM
Absolutely I find Texture addresses larger scaled features within the image than Sharpening does. And Clarity even more so.
Perhaps it is better to talk of the scale of feature that each of these tools "concentrates on". There is no adjustment in Lightroom which completely avoids affecting the image in the ways that other adjustments notionally target. Pretty much everything overlaps in function. Editing Shadows tonality does not have zero effect on midtones - but it does concentrate on those shadows far more than it does on midtones, and has no perceptible effect on highlights. Editing Exposure affects general tonality and that means the midtones strongly, but also shadow and highlight areas. And our editing solution is something of an experimental mix, as a result.
... View more
‎Mar 24, 2025
07:11 AM
I'll express that more simply: in my experience best convenience / clarity / intentionality comes by deciding clearly up front what format is being 'shot for' in the session - camera JPG, or camera Raw.
That's just one more in a whole sequence of committed decisions we already accept. Yes we may later wish we had set the other format: but we then must also wish to have made the slightly different exposure judgements appropriate to this. It's no different in principle than later regretting one's choice of camera to bring, or lens to mount, or the shot's framing, timing... you get the point.
All the camera settings appropriate for the usage of either form of 'digital film' - Raw or JPG - can typically be set up, road tested, and then switched between using camera custom setting presets.
One then does not need to remember to manually turn DRO off and on - not if clicking a custom preset dial from (say) setting C1 to setting C2 will include this step repeatably. It is a convenient way to switch your camera FROM its 'sometimes' role as a JPG capturing device, TO its 'othertimes' role as a Raw capturing device.
... View more
‎Mar 20, 2025
12:11 AM
It is inevitable that wide-angle photographs (taken towards the shorter end of this zoom range) will show increasingly "unnatural looking" towards the edges and corners. This is by and large a viewing problem. The original scene looks natural to us (from a certain viewpoint) and if an (undistorted) photo of the scene was instead held up in front of us at the right distance from our eye for however large that photograph was, that photograph would look essentially the same as the real scene does. This hypothetical photo, in this special circumstance, "mapping on to" - lining up with - what we otherwise see when the photo is not sitting in the way..
The unnatural look of a wideangle photo happens in a circumstance where a photo of the scene is being viewed either further away, or smaller, than that. A fully corrected, undistorted - in the sense of "rectilinear" - wideangle photo can look like a completely natural representation of the scene, but with a typical display - or print size - it is hard to get the eye close enough and still focus on the image. But one can get some idea.
If one imagines scaling this viewing circumstance up - with the image printed ten feet wide, and viewed from a more comfortable distance - one can better imagine how the photo is genuinely "mapping onto" one's real-life view of the scene. But only when seen at that distance, from that viewpoint.
The same effect is present in ALL viewing of photos, captured with all kinds of lenses - but much less noticeable when BOTH a moderate focal length has been used AND a moderate viewing size and distance are being used. That is part of the reason we would consider a given focal length to be 'moderate'.
There are various aesthetic and compositional tricks to make this 'wideangle effect' less pictorially objectionable - there is also a converse 'telephoto effect' for long focal lengths. We are more used to seeing the latter and tend to mind it less. Or there are other tactics still - such as deliberately NOT going for a perfect rectilinear projection, but rather accepting a somewhat "fisheye" one. But since a rectilinear expectation has been built into the lens design - unless that lens is explicitly a "fisheye" one - trying to do this in software is a bit of a forced compromise, with some downsides. To play, one can try the Manual tab in Lens Corrections where there is a "distortion" slider - in sample below, I also disabled "constrain to crop" and used the Scaling in Transform panel to expose better what is being done to the image.
This photo was taken at 12mm on an APS-C sensor, the same as roughly 18mm on your camera. Unlike the rectilinear version, it cannot be viewed from any distance that would map onto one's natural view of the scene - when shown as a flat surface.
But one can imagine printing it onto a curved surface instead, which then could map OK with the scene as seen (grin) - but with viewing distance then becoming even more critical of course.
... View more
‎Mar 19, 2025
11:19 AM
just to add, when you create a LrC Catalog backup (on exiting the program) this includes only the Catalog database itself: a specially packaged, cleanly closed copy of that. Recommended: to a physically separate destination that will not also get swept up, in whatever disaster may afflict your working setup.
Conventional backup and later restoring is appropriate (and recommended, to separate destination) for the imported images. Unlike the Catalog and its accompanying stuff, these are just 'normal files and folders'.
After Something Bad has Happened, on opening a restored Catalog backup into your new setup - which just means extracting a copy of that from its ZIP and putting it where you want - it will arrive with no previews etc initially. Those folders will get made, and progressively re-populated, as you then proceed. You may need to (bulk) re-link the images if the addressing of those has changed meanwhile.
Images that previously relied on AI-generated masking of (say) Subject or Sky will have since lost that info, so that will now need to get re-generated and again saved, before the masking will again display as before.
... View more
‎Mar 17, 2025
04:03 AM
I have had "automatically toggle overlay" option turned off, but LrC is OK for me - behaving apparently as-designed, that is to say - on version 14.2. I can't help you on anything MacOS related though.
... View more
‎Mar 16, 2025
05:04 PM
Is your GPU driver as up-to-date as it can be?
Overlay is behaving itself OK for me (on Windows) - (as a longshot) maybe experiment with overlay settings as below?
... View more
‎Mar 16, 2025
07:35 AM
A few questions just to narrow down the issue a bit:
a) Did you shoot originally in Raw or in JPG?
b) Have these 3 photos "with different adjustments" been differently edited in the computer, or have they originally been shot as separate exposures using differing 'real' exposure settings (say, 3 different shutter speeds when all the other exposure settings are kept constant)?
c) When you say "Photoshop merges this into ugly colours" are you in fact using Photoshop to do the HDR merge, or are you using the built-in function of Lightroom Classic?
... View more
‎Mar 12, 2025
08:15 AM
Just to check - could the setting for the print cell (within the page setup) be at fault here? There is a checkbox option to set or disable 'Autorotate' for how an image inserts itself into a given cell. You then may see an option for Zoom to Fill instead of Zoom to Fit depending on the template used, but that happens subsequent to the Autorotate option.
... View more
‎Mar 12, 2025
12:28 AM
For future syncing, you can set (and change) the storage location in LR Classic Preferences, Lightroom Sync tab, Location section (in my own case, D is a second drive within the computer):
So far as the images already synced, I have no practical experience with changing storage locations of those myself. Lightroom and LR Classic are not the same in a number of ways, and spreading the same images across both systems seems to me like a bad idea or at least some cause for frustration. For example in LR Classic one may have used folders to some extent in one's organisation, and that will not apply in Lightroom. Worse, one may apply keywording in one or the other context - and that does not then seamlessly transfer between. Things should of course be seamless between the desktop app of Lightroom, and the web app of Lightroom, which are two faces of the same system.
... View more
Community Expert
in Lightroom Classic Discussions
‎Feb 25, 2025
06:10 AM
1 Upvote
‎Feb 25, 2025
06:10 AM
1 Upvote
The editing History of the image begins with the first image state seen after import completes. By default, Before view will show you this as-imported image state (though Before can be set to show you some different image state instead). Anything applied during import (however that is done) was self-evidently not applied after import. Only edit steps carried out after import show as successive (recallable) image states, and the Catalog can do this only because those edits happened 'on its watch'.
All that said, one can see just the current default processing for a given image (the same as if a particular preset had not been chosen to additionally apply during import) by using Reset. The image remembers its edited state and provided this is your next action you can return straight to that using the History panel.
Alternatively you can make a Virtual Copy of the edited image, Reset all processing on the Virtual Copy, then compare and contrast these two versions side by side.
... View more
‎Feb 24, 2025
06:07 AM
I have for years retained my photos in full colour mode, even when receiving a B&W treatment. I just desaturate all the photo's hues (HSL) with a preset. HSL luminance sliders now serve the same purpose as the B&W mode's 'mixer', but I also still have all the other hue related controls to call on.
... View more
‎Feb 24, 2025
05:36 AM
Most advice you will see concerning ensuring camera profile is the same (as well as that all the adjustment sliders etc are the same) presumes that this is a Raw conversion profile specific to the camera involved.
AFAIK it is not a thing to use such a profile - a camera calibration one - at partial percentage.
But another kind of choice would be an "effect" profile which modifies RGB starting data towards a certain different look. That profile may often be LUT based. In such a case a variable strength will be logical, say right down to 0% strength - which would mean superimposing no such RGB modification at all - or conversely increasing that even past 100%.
That does presume a valid RGB input for the modification though. And if your starting point is sensor Raw, not converted RGB then some sort of (default profiled?) Raw conversion must have also happened along the way. And perhaps this aspect is what is varying behind the scenes? (because of... reasons).
If so that must give varying results - even when post-applied modifications are themselves identical.
... View more
‎Feb 24, 2025
12:01 AM
yes, Sync only appears when you have more than one image selected - because otherwise it will have nothing to do. Sync is a close equivalent for Copy and Paste and uses the exact same working sequence. Sync is a verb.
AutoSync is only available to turn on when more than one image is selected - but is a completely different method than Sync and uses a different working sequence. It then stays active - regardless whether one image or many images are selected - until turned off. When only one image is selected it does nothing; but the moment more images are selected, each new edit that you carry out automatically applies in BULK onto all of those immediately. AutoSync being on, or off, are two different working modes.
... View more
Community Expert
in Lightroom Classic Discussions
‎Feb 22, 2025
03:53 PM
1 Upvote
‎Feb 22, 2025
03:53 PM
1 Upvote
There is another option. A particular edit action can be directly batch applied onto multiple chosen images, all in one go. This includes when an edit is localised - it should apply 'in the same place' on all the photos, though funny things may happen if some images are portrait and others landscape.
It is (1) a good idea to get familiar with this feature on just a couple of sample images first, also (2) to be very conscious it would be easy to apply lots of unintended edits onto other images that were also highlighted, if one forgot - therefore, it's a good idea to promptly switch this off when not particularly needed.
At bottom of the Develop right side panels are Sync and Reset. There's a little switch next to Sync. Clicking that puts the Develop module into AutoSync mode. This uses a completely different working order and logic than Copy - Paste; or, than Sync (which amounts to the same thing as Copy - Paste IMO).
AutoSync sequence is: activate the mode before making a particular change to active image; this plus all other images currently highlighted receive that specific change (only) instantly,;make your next change; same thing happens instantly, and so on for as long as AutoSync stays active. The only change received by other highlighted images will have been the particular action(s) you did with AutoSync active - all the rest of their processing is left alone.
Copy-Paste (or, very similar, Sync) sequence is: after making desired changes to one image, replicate some or all of its latest processing onto other images as well.
... View more
‎Feb 21, 2025
06:40 AM
It is certain that the virtual copy concerned, and the master copy concerned, are both referring to the exact same file? If so, it should be possible to exchange which one has master version status, and which one has VC status (set copy as master). This switch over should make no difference whatever.
Besides checking that the usual Basic Panel adjustments and underlying profile are the same, also that local corrections are not in place, it may also be worth checking for the same Process Version; also checking if anything's active in the less commonly used adjustment panels such as Grading and Tone Curve.
Can you explain what you meant by "42", for the profile you are having trouble with?
... View more
Community Expert
in Lightroom Classic Discussions
‎Feb 20, 2025
01:24 AM
1 Upvote
‎Feb 20, 2025
01:24 AM
1 Upvote
Just to offer my own experience:
there are many different profiles available (for example, some that mimic various image modes available in a particular camera's menu, primarily to change what the camera JPG looks like). But when you are varying the profile used for processing a Raw, or if this profile is varying what it does, it will take longer and be more complicated to learn what all the Develop adjustments do - to develop your own editing strategies, and understanding. The same is true for relying on Develop presets to achieve different looks: your attention will then be on learning those, but what they are actually doing is maybe mysterious.
What worked for me while learning LrC was to stick with a quite "flat" camera profile - also some fairly neutral and conservative default settings for sharpening and such - and then to explore the myriad pictorial looks possible from there. One then actively makes happen whatever 'enhancement' one wants, rather than reacting passively to different pre-made options. A rapid way to learn. Incidentally one is less likely to fall into formulaic 'recipes': which is more rewarding IMO.
It may seem like more work to carry out, but not really - noting that there is no right or wrong about any of this. If an adaptive profile together with pre-made presets can largely achieve the job at hand, there may be less urgency to learn all the manual adjustments deeply.
... View more
‎Feb 19, 2025
03:17 AM
important to note that this is not really "splitting" the current Catalog, unless / until you've also removed the relevant images from that.
Exporting as Catalog has copied those, not moved those, in other words.
... View more
Community Expert
in Lightroom Classic Discussions
‎Feb 18, 2025
10:28 AM
1 Upvote
‎Feb 18, 2025
10:28 AM
1 Upvote
open the Basic panel, you should see this menu at its top left - in this example photo it is currently processed using a legacy profile but could be changed to one of the Adaptive options instead. Because choice of underlying profile is fundamental, changing between profiles can mean needing to re-consider any and all adjustments done, in the light of the different picture appearance which these will now be resulting in.
... View more
‎Feb 18, 2025
10:18 AM
You can make a new Catalog that contains only those selected photos. This new Catalog can live wherever you want. The photos will still be seen in the current Catalog too - unless you remove them from that.
The underlying source files (camera Raw, camera JPG, Photoshop edited files etc) that are referenced by this new Catalog can either be the same ones in the same locations that the current Catalog is referencing - so that both would share in using these - or else you can instruct copies of just the relevant files to be made alongside this new Catalog, and those would be the ones it would then reference. Again, whether you instruct this or not, the starting files and folders would all still remain in place regardless - unless and until you deleted those from disk.
In other words you can either selectively and partially copy your Catalog to another disk, or else you can do that and at the same time copy all the relevant source files for the photos involved.
This function is called "Export as Catalog".
... View more
Community Expert
in Lightroom Classic Discussions
‎Feb 16, 2025
08:35 AM
1 Upvote
‎Feb 16, 2025
08:35 AM
1 Upvote
When you "Export as Catalog" you choose a location and name for this new Catalog. Whether relevant files are to be copied here too, or not, is controlled by a checkmark option "Export negative files".
IF checked, a set of subfolders is created alongside the new Catalog, corresponding to the relative arrangement of subfolders seen in the current catalog - and populated with copies of the image files concerned. The new Catalog references these copy files and copy folders. The current Catalog continues to reference all the originals as before.
So the files have been duplicated - with the copies separated out systematically, but the originals still intermixed. Thus, cleaning these images out from the current Catalog - using the same highlighted set that you used for the Export - can include a deletion from disk as well as a removal from the Catalog, and then there is no more duplication.
OR if not checked, the new catalog references (the same) files in the same current folders where the current catalog continues to see them - in other words, both the catalogs share these same files and folders. So in this case one's deletion of the relevant images from the current catalog needs to use the Remove from Catalog option only. For, I hope, obvious reasons.
[FYI: when exporting (say) contents of a single Collection, all of which have been highlighted, the first checkbox may not appear. But when it does, if this is left unchecked, all of the images in the catalog will get included regardless of highlighting or not. So these options are important to verify.]
Also - whenever considering removing images from any Catalog, I would advise ensuring an up to date Catalog backup first. The Export as Catalog process is itself non-destructive so far as the current Catalog and the current locations of all the image files - whether copying files or not - but the cleanup of the current Catalog afterwards does need to involve a lot more care.
... View more
Community Expert
in Lightroom Classic Discussions
‎Feb 15, 2025
03:55 AM
1 Upvote
‎Feb 15, 2025
03:55 AM
1 Upvote
Sometimes the adjustment / tool you have active is itself using the arrow keys.
Crop is one example. Whenever the crop boundary has got room to move, you can scroll the image in various directions "underneath" this boundary.
The Ctrl key informs LrC when you want to switch to another image, and not move the current image's crop.
... View more
Community Expert
in Lightroom Classic Discussions
‎Feb 14, 2025
07:11 AM
1 Upvote
‎Feb 14, 2025
07:11 AM
1 Upvote
A Lightroom truly 'Pro' offering would IMO allow multi-user use at extra cost - not trim anything off (which costs no more to include, but may cost more overall to leave out). Multi user is nontrivial (understatement) to implement when it comes to a local Catalog. That is AFAIK built off a database engine (SQLite) which is not capable of concurrent changes.
So I would agree: the opportunity for offering different product levels and pricepoints may be there for Lightroom (cloud centric), but not for Lightroom Classic (local centric).
... View more
‎Feb 14, 2025
03:11 AM
Maybe try avoiding this character (#) and see if that makes a difference? It does sit within that grey area between universally OK, and problematic. I would not say the same thing about the accented characters themselves: these are normal and well tested AFAIK.
[Uninformed speculation]: if that (#) character had raised some error while interpreting these image paths, perhaps LrC could be reverting to just a basic character set for safety - and that tighter interpretation might reject any expanded Unicode characters found.
... View more
‎Feb 14, 2025
02:51 AM
There is a moderation process needed I believe, before an issue will appear formally as a Bug - including checks on reproducibility, and on whether enough technical info has been given. So you may get some follow-up questions first.
... View more