Posted by Scott Laird
Wed, 16 Jul 2008 21:08:00 GMT
Well, that’s a whole lot of fun. I pulled my iPhone out of my pocket today and discovered that it’d been rebooting silently in my pocket for at least an hour. It just kept cycling through a boot cycle every 30 seconds or so, showing an Apple logo then turning off, then showing the logo again, then turning off. I plugged it into my laptop and it booted up just fine, but it immediately asked me if I wanted to power the iPhone off. It seems to work as long as it stays plugged in, but it’ll start rebooting again as soon as I unplug it.
Digging around a bit, I think the lock button on the top of the phone is broken. While it’s plugged in, it’s almost impossible to get it to work, and I end up getting the ‘Do you want to power off’ screen more often then a locked iPhone. Trying to get back to the home screen from inside of apps by pressing the big round button doesn’t always work; I end up with a screen shot instead, which is a sign that the lock button is being pressed.
Wonderful, what I really wanted to do today was to run to the Apple store and try to get a non-existent replacement phone.
Update: An Apple store 20 minutes away had a Genius Bar opening in 30 minutes, so I signed up for it online and jumped in the car. It took them about 3 minutes to decide that I needed a new phone, so they grabbed out out of the back and sent me on my way. Total time to repair, including travel time: about 50 minutes. Not too shabby.
Tags broken, iphone | 1 comment
Posted by Scott Laird
Sun, 22 Jun 2008 15:53:00 GMT
So, after thinking about it a bit, I went out and ordered an Amazon Kindle ebook reader. It arrived last Tuesday, just in time for me to take it with me on Wednesday’s flight to California. The Kindle let me leave 5 lbs of books at home and cut a couple inches off the thickness of my laptop bag, which was a pretty substantial improvement over the previous week’s flight.
Over the past 5 days, I’ve read 3 complete novels on it–Thirteen, All Tomorrow’s Parties, and Slaughterhouse 5. All three were purchased from Amazon and downloaded to the Kindle over the air; I’ve also stuffed the Kindle with a few free ebooks from tor.com; their moble editions convert perfectly for the Kindle via Amazon’s free email converter. After reading 900-ish pages on the Kindle, I’m about 95% happy:
- The screen’s great. The print quality and contrast feel slightly better then a mass-market paperback. Yeah, the background’s kind of grey and there’s a very small amount of roughness to the letters, but you have to go looking for it to see it. It’s a 160 DPI display, just like the iPhone. I haven’t clocked myself reading, but it doesn’t feel any slower then reading paper books, and it hasn’t left me with a headache or anything. It’s substantially better then reading novels on a laptop (which I’ve done at least 3 times this year).
- The software’s pretty good. It’s better then anything I’ve seen from a non-Apple, non-Tivo consumer electronics product in years. My only concern is the book selector UI–it turns into a big cluttered mess once you get more than 30 or 40 items on it. I’d love to be able to organize books by read/unread status, genre, etc., but that’s not really possible right now. Instead, you get a list that you can sort by access time, author, or title. It’s okay, but not great. Considering that I could probably cram 2,000+ books onto a SD card in the Kindle’s SD slot, a simple sorted list really isn’t good enough. On the other hand, with a couple dozen files total it’s not a huge issue, and it’ll probably be fixed in a future software update.
- It’s reasonably fast. Waking from sleep takes around 10 seconds, and flipping pages takes a second or so. In either case, it’s not really any slower then picking up a paperback, stowing the bookmark somewhere, and figuring out which page I was on, or simply flipping pages. It’s not instant, but it’s fast enough for now.
- The overall size is fine. It’s almost exactly the same size as a DVD case, so it doesn’t fit into most pockets, but it’s still easy to keep around.
- The next page/previous page buttons are too big. They make it hard to pick the Kindle up without accidentally flipping pages, and they constrain the number of ways that you can comfortably hold it in your hand.
- The DRMed book selection from Amazon is still kind of small (around 130,000 volumes, or the same as a mid-sized Barnes and Noble store), but it’s not horrible. I haven’t had any problem finding books from my to-read list on Amazon’s Kindle store. In addition, a number of publishers have released free books in Kindle-compatible formats (like Tor and Baen. I have 4 or 5 Tor books on mine ready to go when I get a chance.
All in all, I’m happy with the Kindle. It’s Good Enough. As things stand, I’m probably going to switch to buying most of my books in Kindle-compatible formats going forward, partly because they’re more portable, and partly because I’m getting tired of the sheer size and physicality of regular books. I’ve ripped all of my CDs and most of my DVDs and I haven’t looked back. It’s just easier to have them in electronic form, and I’m happy to have the space back that all of the disks took up. I used to have 2 or 3 shelves full of disks, but I still have an entire room full of books. I’d be just as happy if I could get most of them in a DRM-free ebook form, but even DRM-encumbered Kindle files are still an improvement for most of my reading.
Tags books, kindle | 3 comments
Posted by Scott Laird
Thu, 05 Jun 2008 14:32:00 GMT
I should have planned this better. I’m going to be one a plane to NYC (and therefore completely out of touch) during the WWDC keynote. That means that I’ll have to wait hours to learn about all of the exciting new iProducts that Steve is trying to sell me.
The scary thing is that I’m not sure if I’m joking or not.
Tags apple, joking, notjoking | 4 comments
Posted by Scott Laird
Wed, 04 Jun 2008 01:43:00 GMT
I’ve been tempted to buy most of the e-ink ebook readers for months, and now I’m faced with spending around 16 hours on airplanes in the next two weeks, and I’d love to travel without 5 lbs of books. From what I can see, Amazon’s Kindle
is probably the best fit for my needs. Does anyone have any recommendations one way or the other?
Tags ebook, kindle | 5 comments
Posted by Scott Laird
Wed, 04 Jun 2008 01:11:00 GMT
The last few months have been kind of quiet here for two simple reasons:
- I’ve been completely swamped with launching something new at work. That’s finally done.
- Every spare non-work minute has been spent in my back yard, working on The Project That Won’t Die. I’m re-terracing the lawn, putting in a big planter/retaining wall thing with a couple sets of steps, putting in a new paver patio, and then re-planting the whole lawn. The end is finally in sight there, too.
Basically, I’ve been alternating between not having anything interesting to say and having lots of things to say that I couldn’t really talk about.
Hopefully that’ll be changing soon. I’m changing projects at work; I was the lead for the Google download servers (need a new copy of Earth, Toolbar, Sketchup, Gears, etc?), and I’m going to be taking over a new service soon. The new job’s going to involve a lot of travel; I’m going to be in either NYC or Mountain View at least once per month for the rest of the year, and will probably be visiting at least 2 other offices for one of my side projects. Considering that I’ve only flown 4 or 5 times for Google in the 2.5 years I’ve been here, this’ll be a big change in pace. The job’s starting quickly–I first heard about this yesterday, and I’m already booked to fly to New York next Monday. I’ve never actually been there before, so it should be entertaining. I’ll be stuck in the office for most of the time, but I’ll have a couple free hours per day to wander around and see the sights. I’ll try to hit a couple of the tourist high points this time, and then branch out on future trips.
Tags google, travel, work | 1 comment
Posted by Scott Laird
Wed, 19 Mar 2008 01:19:00 GMT
So, one of the features that’s been in the WebKit tree for a while but finally showed up in Safari today is downloadable font support. You can use CSS to apply a specific font to an element and Safari will download the font from a URL provided.
That’s really cool, but the odds of an exploitable buffer overflow somewhere in the font rendering pipeline has to be almost 100%. I mean, almost every graphics format has had multiple exploitable bugs on every platform, and I can’t see how a complete OpenType renderer can be any less complex than JPEG. Even worse, this is a new attack vector, against a part of the system that wasn’t part of the security perimeter before. Is there a way to turn this off?
Tags fonts, safari, security | 1 comment
Posted by Scott Laird
Wed, 19 Mar 2008 00:37:00 GMT
The Verizon FiOS installers have been circling the neighborhood lately, tearing up sidewalks, digging holes in lawns, and (finally) pulling fiber down the telephone poles in the direction of the nearest CO. According to their call center, they’ll probably be able to upgrade me from 3/768 DSL to 15/15 fiber sometime around the middle of next month. I’ve been waiting for years for them to finally make it to my place, so I’ll probably have to have a party or something :-).
Just for the fun of it, I was reading Verizon’s business FiOS system requirements page. Here’s a snippet:
| Speed | Recommended CPU speed | Recommended FSB speed | Recommended free disk space |
|---|
| 5/2 Mbps | 600 MHz | 100 MHz | 128 MB |
| 5/5 Mbps | 733 MHz | 133 MHz | 200 MB |
| 50/10 Mbps | 2 GHz | 330 MHz | 500 MB |
So, not only do I need a faster CPU to enjoy a faster connection, I also need additional free disk space? Huh. Who knew?
Tags fios, verizon | no comments
Posted by Scott Laird
Tue, 18 Mar 2008 16:21:00 GMT
I really thing I should get some credit for this: I managed to wait until March 2008 to buy myself an iPhone. I didn’t rush out and wait in line on the day they shipped. I didn’t buy myself one when the price fell. I even bought my wife one first, in December for our anniversary. Admittedly, I was in a car on the way to the nearest Apple store when Steve first announced the iPhone last January, before he bothered to mention that it wouldn’t ship for 6 months, but it’d be totally unfair to count that against me.
More seriously, it took me quite a while to convince myself that it was time to retire my trusty Nokia E61. The E61 served me well for almost 2 years, but it was time to swap. In theory the two phones are fairly similar–fairly large screens, WiFi, EDGE (the E61 does 3G in Europe, which doesn’t help me much here), and Safari-ish browsers. In reality, they’re a wonderful demonstration of why feature checklists are worthless. Here are the things that I care about most:
- The iPhone is hands-down better for reading and writing email via Gmail. The native IMAP client is good enough, and the iPhone version of the Gmail web interface is vastly better then the version that we feed to the E61, even though they’re running very similar WebKit-based browsers. The E61’s keyboard is better, but the HTML edit box in Gmail’s mobile web interface is so bad that it cancels out the keyboard advantage.
- The browser is better. It’s faster, it doesn’t crash on every third Amazon page that I try to load, and the touchscreen scrolling is better than the joystick on the E61.
- It’s actually usable as a music and video player. In theory, the E61 can play movies and music, but (1) there’s no easy way to copy content onto it (unlike the N-series phones, it doesn’t come with an iTunes plugin), (2) out-of-the-box it only supports wacko video codecs, and (3) the UI’s bad.
- It’s easier to charge. My E61 has never charged right; swapping batteries and chargers never made a big difference. The iPhone, on the other hand, uses a semi-standard connector and charges via USB. It’s easy to find iPod cables and USB jacks, but finding a spare Nokia charging cable is tough, at least around here.
- I’m never, ever going to have to see Nokia’s stupid “which network connection do you want to use?” dialog box again. For some reason, Nokia decided that asking the user before letting apps use the network every single time was a good move. It’s smart enough to know which networks are available, and which ones I’ve configured it to use, but it’ll still show me a list with one or two choices every time. Bleh.
- The on-screen phone keypad includes letters. It’s a stupid thing, but the E61 doesn’t give you an easy way to dial vanity phone numbers, because there’s no way to tell which numbers map to which letters. I mean, can you tell me off the top of your head which numbers you need to press to dial ‘1-800-884-SOIL’?
The E61 wins a few points, though:
- It comes with a SIP client that’s actually be useful at home for me.
- It’s open, and you can install useful software.
- The Nokia podcast client does a great job of copying new episodes of Escape Pod for me on the fly.
- It’s louder. That makes it harder to miss calls.
SMS is kind of a push between the two; the E61’s ringer is louder and it has a better keyboard, but it takes way too many button presses to do anything.
So, for now I’m using the iPhone. Yeah, I could have waited for the 3G iPhone or Android, whenever they appear, and I may swap for one (or both?) of them when they’re available. From everything that I’ve seen, Android’s programming model will be vastly better than the iPhone SDK, at least for the weird types of things that I care about, but it’s not shipping yet.
Tags iphone, nokia, nokiae61, shiny | no comments
Posted by Scott Laird
Sat, 02 Feb 2008 18:37:17 GMT
Soo Valley, near Whistler, B.C.
I spent Thursday and Friday in Whistler along with a few hundred co-workers, enjoying the Seattle version of Google’s annual ski trip. I took the opportunity to go snowmobiling for the first time, and took my camera along.
I need to find another excuse to go play in the snow with my camera; that was too much fun.
Tags google, snow, travel, whistler | 1 comment
Posted by Scott Laird
Wed, 23 Jan 2008 04:32:38 GMT
One of my favorite places to take pictures is on Fir Island, in Skagit County, Washington. It’s a farming community in the Skagit River delta, and it’s home to around 1 million migratory birds every winter, including Snow Geese and Swans. Ever see a cloud of geese turn the sky white?
It’d been weeks since I’ve been able to spend time hiking around with my camera, so I drove up Monday morning before dawn to see what I could find.
Dawn on Fir Island
There were geese and swans flying by all morning, but I never got a really great shot of any of them from up close. There were thousands of them visible in the distance, though.
Morning flight
It’s been really cold lately, and there was ice everywhere, including the sea shore. There was a weird layer of office over everything; I assume that it was left behind by the falling tide. The plants looked like they’d been wrapped in cellophane.
Plants in Ice
Finally, on the way out, I spotted this Heron hiding in a drainage ditch a few feet from the road. He was my third or fourth heron of the day.
Cold Heron
I can’t help thinking that a bit of fill-flash would have helped there, but he was close enough that it probably would have startled him.
Tags birds, foxisland, photography | 2 comments
Posted by Scott Laird
Sat, 19 Jan 2008 19:16:00 GMT
As any experienced digital photographer can tell you, the trick to getting repeatable color out of a lab is to get a good ICC color profile for the lab’s printer and using it for every print that you make. I’ve been a big fan of Dry Creek Photo’s printer profiling service for years; they work with labs to build quality profiles and then publish them for free on their website, along with some documentation on how to use them.
Unfortunately, actually using the profiles is a pain for most users. The process looks roughly like this:
- Using a color-profiled monitor, get things looking the way that you want on the screen. Save.
- Resize the image to the correct resolution for the print size and resolution that are required for your lab. Different labs want 300, 320, or 400 DPI.
- Convert the image to the color profile for that lab that you’re using. Possibly re-adjust colors slightly.
- Pad the image out to a specific number of pixels to keep the lab’s printer from trying to re-scale your image. The exact settings depend on the printer and paper size. There’s a big chart on Dry Creek Photo’s website.
That’s not a big deal if you’re printing one or two pictures for framing, but it’s a huge pain when you have dozens or hundreds of pictures to process. Photoshop actions can help, but it seems like something is always going wrong.
When Adobe released their Lightroom SDK, I had high hopes that it’d make it easier to automate most of this. Unfortunately, Adobe didn’t expose their profile conversion engine to the SDK in the first SDK release, so it’s not really possible to build pre-profiled images directly out of Lightroom without using some external tool to do the profile conversion. A few weeks ago, Timothy Armes released LR/Mogrify, which uses ImageMagick’s mogrify command-line tool for profile conversion. It’s a cool tool, but it replaces a 5-6 step process in Photoshop with a dozen text boxes that you need to fill in to get good results. It shows promise, but it’s not quite the tool that I’m looking for.
What I really want is a Lightroom export plugin that asks you three simple questions:
- Where are you going to print this?
- Which paper are you going to use?
- What size do you want?
Then it does all of the hard work on its own. It’d fetch the correct profiles from Dry Creek, install them, figure out which resolution to use, handle image rotation, do some amount of pre-print sharpening, and then spit out a JPEG for you. Yeah, you could do a bit better with Photoshop and spending some time dealing with soft-proofing and sharpening, but I’m not willing to do that for 50 4x6 prints.
I’ve spent a bit of time this week building the first part of the tool–a machine-readable profile database. I’ve extracted a list of 765 current ICC profiles from Dry Creek Photo’s website, discarded the profiles that haven’t been updated in years, and produced an XML file that looks sort of like this:
<lab>
<name>Costco #747</name>
<address>24008 Snohomish-Woodinville Rd. SE, Woodinville, WA 98072</address>
<phone>425-806-7708</phone>
<printer>Noritsu 3411</printer>
<paper>Fuji Crystal Archive</paper>
<resolution>320</resolution>
<notes>Note: This lab has multiple printers. Request your profiled prints be run on Noritsu 34?Pro-B.</notes>
<profile>
<name>Glossy paper profile</name>
<date>January 17, 2008</date>
<url>http://www.drycreekphoto.com/icc/Profiles/IccFiles/Washington/Costco-WA-Woodinville-Gls.icc</url>
</profile>
<profile>
<name>Lustre paper profile</name>
<date>January 17, 2008</date>
<url>http://www.drycreekphoto.com/icc/Profiles/IccFiles/Washington/Costco-WA-Woodinville-Lus.icc</url>
</profile>
<size>4x6in</size>
<size>5x7in</size>
<size>8x10in</size>
<size>8x12in</size>
<size>12x12in</size>
<size>12x18in</size>
</lab>
<lab>
...
The <resolution> and <size> blocks are semi-manual additions; the import script sets resolution automatically when it sees a printer type that only has one resolution setting, but Noritsu 3XXX printers can run at either 320 or 300. I’ve filled in the one or two labs that I use most frequently, and I’ll to add others as time permits. The <size> bit is fully manual, and I’m not really sure that it’s worth the effort to populate.
Right now, the XML file lists 380 labs. Entertainingly, that’s 379 Costcos plus Adorama. It looks like Dry Creek has dropped almost everyone else. If there’s a second source of non-Costco profiles, I’d love to know about it.
So, anyway, I have this XML available at http://profiles.sigkill.org/profiles.xml. It’s mostly automatically generated, and I can rebuild it in under 5 minutes. I’ll keep it up to date if people are interested in the data, if not it’ll die off eventually. If you have a tool that wants to use it, then send me mail and let me know that it’s useful. If you have any changes that you’d like to see, or anything that I should add, let me know and I’ll see what I can do.
Tags photography, profiles | no comments
Posted by Scott Laird
Sun, 02 Dec 2007 17:19:20 GMT
I’m really not looking forward to going home from my vacation.
Sunset from Waikiki
1 comment
Posted by Scott Laird
Sun, 02 Dec 2007 05:50:54 GMT
I bought my wife an Olympus 790SW point-and-shoot camera before we left for Hawaii on vacation, and I’m growing increasingly fond of the little thing. It doesn’t really compare to my Canon 5D’s image quality, but it’s so small and handy that it’s easier to carry. Even better, it seems to be indestructible–it’s submersible and can be dropped up to 4.5 feet without breaking anything.
In other words, it’s the perfect beach camera for families with small kids. Plus, you can take it snorkeling, just in case one of these pops up:
Sea turtle
or some of these:
Reef fish
There are more pictures on Flickr if you’re interested.
It also takes semi-decent video. I wouldn’t confuse it with a HD camcorder, but I wouldn’t take the camcorder in the water, either. Here’s my son’s first time snorkeling:
It’s around $260 on Amazon, if you’re interested.
Tags family, photography, review, vacation | no comments
Posted by Scott Laird
Thu, 22 Nov 2007 19:56:00 GMT
So, I’m in Hawaii this week for vacation with the family. It’s been a while since I’ve had a real vacation that didn’t involve cross-country drives or tight deadlines. I’ll write more eventually, but for now, have a few pictures:
Lighthouse at Dawn
Obligatory palm tree
Sunset Beach surfing
Tags hawaii, vacation | no comments
Posted by Scott Laird
Fri, 16 Nov 2007 13:40:45 GMT
It looks like Lightroom 1.3 is out. More excitingly, the Lightroom Export SDK is now available. I guess it’s time to learn Lua.
I might wait until after next week’s vacation to pick up Lua, though. I have a beach calling my name.
Tags lightroom, lua | 1 comment
