I believe this is now day 195 of the Sonoma Shelter-in-Place against Covid-19. We’ve also had a half-dozen serious wildfires since the last festival at the County Fairgrounds. It finally cleared this morning, for the first time since August 18th to have smokeless skies.
Also, according to my ongoing Covid tracker for Sonoma County, the number of active cases here has been in decline since about the first of the month.
Quiet, lovely light just before the county lockdown. So easy to be distracted.
It’s been almost three years since the previous post on using a Chromebook with Fujifilm cameras. How are things today, in 2020, after several newly-released cameras, OS editions, and improved Chromebooks? What about… iPad? Have other camera brands started to catch up?
In this other posts I’ll be looking at the current options and will describe how I’m integrating ChromeOS into my photography (and general) workflows.
This small series was triggered by the recent addition of the Samsung Galaxy Chromebook to my working kit. Like Samsung’s other premiere Chromebooks, it arrives with a touchscreen, pressure-sensitive integrated pen, micro-SD reader (now supporting the high-speed UHS protocol), and support for Android apps. On the Galaxy, you get a solid aluminum frame that’s lighter than the Macbook Air, a 4K OLED display, and at last Samsung has shipped a top-tier Intel-powered (i5-10210U) Chromebook with offical support for Linux.
Basically: the machine I’ve been waiting for since 2017. Did I mention it’s orange?
In this 2020 post, we’ll look at moving photos from camera or SD cards to Chromebook, or to somewhere nearby.
Wireless, standalone devices can provide camera archive storage without a laptop. They range from the luxury Gnarbox SSD to inexpensive spinning disks like my Western Digital Wireless Pro, which trades speed and weight for price (the Gnarbox also provides “folder presets” to allow custom structured-on-import storage like the system I described here).
For my use, this is all good, and the WD can even function as an ad hoc NAS.
Sometimes, you just have to do it yourself.
There are easy ways for a creator to manage digital media, but they tend to be a bit inflexible, or they don’t scale well, or you just never can figure out where your photos are actually stored, which can make backups confusing (or expensive, if you’re paying a monthly fee for cloud storage).
A couple of years back I decided to unify a single storage method for photos, video footage, and audio field recordings. My method needed to apply to all three media types, could handle external drivees, and needed to be able to run on most any kind of device: Mac (at the time, my homme machine), Windows (at the time, my office machine), or Linux (added for travel, using a tiny Asus Eee PC and a La Cie rugged drive).
The result was a python script called kbImport3 – it’s worked for me for over a decade now, with a few minor tweaks like adding DNG support, AVCHD video support, and a minor tweak for running on Chromebook.