Skip to content

Apple Universe

Top-level category for all Apple, Mac, and OS X related topics.

Fix a broken search in Photos

I was having some issues with my desktop photos (which I load from Photos) not working properly, and I noticed that one particular photo wouldn't preview in the Wallpaper System Settings panel. I noted the name, searched for it in Photos, and came up with no matches. Then I tried other searches, for photos I knew were there as I could see them onscreen, and still, no matches. Clearly Photos' search was broken.

I tried the (long, slow, painful) photo library rebuild process, but still, no search.

After much digging, I found a solution that works, which is to force Photos to rebuild its search database. Here's how to do that:

  1. Make sure you have good backup of Photos before you start, just in case.
  2. Also make sure you quit Photos before proceeding.
  3. In Finder, navigate to your Photos.library file and right-click on it. Select Show Package Contents from the pop-up menu.
  4. In the new window that opens, open the database folder. Inside of that folder is a search folder. Delete it, but leave the database folder open.

That's it, you're (almost) done. Now launch Photos, and it will start rebuilding the search database. This can take a while, depending on the size of your database—it took about five or so minutes for my 65,000ish image collection. There's also no onscreen indication that anything is happening, so use Finder: Open the newly-created search folder in Finder, and check the size of the psi.sqlite file. When the size stops changing, the rebuild is done.

I found this answer in a post by Michelle Lyons in this Apple Discussiosn thread. Michelle notes they found the answer elsewhere, but don't link to that source, so I don't know who originally discovered this. All I know is it worked for me!



Undocumented find: A great Mac-compatible flightstick

The VelocityOne Flightsticktl;dr version: I highly recommend the Turtle Beach VelocityOne Flightstick (right) for use with X-Plane on the Mac. Despite not being advertised as Mac-compatible, it works incredibly well, and at only $129 on Amazon, is a very good deal.

There are tons of buttons, three separate analog axes, a mouse and display built into the top of the stick, LED lighting (which you can also disable), and much more. Keep reading for a lot more detail, but if you're looking for a good Mac-compatible Flightstick, I'm over a year into my VelocityOne, and haven't had any issues yet.

I recently built myself a new gaming PC—Frankenmac was nearly seven years old, and was incapable of running the games I wanted to play with any sort of decent framerates. I won't bore you with the details of the build, but the perforance jump from an Nvidia 1080 to Nvidia 4080 graphics card was very impressive!

My main gaming outlet—on both my Mac and my PC—is flight simulation. On the Mac (or PC), it's X-Plane, plus Microsoft's Flight Simulator on the PC. As I don't have a lot of spare desk space, or the desire to spend a ton of money on flight peripherals, I control the simulators with a flightstick1A joystick with features specific to flight sims, such as a yaw axis..

[continue reading…]



I despise this icon

That ugly garish purple travesty shows up in the menu bar whenever your screen is being recorded by any number of apps. From Apple's perspective, they probably consider it a good thing, as it lets a user know their screen is being recorded, and I understand that logic.

But it also shows up when you record your own screen via an app such as ScreenFlow. I find it incredibly intrusive, and there's no option for a user to say "Yes, Apple, I know my screen is being recorded—because I myself started the recording!—please disable that ugly purple icon in my menu bar."

Left in place, the purple icon screams for attention any time it's onscreen, regardless of what you're trying to show in your screen recording. It's unlike every other item in the menu bar, and at least for me, my eye is constantly drawn to it.

So please, Apple, let the user disable that menu bar icon. A logical way to do this would be to show a "Disable this one occurrence" menu item when the menu bar icon is clicked. That way, it's not a blanket override, but you could easily banish it for a given recording.

Until that happens, however, we (all two of us) here at Many Tricks so dislike the icon that we've implemented a workaround, but it's not ideal.

[continue reading…]



Remove the AI bloatware from Logitech’s mouse driver

Note: Newer versions of LogiOptions+ have an on/off switch built into the app; find it in the app's Gear icon. The following is left as a historical footnote in the annals of the societal takeover by AI.

I absolutely love Logitech's Mac MX Keys keyboard and MX Master mouse (though I've now updated to version 3 of the mouse). And generally, their software has been pretty good, too.

But a recent update added an "AI Prompt generator" feature to the mouse side of things, which is absolute garbage—I'm not saying it's bad, as I've never tried it. It's garbage as in there's no reason my mouse needs an AI prompt generator connected to a button. Even worse, as Stephen Hackett discovered, it creates a folder (at the top level of your home folder, no less!) with the ugly name of ai_overlay_tmp.

Thankfully, when Stephen posted about this on Mastodon, user @flipneus posted the solution. And in case that post ever goes away, here it is:

In Finder, open the top-level Library → Application Support folder, then navigate to Logitech → LogiOptionsPlus, and open app_permission.json in your favorite pure text editor. Add a comma after the last } on the line before the final }, then add these lines:

 "aipromptbuilder": {
  "value": false
 }
}

When done, the end of the file should look like this (though the commands in yours may differ):

...
  },
 "backlight": {
  "value": true
 },
 "aipromptbuilder": {
  "value": false
 }
}

The important part is the added comma after (in my file) the backlight-related section. Save the file when done editing, and reboot.

After the reboot, you can delete the ai_overlay_tmp folder—and there won't be an AI generator option in the Logi Options+ app any more. (Alternatively, Stephen points out you can use SteerMouse to program the buttons on the Logitech.)

Thank you, Stephen and @flipneus!



A simple AppleScript to reveal System Settings’ anchors

I stumbled upon this simple AppleScript while looking for something else, but it's incredibly useful for scripting System Settings…so I'm posting it here in case the original site ever goes away.

To get the names of all the anchors for a selected pane in System Settings, just run this in Script Editor:

Run that on the Desktop pane, for instance, and the output is this:

{anchor "Dock" of pane id "com.apple.Desktop-Settings.extension" of application "System Settings", anchor "HotCorners" of pane id "com.apple.Desktop-Settings.extension" of application "System Settings", anchor "MenuBar" of pane id "com.apple.Desktop-Settings.extension" of application "System Settings", anchor "MissionControl" of pane id "com.apple.Desktop-Settings.extension" of application "System Settings", anchor "Shortcuts" of pane id "com.apple.Desktop-Settings.extension" of application "System Settings", anchor "StageManager" of pane id "com.apple.Desktop-Settings.extension" of application "System Settings", anchor "WindowsApps" of pane id "com.apple.Desktop-Settings.extension" of application "System Settings"}

With that information, you can jump directly to a given area in AppleScript with code like this:

I'd always wondered how people found the anchor names, and now I know.



The macOS’ version of the cp Unix command won’t create links

 
Update: Apple fixed this in macOS 14.4; the cp command can once again create hard links.

I ran into this while working on a Keyboard Maestro macro that creates hard links: The macOS version of cp won't create links, at least not in Sonoma. In Ventura, it works even though it throws the same error as it does in Sonoma.

Copying as hard links is part of the cp feature set, fully covered in its man pages. But it doesn't work in macOS. To confirm, try this:

When I ran into this, I searched and discovered that someone else had run into the same issue,1Apple Developer login required but that's the only mention I could find.

I have filed this bug as FB13255408 with Apple, and I'm hopeful they fix it soon. There is a workaround, obviously: Use ln instead. This works fine for individual hard links, but using cp to quickly copy an entire folder as hard links is a nicer implementation.



More helpful help for Terminal commands

I use Terminal a fair bit, for any number of things. But I don't use it all the time, and that means I sometimes struggle to remember syntax of commands. "Was it rsync source destination or the other way around? Or was it ln that was backwards of what I thought it should be?"

You can open the man page for a command, of course, but sometimes there's so much there that finding the simple thing you want is tough. Enter tldr, installable via Homebrew or MacPorts. tldr skips most of the detail of the man pages, providing user-curated examples of how to use a given command.

As an example, here's the aforementioned rysnc command's man page:

[continue reading…]



Replace the mini music player that Apple took away

Back in the early Mac OS X iTunes era, there was a wonderful small window available that had control buttons, volume control, a visual progress bar, and a text display showing the artist, song, and album—it could even display a graphic equalizer in lieu of the artist-album-song info:

It was perfect. Sadly, it was last seen in iTunes 10 in Mac OS X 10.7. And today's version, while offering a mini mode, isn't nearly as mini or as functional as it used to be; read on for some details…

tldr summary: Mario Guzman's Music MiniPlayer is a full-retro near-perfect replacement for the original mini player. It's free, and I love it. If you're not into retro UI, Silicio on the App Store is also free and quite good, though you can't freely resize the window.

[continue reading…]



Speedier screen sharing startup in Sonoma

macOS Sonoma introduces a revised Screen Sharing application that lives in the Applications → Utilities folder1Though that's not really where it is, but that's not important…. It presents a list of recently-connected devices:

Select one, and you'll see the username and password dialog for that machine. While the GUI is nice to have, it's also slower than the old method: In Ventura and earlier, you could launch the (not in Utilities) Screen Sharing application, and start typing the IP address:

Select the host from the list, and you were done. This is much quicker than launching an app and waiting for the GUI, then navigating and selecting the desired machine. After just a bit of digging, I found a much quicker way to connect to my Macs in Sonoma (and earlier versions of macOS): The "vnc" URL scheme.

[continue reading…]



A quick iPhone 13 Pro vs iPhone 15 Pro photo comparison

I upgrade my phone every two or three years; I just moved from the 13 Pro to the 15 Pro, primarily for the new camera features. I'm not a pro photographer, nor even a prosumer photographer. I do like seeing how things have progressed, however.

So here are three photos shot with each phone, taken seconds apart, with each camera set to its highest resolution and HEIC-formatted photos. I then edited the photos only to improve their alignment, and reduce the sizes. See if you can guess which photo of each set was taken with which phone.

Indoors
Before imageAfter image

[continue reading…]