2022 – Week 25

Web host had a major outage, but they seem to have fixed things.

Found out my local hardware suppliers have stainless steel tie wire, in the diameter I want to use, though not the grade (316). I should be able to use it to do some experiments for bending.

Finally got around to assembling the workshop stool I bought for welding, and used the air compressor to blast out an oil heater we brought back from storage.

2022 – Week 24

Another quiet week, of medical stuff, and a visit from a building inspector who seems to think the water issues with the roof are entirely from the air conditioner. Concluded the week with my web host messing something up, taking all my sites and email offline on a Sunday evening.

2022 – Week 23

Quiet week. MRI scan on Monday. Brought some wire and bits & pieces back from storage to try a proof of concept for a sculpture idea. Feels good to be actually making a thing.

I think I’ve narrowed down the wire I want to buy, such that I’m comfortable buying ~2.5km of it.

2022 – Week 22

Continuing to monitor the air conditioner, it seems to be stable, and not running anywhere near as much, or as hard as it was previously. Though, we haven’t heard back from the second aircon guy, so we’ll probably speak to a third party to get an independent assessment of the situation.

In other news, I updated my workstation setup, with another round of galvanised plumbing pipe construction.

This lifts the display, so my graphics tablet can slide all the way back to the wall, freeing up desk space. Local tile company was kind enough to give me the wall tile (because they don’t charge for singles) the display is sitting on. It’s all mounted with double-sided foam tape, which pads and secures it to the pipework.

2022 – Week 21

Wild weather again – this time, the house lights went out while sitting down to dinner. All the appliances kept running, so going upstairs to investigate the fusebox, I found the safety switch wouldn’t re-engage. Going into my room to check all my gear on the UPS, everything was fine, but coming out to stand in front of the fusebox again, I felt a drip on my head, as water began emerging from the smoke detector. It is wired into the lighting circuit, which is why the lights went out.

So now we have roofing guys, and electricians surveying the damage, and suggestions that chunks of the ceiling are going to have to be ripped up due to mould. The first roofing guy is said there’s no roof damage, and it’s purely due to the aircon puling condensation out of the air. Then we had another roof guy say there is roof damage, and parts of the roof weren’t sealed properly.

End Times never end.

2022 – Week 20

More rainpocalypse and broken sleep, but some good progress made on cleaning up storage.Slowly, and surely, it’s getting done. Things have arrived in the mail, videos from America, a fancy computer light, which isn’t suitable for the job, and will end up having to be returned, which was a shame.

2022 – Week 19

Major breakthrough this week – I solved a huge problem that’s bedevilled me with Capture One – figuring out how to manage window focus with multiple windows.

This lets me really use Capture One as a serious tool, so I spent a bunch of the week watching tutorials on LinkedIn. Thankfully the Qld State Library provides free accounts for LinkedIn Learning – it’s a huge social benefit.

Time Machine Duplication

To duplicate a Time Machine Drive, and Re-integrate it to the backup process:

  1. Switch off automatic backups.
  2. Copy the source drive using SuperDuper (the only utility that can properly clone a Time Machine volume) with the Backup All Files option.
  3. Wait hours or days for the copy to complete.
  4. Add the drive in the time machine  prefpane
  5. terminal
    1. Inherit the backup (do this by dragging the actual computer name folder from Finder into Terminal after typing the inheritbackup – the full path will then be populated):
      sudo tmutil inheritbackup /Volumes/(The Backup Drive)/Backups.backupdb/(The Computer's Name on the Backup Drive)
    2. Associate the Boot Drive (again, drag the boot disk’s entry in the latest backup entry of the duplicated Time Machine volume, from Finder, to the Terminal window, and it will populate the area in brackets – make sure you check the number and spacing of forward slashes):
      sudo tmutil associatedisk -a / /(the path to the the last backup of the boot drive on the backup drive)
    3. Associate each backed-up non-boot volume (dragging again from Finder to the Terminal window for both of these):
      sudo tmutil associatedisk -a /Volumes/(Non-Boot Disk) /(The path to the most recent backup of the Non-Boot Disk)
  6. Open a terminal window and start recording the TMUtil log output:
    1. log stream --style syslog --predicate 'senderImagePath contains[cd] "TimeMachine"' --info
  7. Run a Time Machine backup manually and watch the terminal log to make sure each part of the backup is being connected correctly. Look for Inheritance Scans and watch the sizes of the backups, to make sure it’s not doing complete fresh backups.

Special Note: holding down the Option key in Terminal, allows you to place the cursor insertion point wherever you click in the text.

If this helped you, maybe go buy one of my eBooks.

Fixing Capture One, with Keyboard Maestro.

Capture One is a RAW photo developer, editor and Digital Asset Manager app. It’s my current go-to as a long-term replacement for Apple’s long-discontinued Aperture.

In general, it has better image processing than Aperture, but falls down a bit on the DAM side of things. It can’t import directly from iOS devices, and doesn’t have export to iOS device integration through iTunes. It also lacks Aperture’s “Flag” option, which is super helpful for doing a first pass through a shoot, and flagging images as keep, or not, before filtering for flagged, and going on to subsequent passes for assigning star ratings.

The biggest problem from a fast workflow perspective, is in how it handles a multiple-display setup. You have your thumbnail Browser window open on one screen, and the image Viewer window open on another. When you click on a thumbnail, although the image is displayed in the Viewer, the application’s focus remains on the Browser. This means keyboard shortcuts to control the zoom level of the image are captured by the  Browser window, and not passed through to the Viewer. As can be seen in this video:

The workaround was to have to manually click on the Viewer window, to bring it into focus, then do the zoom keyboard shortcuts, and back and forth for every image.

This really defeats the purpose of shortcuts, which are designed to minimise unnecessary mouse movement.

I spent almost a year holding off committing to Capture One (after purchasing it) over this, before discovering Keyboard Maestro.

What Keyboard Maestro does is sit in the background, capture keystrokes, and use them to trigger various workflows & macros.

In this case, I configured it to listen for the keyboard shortcuts I had previously used in Capture One for the zoom-to-100%, & zoom-to-fit commands. I then configured it to generate two keystrokes in succession, in response to each of those original keyboard shortcuts.

  • The first, is the keyboard shortcut to make the Viewer the active window.
  • The second, is a reassigned shortcut for zoom-to-100% & zoom-to-fit respectively.
Use a Group to limit the macro’s scope to Capture One.
Set up the chain of keystrokes, triggered by the first.

So, the process now is:

Select a thumbnail, then:

  • Press the Key originally used to zoom to 100%.
    • Keyboard Maestro grabs the keystroke, and uses it as a trigger to fire off:
      • Keyboard Shortcut to make the Viewer window active, then
      • Reassigned Keyboard Shortcut to set the Viewer zoom to 100%.

Or:

  • Press the Key originally used to zoom to fit.
    • Keyboard Maestro grabs the keystroke, and uses it as a trigger to fire off:
      • Keyboard Shortcut to make the Viewer window active, then
      • Reassigned Keyboard Shortcut to set the Viewer zoom to fit.

The neat thing, is that using the shortcut to make the Viewer active while the Viewer is already active doesn’t seem to cause any problems, so there’s no need for conditional logic to test which window is currently active.

All in all, this is an elegant solution to a problem that seemed hopeless.

If this helped you, maybe go buy one of my eBooks.

2022 – Week 18

Slowly, and surely we’re making progress on tidying, and reorganising the storage setup. It’s a shocking insight into just how inefficient the use of space was previously, or perhaps how lacking in ambition and tetris-playing we were in organising it. But, things are progressing.