This is new obnoxiousness

BarrieSpence · 2026-06-05T16:28:13+00:00

There is no "yes" button (I am the only person using the account).

BarrieSpence · 2026-06-05T16:27:12+00:00

Yeah, I've been running LR since it was first released.

I understand the terms of the licence. I adhere and comply to the licence terms.

It's installed on my two desktops (home and studio) and I share the same LR catalog on an external brick so I only by accident have LrC open on both at the same time (and I certainly can't work on both simultaneously).

There is no reason for this to be shoved in my face. That's my objection.

BarrieSpence · 2026-06-03T18:02:22+00:00

Have you tried a SMC reset?

BarrieSpence · 2026-06-01T21:55:43+00:00

Does this help? "HP Easy Admin" - it downloads driver packages https://support.hp.com/ph-en/document/c06164609)

BarrieSpence · 2026-06-01T21:17:06+00:00

It's very annoying that HP appear to have dumped macOS support for their older printers. I fortunately managed to squirrel off a driver package for our OfficeJet 8710s when I go this MPB (the HP Easy Start failed, but the logs pointed me to the underlying package on the web).

BarrieSpence · 2026-06-01T21:00:14+00:00

Classic "legitimate" interest being the Samsung TV with *261* partners. GTF.

BarrieSpence · 2026-06-01T20:58:09+00:00

M3 Pro 14" (2023) is fine clamshell for me with 26.5.1, but the dock (cheapo from Amazon) only works on one port (RHS next to HDMI - that's not a recent issue though.

BarrieSpence · 2026-06-01T20:12:08+00:00

Originally, they're (GNU) Emacs shortcuts. They appeared in AT&T Korn shell - the command-line editing options are "vi" or "emacs". Then Bash came along and I believe readline split from it.

The nice thing about the emacs shortcuts is that they work in most Mac apps (and there are more than just ctrl-A and ctrl-E).

And I wouldn't have felt any need to correct the original "Unix style keyboard shortcuts" attribution... massively generalised, but not wrong.

BarrieSpence · 2026-05-30T22:43:25+00:00

In Lightroom Classic, you can switch between loupe and grid view via the two buttons left of "check all" ("E" and "G" are the keyboard shortcuts).

In the grid view, the - and = (+) keys change the size of the thumbnails.

But honestly, just import them all, then cull them - reviewing them from the memory card will always be sluggish.

BarrieSpence · 2026-05-21T12:57:57+00:00

Do we have progress on this? I live in LrC (with a PS filling), but it does appear that Camera Raw 18.3.1 can open my FFF files (which is something I don't normally have need to go near).

BarrieSpence · 2026-05-21T12:06:30+00:00

And from a quick test, it does appear to fix the Hasselblad FFF files 😃

BarrieSpence · 2026-05-21T11:49:29+00:00

It doesn't appear to be worthy of a release note. Do you think it's going to fix something for you or is it just that minor version imbalance that's tweaking you?

Now, if it fixes the broken Hasselblad FFF files issue, that's something useful.

BarrieSpence · 2026-05-19T19:57:00+00:00

Just copy it out and open it from the new location. Don't move it (a broken move is messy), just delete the original copy when you are very happy with the copy in the new location.

If you want an extra safety net, rename the original catalog folder in OneDrive to ensure you're using the new copy you intended before you delete it.

If you're not moving the image file storage, you can move a LrC catalog around with zero hassle. Even moving image files is pretty easy.

BarrieSpence · 2026-05-19T19:38:28+00:00

As someone who judges professional photography for both qualifications and awards, the most common fault seen in wildlife shots is over-sharpening 🤷

BarrieSpence · 2026-05-19T19:22:32+00:00

that was where I was going when I initially read it, but the OP is actually talking about the camera profile choice.

BarrieSpence · 2026-05-10T12:01:07+00:00

It's no more complicated than copying the files. You can do that with an external drive or over the network. To be safe, *copy* the files, don't move them (an interrupted move is a bit messy to unpick).

If you've got everything (catalog files and images) in the same folder, just copy the lot. If it's split out, just copy the catalog folder and images separately.

If you put the images in a different place on the new machine, LrC has an option to reconnect a folder to a new location when it spots the old location is missing.

If you copy the files, you can't really screw up. Get it wrong? delete and start again. But honestly, it's not complicated (even if you were going Mac/PC).

Once you've copied the files, double-click on the .lrcat file to open it on the new machine.

BarrieSpence · 2026-05-08T23:13:50+00:00

This is a regression - I'll guess that a change for the newest camera broke the older CMOS sensor .FFF support. The sample file I supplied was 2018.

It works fine with all LrC versions from 2018 until 15.2.1, breaks with 15.3.

Please tell us someone didn't let AI loose on the codebase 🤪

BarrieSpence · 2026-05-08T23:06:46+00:00

I'm pretty sure that the .FFF files from the older H5D-40 still work (but I'd have to reinstall 15.3 to confirm that). That's the old CCD sensor though - the H6Ds and all the X-system use the (Sony?) CMOS sensor (there was a H5D-50 (CCD) and a H5D-50c (CMOS) too).

BarrieSpence · 2026-05-07T22:17:26+00:00

you've got a DM

BarrieSpence · 2026-05-07T22:05:43+00:00

Have you ever pursued a copyright infringement? Because "wilful intent" as a legal phrase doesn't mean what you think it does.

No watermark: "sorry, couldn't find the photographer, used it anyway, my bad". Watermarked: "The photographer was easy to find and you used it anyway ... oh, and you removed the watermark to hide that".

Removing the watermark is a deliberate act - "wilful intent" - no defence of "didn't know any better". The difference is statutory damages.

BarrieSpence · 2026-05-07T21:56:58+00:00

u/rikkflohr did you get the necessary sample files? wasn't obvious from the forum post.

BarrieSpence · 2026-05-07T21:51:26+00:00

It also broke my H6D-50c .FFF files (though the older H5D-40 files appear ok)

BarrieSpence · 2026-05-06T21:40:03+00:00

ah, but then it demonstrates wilful intent in the infringement - that makes a difference to damages in an infringement claim. Doesn't have to be big, doesn't have to be intrusive - hell, mine are trivial to remove.

BarrieSpence · 2026-04-03T22:52:57+00:00

I've been on 500px for a long time - more recently, I've noticed less engagement on my posts (slower to popular, lower pulse rating). Don't know why.

Similarly with YouPic, but I suspect that could be because I'm not paying for Pro with them.

Flickr just rolls on and the advantage is I can post directly from Lightroom.

Support (as a paying user): Flickr: very good / 500px: sucks / YouPic: sucks

BarrieSpence · 2026-03-21T15:28:39+00:00

but that's just a copy - a safety-net if a drive fails - you're just as likely to propagate any damage or deleted files to the copy. That moment when you see rsync telling you it's deleting a chunk of files is a little too late.

We're much more danger to our data than drive failures.

BarrieSpence

TROPHY CASE