I like diving. And I like photography. So here we are! My computers run an open source operating system (OpenBSD). So my diving and photography and web publishing software are open source too. Some of these I've built myself.
Most photos on this site are taken with a Sony RX100IV and a wide-angle lens (UWL-09) or macro lens (Saga Dive Pro +15 Macro Diopter). More important than the camera is the lighting. I just use the cheapest Sea&Sea YS-01 strobes in TTL mode.
I have three pre-programmed modes set in the camera: macro mode (big aperture, fast shutter, full zoom), wide-angle mode (smaller aperture, slow shutter, almost full zoom out), and wreck (smaller aperture, slow shutter, higher ISO, almost full zoom out).
It's worth talking about rigging for a moment, because the more photography equipment, the more the question of rigging is significant. It's not just convenience—it's really a matter of safety.
When free diving, which I do with a lighter rig (one strobe or video light) that's slightly positively buoyant, I have a d-ring on my rubber weight belt. During a descent, I'll keep the camera clipped on. Then I take the shots I want at depth and either keep holding it on the way up or clip it.
Scuba is a bit more involved.
I generally dive with two video lights or two strobes, so
the camera is much bulkier.
I always dive with a neutrally buoyant rig, however, as I'm
already prone to
After diving, my workflow starts by getting pictures off the camera. For that I use gphoto. I pull the pictures (RAW+JPEG) directly into a pair of external USB 1 TB drives configured with RAID1.
Once pulled—it can take time—I fire up shotwell, which I use as my photo manager. I'll sometimes use geeqie for a single series of dive photos, but not for looking back over time.
I then edit the raw photos with ufraw and post-process in gimp.
Why these tools? My needs are few.
For the photo manager, I just want a quick glance, event by
event, of the photos, and the ability to easily open photos
in an external editor and save as a new file.
I don't really like Shotwell: it's slow and tends to use
system resources when it's just sitting there.
Plus, it's in
which is a
transpiler into C.
This makes it much harder to debug problems: are they in
vala logic or in the produced C code?
But I don't know of any other system that has a nice
I'm not really happy with this part.
As for editing, ufraw might not even be maintained any
more—but for me it's fine, as it's fast and all I
really use it for is colour correction.
The gimp works fine for my only use of it:
mask, as ufraw doesn't do any sharpening.
This is the boring part, I guess. I wrote all of the publishing components myself, though, so I like them.
First, I upload an exported image to my
I then create a Markdown file that tells the
and contains photo meta-data (exposure settings, location,
depth, temperature, date, etc.).
To get the temperature and depth, I review the dive profile
Technically, all of this—upload, mining EXIF data,
creation of the Markdown template—happens in one step
by a small
upload script I wrote.
So creating a new article is simple.
Once I have a Markdown file that I can edit with a story, the file is transformed into web page you see by combining lowdown to parse Markdown with sblg to manage templates. These tools are chained together with make, so the whole web site is built and updated with one command.
The tag indexes and such are built in the same way: shell snippets in the Makefile. This is probably the most complicated part because it involves lots of piping and chicanery. At the end of the day, everything's automated.
Why all the effort? Cause it's fun! Diving—no matter where you live—is a way to experience part of the world we often disregard as inaccessable. And in a way we'd otherwise consider impossible: floating effortlessly. It may take training, hard work, and discipline (and not a little disposable income), but it's worth it.