002:365

January 3, 2012

002:365 by daggerquill
002:365, a photo by daggerquill on Flickr.

Day 2

001:366

January 3, 2012

001:366 by daggerquill
001:366, a photo by daggerquill on Flickr.

Since I’m not using this space for anything else in in particular at the moment, I’m rolling it only my 365 project. And, who knows? maybe it will get me blogging about other things, again, too.First up: Tara ringin in the new year with her nephew.

This an open complaint to every PC maker on the planet: get over it already.

I know that there are historical reasons for this nonsense. Decisions had to be made decades ago, and the mess of RGB, VGA, sVGA, etc. complicated things. Plotting RBG values in a VGA space is difficult, and people don’t agree on the best place to make compromises. blah, blah, blah.

This is 2007. This should just work. This is software problem, not a harware problem, so lets just agree on the defaults and get on with it. The is no longer any valid reson that if I edit a picture on a PC, it should look differnt when someone viws it on a Mac or Linux box, or vice versa. There is certainly no reason that it should look substantially different on two machines plugged into the the same monitor.

If the industry can agree on standardized cross-platform serial, parallel, RAM, and video busses, it can agree on a standardized value for one single-precision float.

I know, I know. I can adjust the gamma to suit my fancy. I can embed sRGB profiles in most image types.

But I shouldn’t have to.

Last week, I did something stupid (an unfortunately frequent occurrence). I was going through my digital camera trying to free up some space on the card and, so I *thought*, protecting the pictures I wanted to keep or hadn’t uploaded yet. When I hit delete, and confirmed that yes, I was absolutely sure I wanted to delete the pictures, though, I had one of those slow motion realizations that I hadn’t protected the most recent snapshots. What to do? Google, or course. But as it turned out, there are no free unerase options for removable media on Linux, and not many for OS X that looked reliable. Sometimes it seems, Windows users may have it better after all. After a little searching, though, I stumbled across a few fragments of C++ code that claimed to do the job. Thing were starting to look up. The only problem was that C code makes my head spin, and I wasn’t about to trust my un-backed-up pictures to some random code, even if a recovery process that involved paying attention to `gcc` output had appealed to me. Enter the savior of lazy programmers everywhere, Perl. One of the truly great and often overlooked things about using an operating system with unix heritage, whether OS X or a Linux or BSD flavor, is that it almost certainly has a default Perl install. Unless you’re a sysadmin or programmer, you may pass over this extrmemly useful tool most days in favor of flashier alternatives like applescript, or pre-built binaries from versiontracker, freshmeat, or rpmfinder, but it’s nice to know the power tools are there when you need them. And when you munge you data, you need them.

This how-to will cover recovering data from a munged CF or sD/xD card using only the tools built into your system.

Read the rest of this entry »