Mischievous Ramblings II

Printing 2 of X: Renaming (a lot of) Color Profiles on the Mac

With paper comes profiles.  With sample packs of paper come LOTS of profiles.  Profiles which invariably have unpleasant names, like "HFAPhoto_CanPro1000_PK_HahnemuehlePhotoSilkBaryta310" which neither rolls trippingly off the tongue nor makes it easy to pick "Hahnemuehle Fine Art Photo Silk Baryta 310 for the Canon PRO-1000" off of a menu.

Renaming the files is easy using Better Finder Rename, a mac utility I've been using for at least a decade.  It brings a step-by-step interface to simple and complex renaming of multiple files.  Well worth it.

But renaming the profiles isn't as simple as renaming the files.  ColorSync utility will let you do it, and there is a script provided to do the renames, but renaming dozens of profiles at once is a pain.  To use ColorSync directly, just double-click on the profile file, and then in ColorSync click on the 'dscm' Apple multi-localized description strings field if present and edit it, or click on the 'desc' field and edit it.  So far as I can tell, the 'dscm' field will take priority if it is present.  If you prefer, there is a 'Rename' script in the 'ColorSync' portion of the menubar script menu, which you turn on using the 'Preferences...' menu item of the 'Script Editor' app in the Utilities folder of the Applications folder.  But using either to rename a bunch of profiles remains a big pain.

So I wrote a shell script which renames profiles to their base filename.  It's crude and simple, and will probably break for other people, but here it is:

---

#!/bin/bash

for file in ./H*
do
    BASENAME="sips -s description '$(basename -s .icc $file)' '$file' "
    echo 'executing $BASENAME...'
    eval $BASENAME
done

---

Hope someone finds it useful.

I rename the files to roughly PaperManufacturer PaperName PaperWeight BlackType Printer, e.g. "Hahn Photo Pearl PK Canon PRO-1000" which still isn't a brilliant name to sing out at night, but at least tells me what I'm looking at.

Printing 1 of X: Testing (and Testing (and Testing (and Testing...)))

Previous post in this series

In which our Hero (ahem) seeks out the work of earlier giants, absorbs mentorship, tries and fails, learns that obvious things are obvious even to him (after failing), and muses on the proper order of tasks...

So, learning to print...

It's a big topic.  Here's how I'm doing it.

First, obviously, I bought a printer.  You can find that event in a previous post, already linked above.

Second, I started reading.  The second link, above, is an example of the kind of web search I'm doing, although they are getting more and more specific as time goes on.  I also bought a bunch of books.  Among them are:

• Jeff Schewe's Digital Print and Digital Negative;
• Guy Tal's More than a Rock;
• Robin Whalley's Photographers Guide to Image Sharpening and Perfect Prints Every Time;
• Fine Art Printing for Photographers by Uwe Steinmueller and Juergen Gulbins;
• Tom Ashe's Color Management & Quality Output;
• and more...

I haven't read them all -- hell, I haven't even cracked them all.  You will notice that I prefer ebooks.  They have less mass and volume than physical books.

Third, I started printing.  A manager of mine once said "you don't have time to make all the mistakes other people have made", so I gather other people's stories in order to make my own.  But in order to make my own, I've gotta actually try doing it.

Case in point: I'm starting with mostly black and white printing.  Not because it's easier but because I'm exploring my monochrome side :-).  I've got a variety of papers and a variety of images, I'm trying workflow improvements in Lightroom, testing control surfaces and keyboard overlays, adding color management (because when the images are only appearing on my displays, color is what I say it is, so why manage it?), and so on.  Eventually I observe that my sample prints are consistently far warmer (brownish, basically) than what I see I on the screen.  I can hold a print up to the screen and see the difference.  I find several different ways (eight? nine?) to characterize color management through the workflow path, using Lightroom, Photoshop, ColorSync, and multiple third party solutions.  I try them all.  I re-calibrate my monitors (3 of them!) and my printer.  I improve my physical set up so that I have allegedly D65 lighting above the printer.  I add an allegedly D65 task lamp to my desk.

And that is the magic.  Seen under the task lamp, images match the screen.  Seen under the overhead LED bulbs in my track lighting, images are warmer.

Lessons learned:

1. Paper alters the visual appearance of a print (duh -- but while I had considered surface reflectance and texture, I hadn't really grokked that white paper has a color -- because I'm an idiot);
2. Viewing light alters the visual appearance of a print (again, duh -- but I understand that in my gut now);
3. Perfection is a rathole -- I spent days researching, experimenting, and tracking this down.  The paragraph above does not do justice to the amount of work involved.  I have a new understanding that, while I have lighting in place above my printer and on my desk that is allegedly D65, I am not yet prepared to create spaces and spend money to virtually guarantee consistency of lighting in creating and viewing prints, nor am I yet knowledgable enough to select which of several possible standards (D50, D65) I should choose; so...
4. For now, good enough will have to do.

The number of details is overwhelming.  I have white cotton gloves to handle paper before it's used (to avoid getting skin oils on it, which may damage the print).  I have sticky notes all over one screen detailing my current (and some previous) procedures to go from (notionally) final image in Lightroom to image on paper.  I am in the process of creating somewhere between 12 and 30 proof copies of the same black and white image for paper tests.  And I will do the same for at least one color image (probably more -- a set of color charts won't suit me in this, so I will probably print images with several color sets).  Those proof prints will have to be protected and stored, because while I expect to settle on a couple of paper types for common use, there will undoubtedly be images I want to treat specially in the future, and I don't want to do sets of tens of proofs over again if I can help it.

Why am I in such a hurry to pick a paper?  Because a friend has indicated he would like a print (actually, he offered to buy it, but I'm giving it to him) and I don't want to lose this opportunity to share my art with someone else.  But I'm geeky enough to want to get it right.  And there is no management chain standing over me telling me how I have to do something, or setting a schedule.  I'm eager to get it done, but I want it right before I release it :-).

Soft Proofing for Printing

A huge element of this process is going from (allegedly) final image to print.  Working the image is a whole thing in itself (and I'm working hard on that too) but going from image to print is a new thing, not an adjustment of an existing thing.

I work in Lightroom wherever possible to do what I want.  In this case, that means I'm working in the Develop module, I'm using Before/After Left/Right Split as my View mode (I set it in the toolbar at the lower left corner of the working window), checking Soft Proofing (also down in the tool bar), and make sure the Before image is the "Master Photo".

 

My preferred soft proofing screen, cut down to about 1/4 of my monitor.  Click image to embiggen.

First thing to do is make a Proof Copy and select the paper's ICC profile in the "HIstogram/Soft Proofing" panel of the Develop module.  I see whether Perceptual or Relative intent better serves my purposes (almost always, for now, I'm ending up with Perceptual) and check what Schewe calls the "look like crap" box -- the "Simulate Paper & Ink" checkbox.  Then zoom to 100%

Why do I check that box?  There are places on the web suggesting you not bother, because Soft Proofing in Lightroom "overdoes" the loss of contrast moving to a print.  Yeah, that's true, and I often find myself looking at the difference between original black and simulated on-paper black and trying to figure out a way to make on-paper black blacker.  But I can't.  But the simulation gives a decent look at the overall color cast of the paper, which matters a LOT to me, relatively speaking.  The difference between white white and warm white (or cold white) in a black and white print is something I want to see.

Generally I find that relatively minor Basic adjustments are all I'm doing here.  Maybe up to 0.3 exposure change, less than 10 Temp change.  Sometimes a bit of Contrast.  Schewe advocates a bit of Clarity to boost the lost contrast, but I'm not there yet.

When I'm satisfied, I jump over to the Print module.  From there, I check the Page Setup... to make sure the Paper Size is correct.  When I have more than one printer, I imagine I'll be checking which printer I'm talking to, too.  If I haven't changed anything, I'm careful to hit the Cancel button because sometimes the OK button makes my panels go away.  No, I don't know why.  I just avoid it if possible.

Printing via Lightroom Print module

From top to bottom, I make sure:

• I'm on Single Image;
• Rotate to Fit is checked;
• Margins are 0.25" each;
• Cell Size is appropriate for page size;
• all Guides are shown.

Print Resolution gets unchecked momentarily to check the actual print PPI (upper left corner of the image, but it only appears when Print Resolution is unchecked).  Since I'm working on a Canon printer, I want my resolution to be a multiple of 300.  If the resolution is between 300 and 600, I set it to 600.  I haven't gone higher than that yet.  Then make sure Print Resolution is checked so that Lightroom will resize the image to a multiple of the printer's native resolution.  If it were an Epson, it would be 360 (720) instead.  I should note that Schewe says this is only necessary when working with high-gloss paper and not when dealing with "watercolor" papers.  I infer that smooth surfaced papers are more likely to show a difference here, but don't worry too much about doing the upsampling when unnecessary.  It's just CPU cycles and RAM, and I've got enough of both.  When the new iMac Pro or Mac Pro gets bought, I'll have even more :-).

Print Sharpening gets set according to what I've done to the image before calling it a master.  If I did no sharpening, I set it to High.  If I did capture sharpening, I set it to Standard.  I haven't set to Low yet because I trust Lightroom to do my target sharpening for me (so far).

Media type is set to Gloss or Matte as appropriate.  I call Satine or semi-gloss glossy.

Make sure the profile is set correctly (why doesn't Lightroom make this profile match the soft proof profile if present?  I don't know, but it should). Check the Intent (ditto).

Now the Printer... dialog.  If I'm working off a commonly used paper, I have a preset.  If not, I start with defaults and check to make sure that:

• Color Matching is disabled and set to ColorSync;
• Paper Handling does NOT have "Scale to fit paper size" checked and that Destination Paper Size is correct;
• Quality & Media has the right Media Type and the right Paper Source.  I rarely play with Print Quality so far, and am not yet testing the Black & White Photo Print mode;
• Paper Detailed Settings has "Cancel Margin Regulation" checked in case I'm doing borderless printing or, really, just to make sure I'm in control of the margins.

At some point, I may set color options for one or more papers, in which case there will be more saved presets, but I haven't seen any reason to do this yet.

Hit the "Print" button in the dialog, and wait...

After Printing

It doesn't really take that long to do a print.  But a print should be let sit for minutes to hours after the ink hits the paper.  ColorMunki software says a minimum of ten minutes for color to stabilize.  Schewe's Digital Print notes that prints are susceptible to scratching for several hours and to avoid stacking prints without interleaf sheets and further advocates waiting 24-36 hours before framing to allow ink to outgas.  Since I am doing test prints right now, this isn't really relevant to me.  If I scratch a print I just have to compare it somewhere it's not scratched.  When I am doing production prints I will search out a source for interleaf sheets and use them.

Many of my prints go upstairs and get put on a table in the living room that gets lots of natural light in order to see them in an alternative viewing setting.  It also gives my wife a chance to peek at them and point out problems she sees that I do not.  My color discrimination is not great, so it's nice to have someone else take a look at them.

And there it is.  The current Testing process.

Printing 0 of X: Introduction to a series.

Next post in this series

First Print on Canon PRO-1000, 4x6, Evan Robinson, scanned 2017-05-11

As part of a two-and-a-half week road trip to the Southwest, this year I attended the penultimate Moab Photography Symposium.  The symposium itself (and the Terrific Trio workshop immediately before it) are worth at least one post by themselves, but I want to concentrate on the upshot, which is that I committed printer when I got home.

And in my usual fashion, I went pretty big.  When I walked into Glazer's Camera Supply in South Lake Union (just blocks from my old job at Amazon) looking for a printer, ink, paper samples, and advice, I was 95% sure I was picking between an Epson P800 and a Canon PRO-1000, with the initial edge going to the Epson because of its paper roll support (important for printing panoramas).

After 20 minutes or so of conversation with Dana (the reason I support my local camera shop and try to buy a minimum of 1/3 - 1/2 of my gear from them, in addition to anything I need significant advice about, is this kind of knowledgeable support), the benefits of the Canon were convincing me.  In no specific order, they included: current deals on the printer plus about $400 in free paper, a $300 rebate, separate channels for photo black and matte black, higher build quality, hack to use bigger paper, and a previous lifetime's worth of Canon loyalty.  On the down side, there is no straight media path, the thickest media I can put into the Canon is about half the thickness of the Epson's ability, and I need a hack to print a large pano.

Regardless, I wasn't being steered to something I hadn't considered, and the reviews on the Canon have been good, so I went for it.  It came with five boxes (125 sheets) of 17x22 Canon paper, and I threw in a couple of sample backs of Moab and Canon 8x10 sheets.  I screwed up by not getting a pile of 4x6 pages for initial testing.  Getting the whole thing into the car alongside a cooler full of Costco meat (see previous posting on new pellet smoker) and the dog wasn't trivial, but part of the Glazer's service included a hand truck and Dana's help lifting and pushing.  I left the printer box in the car until Kiernan got home, and he helped me get it inside.

Next problem: this thing is NOT small.  The basic printer footprint is about 18"x30", but the 18" expands to nearly three times that when the paper feed tray and paper catching tray are open.  And it weighs 70 pounds, so it requires its own piece of furniture.  Plus storage for paper boxes and archival boxes for prints.  Without much hope, I visited Storables at U-Village when I went to the Apple Store.  And they surprised me by having a technology that seemed to do the trick: their Industrial Post Steel Wire Shelving, which is an easily assembled, more attractive and flexible version of Gorilla Shelves.  With each shelf rated for 300 pounds and each rack rated for 2000, all I needed to do was figure out my needs.  I sketched a few ideas, measured a space in my office, and spent about a day throwing shit out and packing shit more efficiently to get the space I needed next to my desk.

The shelving went together as easily as described (perhaps more so) and I wrestled the printer box (which could easily hold at least one body, in my inexperienced estimation) downstairs into my office, lifted the printer out onto the top shelf (easier than it should have been -- Canon ships the printer in a bag with handles which is designed with handles to lift the printer out), removed the 20+ bits of orange and yellow tape, plastic, foam, and so on which protected the printer during transit, installed the print head and so many ink cartridges I lost track (apparently they are individually keyed so that you can't put them in the wrong place, but I never tried because the labeling was so clear so I can't confirm that), and ran the setup program.  Which, contrary to my previous experience with Canon software, was reasonably clear and did a good job, even avoiding me having to enter my wifi password via a four direction keypad on the printer.  It takes quite a while for the printer to set itself up, and the process is rather noisy as the print head moves around, the vacuum feed system blows air here and there, and the ink cartridges are milked to fill in the lines to the head.  There's also apparently some kind of ink agitation system built in (I think Dana mentioned ball bearings in the cartridges) that rattles a bit.  The whole process of unpacking and setup probably took a couple of hours, but I was in no hurry and wanted to get it right.

Upon realizing that the bulk of the paper I had was 17x22, and the smallest was 8x10, I stopped at Office Depot and bought a box of 100 sheets of 4x6 HP semi-gloss photo paper.  I figured that if there were going to be big problems, starting small was a good idea.

Remarkably, the process is pretty straightforward at my current level of understanding.  It's annoying to have to print via the "Plug-in Extras" menu, and I wish Canon's Print Studio Plus did a better job of understanding borders, but it's OK.  I'm unclear as yet whether the printer's idea of what kind of paper overrules PSPs or vice versa, and I'm pretty sure I'm going to try out an additional printing manager (possibly PrinTao, possibly something else) at least to implement that pano hack and probably to manage paper types.  B&W prints on the HP paper are a bit warm, and I need to work on that, but I haven't even gotten a custom profile for this printer yet.  It may also be the paper, not the ink.  Things to investigate, things to learn.  Things to become (or resist becoming) obsessed about :-).

It will be an adventure.  I shall remain steadfast in memory of Mark Hamburg's immortal statement (Mark was the architect on Photoshop when I was at Adobe):

"Color Is Hard"

Why didn't I do this sooner? Oh, yeah....

Transcend Travel CPAP/APAP.  Image borrowed for fair use from Intertubes.

 

Sara and I both use CPAP (Continuous Positive Airway Pressure) devices.  These are small machines that sit by the head of our bed and force air through a hose, into a mask that covers our nose, and down our airway to our lungs in order to keep it open while we sleep.  It is a treatment for Severe Obstructive Sleep Apnea (SOSA) which is a condition in which the airway closes periodically during sleep.  We actually use devices called APAPs (Automatic Positive Airway Pressure).  Each of us has two APAPs, one for home and one for travel that is smaller and runs easily off a battery.

As a geek, I want access to medical technology that I have to use, and I want data on my usage (my pulmonologist says that I am his poster boy for compliance, and seeing the data is part of that for me).  As a pilot, Sara requires data from the CPAP for her flight medical.  Both of us want to be able to program the devices to change their pressure parameters as our needs change.  To do this, you need special software, and in at least one case, a special piece of hardware and cable for the CPAP.  We have all of that.  We have everything we need to access data on and program each of the four machines (two types) that we use.  I have visited multiple pulmonologists in the 15+ years I've used CPAP, and never has one been able to read data off my machine.  But I can. :-)

You also need a Windows machine.  The CPAP market is not so large that the manufacturers build great software, and they only build it for Windows.  Some of them use outdated hardware specifications (like 9 pin serial ports and 8 pin DIN connectors).  Many will write to one or another kind of SD card (some only to original SD, not SDHC, some to micro SD, etc.), but all of them I've encountered require Windows software to extract data and get reports.

Have I mentioned how much I hate Windows?  I have an old media PC I bought from someone at Amazon that I run the software on.  It's old and crappy and never connects to a network, and only comes out to run this software, but to do so, I have to keep a monitor around and move my keyboard and mouse while I set the machine up somewhere, and it's just a pain.

So I thought, I'll buy myself a cheap old Windows laptop, maybe even with a serial port, running Windows 7 or 8, and it'll be cheap and easy to move around and I can reclaim the cubic yard of office that the current device and monitor and keyboard and mouse occupies.  And I did.  I went to the local neighborhood computer repair place and bought a used ASUS laptop for $150, and it's just what I needed even if it doesn't have a serial port and runs Windows 10.

I need to install two applications on it.  One for each brand of CPAP.  And it takes hours.  The first app is on CD, and it doesn't have a disk player, so I move one over from my Mac and it reads it but it won't install the software because the software uses a library that isn't included in Windows 10 and won't install off the CD in Windows 10 and I have to research it and find the newer 4.0 version that includes the older 3.5 and 2.0 versions and install it and see if the installer will recognize it and I try to install that software four times before it works.  The second piece of software isn't nearly so bad so I only need to install it twice before it works.  And then it takes 40 minutes for the Windows 10 system to recognize the USB to serial adapter and find a driver for it, and another 30 minutes to update the Windows 10 system files.

And finally it works. And I have a portable system that I can use to access my own medical data and program my own medical devices.

And this morning when I turn it on to suck data out of my CPAP, it takes 20 minutes to update Windows 10 again.  Two days after I last updated it.

Now I remember why I didn't do this sooner...

 

Cross Posted to Group News Blog

Photography, Storage, and Backups

Upon returning from my most recent photo workshop (five days on the Olympic Peninsula with David Muench, Jerry Dodrill, and Grant Ordelheide), I set upon my routine of backing up photos.  Step 1: use Chronosync to move photos from my laptop to my desktop.  And was immediately stopped by the lack of available space on my desktop.

This prompted a re-evaluation of my storage strategy for photos, which prompted a re-jiggering of my backup strategy.  I thought I'd document both for anyone else who was having similar issues, or needed a little help figuring out out to handle the mass of data a modern DSLR (or two) can generate.

I'm currently in possession of over 50K digital images taken over the last 16 years (I lump anything before 2000 in with the 2000s for convenience -- there aren't very many and they're small anyway).  If I include images, movies, export versions, DNG and sidecar files generated by Adobe Photoshop Lightroom, as well as movies and folders, it's 63,187 files and folders occupying 1.28 TB.  More than some, less than others.

Enough to be a pain.

My data usage and backup workflow used to look like this:

1. Copy photos from camera data cards to Laptop Internal SSD drive (manual)
2. Separate photos into date folders and rename (manual using scripts)
3. Import photos into Adobe Lightroom (manual)
4. Backup from Laptop Internal SSD drive to External SSD drive (manual)
5. On return: Sync Desktop Internal SSD drive photos with Laptop Internal SSD drive photos (manual using Chronosync)
6. Backup from Desktop Internal SSD drive to RAID Box 1 (automated daily with Chronosync)
7. Backup from Raid Box 1 to Raid Box 2 (automated daily with Chronosync)
8. Sync from Raid Box 2 to Amazon CloudDrive (manual using GoodSync)

Using this workflow, I have a master library (the external SSD "backup" drive plus the current year or two on the internal drives of my laptop and desktop), two local RAID backups, plus a cloud backup.  If my master fails or I lose a drive, I can redirect Lightroom to point to a RAIDed backup without much effort (each year folder is directed separately).  A notable potential problem is that I may work simultaneously on my laptop and desktop on the same catalog or even images.  I have avoided this problem through discipline, which will eventually fail.

The workflow interruption came initially at step 4 (the external SSD was no longer large enough to hold my entire photo library, which was nonfatal because the photos were also on the laptop drive), then because fatal at step 5 when the desktop internal SSD was not big enough.  Even though the laptop and desktop internal SSD drives were only holding this year's photos, going on a long road trip this spring followed by two workshops this summer had my total image for the year approach half a terabyte.  Because the desktop also has a Parallels image occupying about 50GB, there wasn't enough room on that drive.

I do all my work from SSDs whenever possible.  Backup systems (the three RAID boxes in my office) are all using spinning drives, but each is set up so that one drive can fail without data loss.  With my primary photo library now well over 1 TB, I didn't have an SSD large enough.

Immediate ideas: break my photo library into multiple libraries.  Many luminaries recommend one catalog per year, and I already store images in folders by year, so it wouldn't be a stretch.  But I'm not ready to do that.  I have vaguely imagined moving significant images to a "good images" catalog and storing them separately, but I'm dubious about my judgement in picking out the good ones, so I'm not happy with that idea.  I could get a small RAID box like the ThunderBay Mini 4 (designed for laptop drives) and fill it with SSDs, but that would cost in the neighborhood of $3K for 6 TB of usable storage.  Or I could find a 2 TB external drive and move my primary library onto that.  Which I decided to do.  It cost about $800 including several new USB-C 3.1 cables, and of course Amazon delivered in two days.

It took overnight to copy the entire library (including several shoots I'd held out as distinct) to the external drive and make sure that the corpus matched the files on my backup drives.  The copy took that long because the USB C cables I bought from Amazon didn't implement USB 3 (as specified).  They're going back for longer cables (I like 6" cables for drives attached to my laptop).  The biggest issue was some wonky file permissions that were different among backup versions, which a few minutes with the Terminal sorted out.

Now that I am using the external drive for my primary library, the workflow is simpler:

1. Copy photos from camera data cards to External Library SSD drive (manual)
2. Separate photos into date folders and rename (manual using scripts)
3. Import photos into Adobe Lightroom (manual)
4. Backup from External Library SSD drive to RAID Box 1 (automated on booting external SSD using Chronosync)
5. Backup from Raid Box 1 to Raid Box 2 (automated daily using Chronosync)
6. Sync from Raid Box 2 to Amazon CloudDrive (manual using GoodSync)

I still have my master, two local backups, and a cloud backup.  I've removed two manual steps.  In case of disaster, switching to using a RAID backup instead of my External SSD master is now a matter of relocating one folder in Lightroom instead of one per year.

My projections indicate that this solution will last no longer than the end of 2017, but I have that much time to figure out a catalog schema that will cross multiple drives.  I have also accepted that it's OK to delete the technically unacceptable photos* and will be going back to do that.  By next June I need to have a solution.  In the worst case, I can buy that small external RAID device and fill it with large SSDs, but that's just throwing money at the problem, and it dramatically reduces my ability to work portably, since the external RAID requires a power brick, while the external SSD drive doesn't.

With the exception of the length of time it takes to sync up to Amazon CloudDrive, I'm happy with this solution.  Manual steps are reduced, I have a "working token" in the external Library SSD to make sure that I'm not working simultaneously on the desktop and laptop versions of Lightroom, and the backups are more automated (and will be even more so when I turn on GoodSync automation now that the sync is a single job instead of one job per year).

My friend Chuq von Rospach is only one of the people who notes that there are two kinds of computer users: those who haven't needed their backups yet and those who have.  Those of us who have are more likely to set up systems to make sure our backups are in good shape.  I have tested every portion of this system except a full restore from Amazon CloudDrive (I have restored a relatively small year's worth) and am unaware of any reason why I won't be able to get my photos back in the face of almost any disaster (i.e., my computers can be lost or destroyed or my house can burn down).  I might add periodic backup to a spinning drive to be placed offsite, but so long as Amazon AWS stays in business I have offsite backup covered.  It would take at least two simultaneous disasters for my to lose it all :-).

 

* I did a sunset shoot working to get seagulls crossing in front of the ball of the sun, using my D500's 10 fps and a long lens.  In that demanding setting, using a brand new camera I'm not familiar with and that I hadn't configured the AF system on, nearly half the images were out of focus.  In a first, I deleted them wholesale.  I'll gradually be going back over my catalog seeing if there are other obviously worthless photos to get rid of.  I doubt it will be a 10% reduction, but at this point that's 100 GB, so it would be worth it.

Thoughts on the Apple Watch after less than 24 hours

 1) it's a little strange to be wearing a watch again.

 2) the apps screen gets full really really fast

 3) I want to write complications for it.  Complications are the elements that can be configured in watch faces.  A quick google search has not turned up any information on creating them.

 4) It was obvious that the watch was going to be a relatively simple i/o device attached to my phone. Brief experience bears that out -- with the exception of the watch face and complications (some of which DO depend upon the iPhone -- Weather, for instance) -- it's a new interface into existing apps on your iPhone.

As such, it creates a new category of interactions which used to be folded into your phone -- extremely brief ones for which you might have carried your phone in your hand (e.g., moving to the next song or changing the volume on your music -- exactly what buttons on your headphones or cable were intended to do) -- like incessantly checking the time, or a countdown timer you have in place.

So I'm not quite sure that I like the idea of games on the watch.  If you are sufficiently engaged in something to interact with it constantly, why not use your phone, which has a bigger screen and better UX?  The only game type I can see working on the watch is something where you make a very simple decision every few minutes or so.  Definitely NOT highly interactive systems.

5) Oddly, the watch is more intrusive than the phone for interacting, because it absolutely requires two hands.  There are a lot of things I can do on the iPhone with a single hand (the previously mentioned music manipulations, simple short texts or typing with one thumb, swiping, etc.) but I have to have my phone out and in one hand to do it.  The watch, which doesn't need to be taken out or put away, must be manipulated with the opposite hand.  It sounds small but it it weighing heavily right now -- partly because in each case the primary use hand is my right hand.  If i'm holding the phone to do one handed manipulations, it's in the right hand.  If I'm manipulating the watch in any way other than just flipping my wrist to the see currently displayed glance or app, I'm doing it with the right hand.  I assume that lefties will act correspondingly using the left hand.

Anyway, those are the first thoughts.  More later, I imagine.

 

Cross Posted to Group News Blog

Gordon Walton: Publishers see devs as "replaceable meat puppets" | GamesIndustry International

Walton spent many years building games to put in boxes for retail stores, and over time began concentrating on online games, which demands a relationship between the company and individual gamers. That's a difficult transition for publishers used to the old way of doing business. "Most of the big companies I work for think about the consumers like a faceless mass, and not about people," Walton said. "People are the ones using our stuff. Even in the mid '80s, when I was doing games then, I always went to alpha as quickly as I could. I was on the online services and I would recruit people who were interested in the topic and I would have forty or fifty people playing my early game and giving me feedback, because you can't see the forest for the trees when you're making the game. Just because you made it for yourself, and your team, and they all think it's cool, doesn't mean a damn thing if customers don't think it's cool."

via www.gamesindustry.biz

Not like the industry hasn't heard this before, and I doubt they'll listen just because Gordo got some press.  OTOH, if reading Gordo's words educate even a few of the kids who enter the computer games business every year, then it's a great thing.

"Limiting access may be impossible"

According to Fox News: 

A new Department of Homeland Security intelligence bulletin warns it could be "impossible" to stop 3D-printed guns from being made, not to mention getting past security checkpoints.

Of course, it's not like you can't just build a working gun with parts from the local hardware store.

The undetectable thing makes sense, except for the fact that ammunition is currently made out of metal.  Whoops!  Except for this 7.62x51 (308) DAG Training Ammo.

The world is changing: I feel it in the water, I feel it in the earth, and I smell it in the air.

Which countries do not belong?

You'd think we'd be over this by now. Really.

Us, Burma, and Liberia?

"River of Meat Blood"

From Gizmodo:

Drone Pilot Discovers River of Meat Blood

Seems like a "Dallas drone hobbyist" was flying his camera equipped drone around when he "...discovered a huge stream of blood emptying into the Trinity River..."

Seems like the meat packing plant (aka slaughterhouse?) he was flying near was (probably) illegally discharging, um, waste material into the local watershed.

As more and more drones get into private hands, this is an example of the way that we, the people, can turn the tables on the wholesale surveillance state -- by turning the cameras on them.  Turn the cameras on the police, the corporations, the politicians... on The Man!

Apropos of, well, everything about this: Eye3; Engadget; TechCrunch