Category Archives: Apple

    Click on the title of the blog post to view the entire entry.


    My first impressions of the iPad

    (Sigh, insert “pad” joke here – maybe something about Procter & Gamble’s stock price? Your call. )

    First off, I was immediately struck by how think the borders are around the device. Is this so I can race matchbox cars around it and pretend I’m Dale Earnhardt, Jr.? (Of course, this would be counter-clock wise only).

    Screen shot 2010-01-27 at 4.00.02 PM.png

    Maybe it’s for big greasy fingers to hold the thing? Or vise grip robotic arms to hold it (controlled by SkyNet)?

    Second off, people are blabbering on about how the Kindle is dead. Au contraire mon frere. Nay. Not. Nada.

    Here’s why.

    The Kindle uses the liquid ink technology which is easy on the eyes, like an actual book. The iPad is going to be bright and not well suited for sitting down and reading a novel for hours. Apples and Oranges (er, no pun intended) . Sure the technology is awesome, and I eagerly anticipate using it to read technical or photography books, but novels? Probably not.

    Also, regarding reading books. Content. Content. Content. Amazon is still the center of the book universe. If Apple locks out the Kindle app from the device, this will be a big problem. If not, it’s a non issue, and I’ll probably continue to buy my books from Amazon. Somehow I doubt I’ll be finding Neal Asher or Ian M. Banks novels on the Apple store.

    Also, as an aside, all the animation in the demos of the book reading app annoyed the poo out of me, and I haven’t even used it yet. I hope you can turn off all that fluffy demo chrome and just use it. The same goes with the rest of the device.

    By the way, I read a lot.

    Some omissions:

    1. no mention of Verizon.

    2. maybe I missed it, but no handwriting app? Maybe the whole stylus thing made it a non-starter. To Newton-esc?

    3. it would be nice if it had an iChat camera. But I can see why it doesn’t. Where to put it? Streaming video over At&t? Er, epic fail waiting to happen. Maybe v2 will have it.

    Other than that, as a iPhone developer, I’m super excited because of the product development possibilities. Especially for someone like me who specializes in photography and web services and all that kind of thing. Rubs his hands together and grins. Pinky, it’s time to take over the world!

    I’m glad it will be released in a few months, this gives me time to save my pennies to buy one. The 3g version of course.

    Apple’s iPad.

    Customer service done right

    So, quick story.

    It was a dark and stormy night. Johnny Cash was playing on the Jukebox, singing about his empire of dirt. My battered Harley was parked out front. A half ashed Marlboro Red hung from my dry lip, the smoke stinging my eyes, as I nursed another highball. The bar was worn oak, threadbare, from a thousand average joes like me, with a thousand stories, sobbing into their beers. The light was dim, like my prospects, lit, mostly, from the screen of my Mac Book Pro. I was trying to forward a important email to all my friends and family. It was an important email about an exiled prince from Nigeria who has a million dollars he wants to split with me (I met him on craigslist when I was trying to sell a set of Hello Kitty tire stem caps). The kicker was I just needed to come up with a couple of thousand bucks to lend him so he could get on a plane ticket to Houston where the money is. I knew my friends and family would want in on this deal. It was a sure thing. It had to be, dammit. But the button on the computer was all clicked out. I had no click. No clickage. Click? Nope, don’t got any. The trackpad button wouldn’t work. I couldn’t send off the email. The dammed thing. That’s my hard luck story. One story in a million in the big city. Bartender, slide me another…

    Turns out, the battery on my Mac Book Pro suddenly swelled up. Not good. Next stop, explosion city and the eleven o’clock news. I figured this out because it swelled enough enough to eliminate all the space for the track pad button to depress inside the case. No battery equalled plenty of click. After some head scratching, tinkering, a sandwich, a ten thousand piece three-d puzzle of stonehenge, and a episode of CSI (you know, for the sleuthing vibe) I figured this out.

    Next stop, Appleville. I took my battery into the Apple store and showed it to to the frickin’ geniuses there. (Now, could that sound more sarcastic? I submit that it could not.) Some genius there quickly took the old battery off my hands, see, and recycled it, see, and gave me a shiny new one, see. For free. Keep in mind, my battery is almost 3 years old. The replacement is a $130.00. I couldn’t believe it. I kept looking over the shoulder for a guy in a suit, dark glasses, and an ear piece to come hot, weapons drawn, and talking into his sleeve about taking “the shot”.

    I have another random story about Apple customer service. A while back I took apart a Mac mini to upgrade the Ram. This procedure is tricky, requiring the use of two paint spatulas, a m-80 firecracker, a backhoe, and some warm chewing gum. Yes, it has to be warm. Midway through the procedure, things, um, got away from me, and I did an impression of an old timey vaudeville act. I ran around screaming “I got it! I got it! I got it!” bobbling the naked motherboard around in my hands like NFL receiver trying to haul in the game winning catch. All to the sounds of some honkey tonk ragtime piano music. Then, of course, I screamed “I don’t got it!” which was followed by a sickening crunch, a small fire, and a rift in the space-time continuum. I broke the IR receiver right off the motherboard. So after I nearly burned down my neighbors house trying to solder it back on (you don’t think I solder at HOME do you?). I took finally took it into the genius bar, fully expecting a bank busting bill. When the Apple genius asked me what happened, I fessed up and told the truth (cause, that’s just how I roll, McDuff), and, much to my shock, they said that since I didn’t lie, they’d fix it for free. Seriously. Me dropping an open computer onto the ground and breaking something off the motherboard is NOT covered by ANY warranty that I know of. Sweet.

    Mike is happy Apple customer today. Also he’s hopped on the goofballs. Of the over the counter cold medicine variety.

    Peace out, crime fighting dog.

    Aperture is still horked, kerbusted, and fracked with lastest ProKit update

    I was hoping the changes in the Prokit update today would fix the Aperture problems. Nope. In fact it seems worse.

    Check this out. Some of my images are actually corrupted in Aperture. Actually, I think its the preview in the Aperture library, but still. Come ON, people! This is with the Nikon d70s RAW format. I’ve also seen this happen with my Panasonic Lumix RAW files. At least I think I have. Regardless, the work around here is to convert these to DNG and reimport them. For @#$% sake.

    Finderscreensnapz001

    Here’s Aperture failing to display my Nikon d300 photos:

    Aperturescreensnapz001

    Here’s the crash in import:

    Thread 12 Crashed:

    0 com.apple.Aperture 0×0000cbe9 0×1000 + 48105

    1 com.apple.CoreFoundation 0×92644329 __raiseError + 521

    2 libobjc.A.dylib 0×929ce09b objc_exception_throw + 40

    3 com.apple.CoreFoundation 0×9264b46a -[NSObject doesNotRecognizeSelector:] + 186

    4 com.apple.CoreFoundation 0×92649a6c ___forwarding___ + 892

    5 com.apple.CoreFoundation 0×92649b32 _CF_forwarding_prep_0 + 50

    6 com.apple.CoreFoundation 0×9255dac8 CFArrayAppendValue + 168

    7 com.apple.ImageIO.framework 0×92c190ce storeDataInXMPDictionary + 1018

    8 libxml2.2.dylib 0×94673cb0 xmlParseAttributeType + 2080

    9 libxml2.2.dylib 0×9464b698 xmlParseElement + 1748

    10 libxml2.2.dylib 0×9464c347 xmlParseContent + 206

    11 libxml2.2.dylib 0×9464b284 xmlParseElement + 704

    12 libxml2.2.dylib 0×9464c347 xmlParseContent + 206

    13 libxml2.2.dylib 0×9464b284 xmlParseElement + 704

    14 libxml2.2.dylib 0×9464c347 xmlParseContent + 206

    15 libxml2.2.dylib 0×9464b284 xmlParseElement + 704

    16 libxml2.2.dylib 0×9464c347 xmlParseContent + 206

    17 libxml2.2.dylib 0×9464b284 xmlParseElement + 704

    18 libxml2.2.dylib 0×9464c347 xmlParseContent + 206

    19 libxml2.2.dylib 0×9464b284 xmlParseElement + 704

    20 libxml2.2.dylib 0×946489ef xmlParseDocument + 1176

    21 libxml2.2.dylib 0×94646c86 xmlSAXParseMemoryWithData + 116

    22 com.apple.ImageIO.framework 0×92c174e0 readXMPProps + 476

    23 com.apple.ImageIO.framework 0×92c3b36a readXMPData + 136

    24 com.apple.ImageIO.framework 0×92c38453 initImageJPEG + 1630

    25 com.apple.ImageIO.framework 0×92c37dea _CGImagePluginInitJPEG + 65

    26 com.apple.ImageIO.framework 0×92c08cba makeImagePlus + 503

    27 com.apple.ImageIO.framework 0×92c0e618 CGImageSourceGetPropertiesAtIndex + 120

    28 com.apple.ImageIO.framework 0×92c0e572 CGImageSourceCopyPropertiesAtIndex + 120

    29 com.apple.Aperture 0×002f804f 0×1000 + 3108943

    30 com.apple.Aperture 0×002f31d4 0×1000 + 3088852

    31 com.apple.Aperture 0×00130637 0×1000 + 1242679

    32 com.apple.Aperture 0×00131f4b 0×1000 + 1249099

    33 com.apple.Aperture 0×000db56c 0×1000 + 894316

    34 com.apple.Aperture 0×000daffa 0×1000 + 892922

    35 com.apple.Foundation 0×9165f04d -[NSThread main] + 45

    36 com.apple.Foundation 0×9165ebf4 __NSThread__main__ + 308

    37 libSystem.B.dylib 0×963c5075 _pthread_start + 321

    38 libSystem.B.dylib 0×963c4f32 thread_start + 34

    Crikey, it looks like Apple is finally going to update Aperture

    I wish they’d hurry up, for the love of peter the pumpkin eater. I can’t use Aperture at all. Two reasons, no Nikon d300 RAW format support, and I found a crashing bug. Edit your photos in Adobe Lightroom. Key word them. Import them into Aperture. Aperture crashes. Parsing XML EXIF data. Dammit all to heck. To be clear, key word any photo in Lightroom. Even a five year old jpeg. Aperture crashes on import every single time. I doubt I would have run into this at all if I could have just used Aperture to manage my new d300 photos in the first place.

    I’ve spent a lot of time key wording my photos lately. I’ve individually key worded over 9000 pictures over the last weeks (I have about 3000 to go yet). This takes hours and hours and hours and frankly sucks my will to live. Though having them all key worded is so damn cool its worth the time. For example, now I can find all my pictures of Jack in the snow in Portland in 2005. Sweet. Plus I only have to do this once, since I’ve got into the habit of key wording photos when I import them now.

    I did this all in Lightroom. Now, Lightroom is a great program. Everything works. The new Nikon RAW formats. Importing. Editing. Printing. Thank the photo gods we have it. It’s worth every penny. Though I have to say some of the UI drives me out of my mind. The fixed panels on the side. Bad. Very bad. I want Aperture back. It’s been months since I’ve been able to use it.

    Here’s the 100% factual, no possibility for error, post on a rumor site that I got this info from: Apple hints at forthcoming Aperture update.

    Hit me on my iPhone…

    Why a MacPro, not an iMac?

    Jud asks me the question, why not an iMac instead of a MacPro? I started answering in a comment, but I’ll just make it another post.

    There are a couple of huge differences between the iMac and the MacPro. Well, more than a couple, but the (configurable) ones that affect me the most are, video card, RAM, and options for disk drives. Also, of course, the machine is just faster. Faster bus. More cores. Blah blah blah.

    The video card has a direct affect on how fast Aperture, Photoshop, etc., can process a huge photo, so the digital work flow is going to be much faster with a high end video card. Also, the MacPro has many bays for hard drives so you can throw in a RAID card and stripe 4 huge drives for speed. And of course you can stuff it to the gills with RAM. All these things speed up the digital workflow, which right now is bordering on frustrating slow on my MacBook Pro. This is why professionals use the MacPros, not the iMacs (though the iMacs are killer machines, imo, just not for photo or video editing).

    Think about previewing hundreds of photos back to back. A single photo from my camera is about 15 megs, so it takes a while to load and render each one. Typically, I make several passes through all the photos, rating them, weeding out the bad ones, adding keywords, and all of this is very slow on the MBP. It would definately be faster on a current iMac, but not fast enough.

    It’s all about the digital workflow. In my experience, I spend much more time processing the photos I’ve taken, than taking them. It’s too slow. Far too slow. Some of this is my inexperience. But some is definately down to the hardware. I want to spend as little time processing photos as I can. This is why I want a killer machine. I spend hours. Days. Processing photos. That’s time I could be doing something else. Something useful. Like watching Bounty Hunter crush school buses in HD.