As of Sequoia's end when you duplicate an image in Photos you have the option to "Duplicate as Still Photo" thus omitting the live image video.
So duplicate and delete original to remove video portion.
Tech tips and notes with a bit of commentary. macOS and iOS mostly.
As of Sequoia's end when you duplicate an image in Photos you have the option to "Duplicate as Still Photo" thus omitting the live image video.
So duplicate and delete original to remove video portion.
Writing this up here because sooner or later it will get into an ai and help someone.
I was unable to set up an FEPBlue.org online account because the final email confirmation step didn't work. There's no recourse, you have to start over. Yes, "start over" is crap coding -- but web sites are getting worse.
I checked spam folder, etc. The email was not being sent.
I had used an email address that's part of a (legacy) Google Apps domain. I had a hunch so I repeated the process with an iCloud email. That worked.
A clueless developer had put in place some security filter that treated the Google Apps custom domain email as a security risk. Like I noted above, there's a lot of bad quality software now. All the talent has left for way better money. We really do need to turn this class of software work over to the AIs.
Anyway, if you find it doesn't work - use an email that's not a custom domain.
(Obviously there's no way to report a bug like this.)
Open the toner access door on your printer.• Press the Secure and Cancel buttons at the same time.• Use the arrow buttons to select the correct toner yield of the toner you are usingTNR-STR = Starter cartridgeTNR-STD = TN-820 standard yieldTNR-HC = TN-850 high yieldTNR-S.HC = TN-880 super high yield• After you have found your toner cartridge type, press OK• Press up arrow to Reset
I don't think it matters which cartridge you choose, that just determines what count is applied and any of them will exhaust your low toner. But it does allow continued printing while waiting for a replacement.
(The printer is end-of-life, it's had one drum replaced. I keep it because it's unlikely there's anything better today.)
My single greatest Photos.app frustration (I have many) is the inability to search the folder hierarchy. Mine contains hundreds semantically important folder names where the hierarchy is also meaningful. Meaning lost in the catastrophic Aperture to Photos migraiton.
This morning I had an hour free so I asked an ai about available utilities and workarounds. It said there are really no good options, but the Python osxphotos module might be able to traverse the folder hierarchy.
I have dabbled in minor Python coding and I have a half-baked Visual Studio Code environment. So I asked Claude 4.5 in Perplexity (this is not a formal supported coding environment) to write me a script that would use osxphotos to build a text file representation of the hierarchy. I ran whatever it generated.
It took 4-5 tries. I never edited the code myself. The first time there were copious errors, I describe errors and requested a redo. The next two times there were fewer errors, but I only got the top level of the hierarchy. The ai added debug code. It took two more tries of running and reporting errors to get a script that generated the text file I wanted (example):
[Teams and Orgs / MN Special Hockey / MNSH 2006 pre-season] MNSpecialHockey_060317
[Teams and Orgs / MN Special Hockey / MNSH 2022-2023] MSH 2023 Printed
[Teams and Orgs / MN Special Hockey / MNSH Woodbury 2019-2020] MSH Portraits Jan 2020
[Teams and Orgs / MN Special Hockey / MNSH 2008-2009] Nov 2008 MN SH Section 108 Event
[Teams and Orgs / MN Special Hockey / MNSH 2021-2022] Portraits MNSH Woodbury 2022
This is most personally valuable code I have ever "produced" since my days of writing the "medtrans" C program to turn 1990s MEDLINE output into tab delimited importable text.
And I wrote none of it.
I'll be cleaning it up and refining it, but below is the code I have today. It also included album names within a containing folder - I didn't want that but now I find it useful so I'll leave it.
Code
I like to wait a month (iOS) or six months (macOS) before applying major updates. By the time I apply them all the useful tips and tricks I read along the way are ancient history.
Instead of trying to keep track of these things before the OS is installed wait until you are ready to pull the trigger. Then ask your ($20/m) ai to summarize known issues and interesting new features, tips and tricks. You can provide context as needed (ex: I am an expert user, etc).
PS. Apple got away from providing PDF versions of manuals and user guides -- but if they still did that I'd drop the PDFs into my Perplexity macOS Space.