Getting to know my Eye-Fi card in preparation for AU 2010

Eye-Fi Pro X2As part of my preparation for a class I'm presenting at AU, Point Clouds on a Shoestring (AC427-4), I bought myself a new toy a couple of weeks ago: an Eye-Fi Pro X2 memory card.

This very cool little device is much more than a high capacity SD card: it has an in-built Wi-Fi chip that allows it to connect to your local Wi-Fi infrastructure (whether via a wireless router, access points or an ad-hoc connection to your PC) and will automatically upload the images you're taking to a folder on your system and (optionally) to your favourite photo sharing service such as Flickr. I chose the "Pro" version to have the flexibility to connect to an ad-hoc network with my PC, something I may need when presenting in Las Vegas.

As you're no doubt aware, I don't normally do product reviews, but I can see some really interesting potential uses for this technology – especially the thought of adapting it for use with tools such as Photosynth or Photofly – so I can't resist going through how it works. My idea is to give a digital SLR containing this card to a member of the audience to take snaps of an object inside the classroom. While I present, the volunteer will hopefully snap away and the resultant photos would just appear in a folder on my PC, ready for uploading to Photosynth and Photofly (a manual step, for now, but I'm certainly chewing on ways it might be automated :-).

So far the device seems to work well. To get started you place the card in the provided reader and plug it into a USB port on your system, at which point you should have the option to install and then launch the Eye-Fi Center application.

Eye-Fi card in USB readerEye-Fi AutoPlay

The Eye-Fi Center is – as you'd expect – the tool you use to configure your Eye-Fi card. You start with the main UI, from which you can display and modify the various settings of your Eye-Fi card(s), as well as manage the photos you've taken and transferred.

Eye-Fi Center The first things you typically want to configure are the network settings. The UI to allow the card to connect to detected access points and ad-hoc networks is pretty straightforward:

Eye-Fi Center - adding networks

You can manipulate the location under which transferred photos are stored on your local machine:Eye-Fi Center - photo settings - computer As well as the options for uploading them to your file-sharing service:

Eye-Fi Center - photo settings - onlineI actually found that I needed a file-sharing service configured and enabled – even if I only wanted images transferred locally to my PC – which surprised me somewhat. Perhaps this was a glitch specific to my set-up but it took me a while to recognise it. You'll see later on there are ways to only upload selected images to Flickr, etc., so it's not an especially big deal, all things considered.

I shoot neither RAW nor video with this particular SLR, so I won't bother looking at those settings.

The next option of interest is related to geotagging:

Eye-Fi Center - geotaggingThe card doesn't contain a GPS chip (now wouldn't that be something?  🙂 so it relies on the WPS service provided by Skyhook. Apparently iPhone devices once relied on this service for non-GPS positioning (such as inside buildings), but as I don't have an iPhone this is my first exposure to this service. It's pretty slick – it certainly did a surprisingly accurate job of positioning the images I've taken at home and the office:

Eye-Fi geotagging in actionAnyway, the last setting I'll look at is the transfer mode. This is important if you don't want all the photos you take uploaded to an online service (even in "Private" mode):

Eye-Fi Center - transfer
modeI have left the mode set to "automatic", for now, but have used "selective" effectively when I only wanted the images to be placed on my machine.

As well as the Eye-Fi Center application, there's also an Eye-Fi Helper agent which presumably maintains some kind of connection with the Eye-Fi servers and remains ready to bring down images as they become available. When it does so, a toast pop-up notification appears with a thumbnail and progress bar for that download:

Photo notification

All this no doubt raises some security concerns for some people (in fact I've seen such concerns raised on the web), but I personally see more potential benefits from the technology. And I'm now getting used to service providers hosting (and hopefully not looking at) my files, and in any case the images I take are innocuous enough.

On the download frequency: the images tend to download in fits and spurts. Part of this is about being close enough to the wireless router (or PC if using an ad-hoc network), but it's also about configuring the camera not to turn itself off in attempt to save power too readily. I suspect there must also be some server-traffic component to this on the Eye-Fi side of things, as there are certainly times when it feels as though the photos should come more quickly.

The other change I've made – specifically with respect to Photosynth and Photofly – was to adjust the resolution of photos being taken by my SLR down to 3 megapixels. Neither technology makes use of anything above 3 megapixels (and Photosynth's synther apparently uses a maximum of 2 megapixels), so anything greater would mean some conversion is needed prior to upload to these services, as well as resulting in a larger download from the Eye-Fi servers.

I'm going to continue to play with the technology over the coming weeks, but so far I'm pretty impressed (and think it'll add a fun component to the AU demo). If you'd like more detailed information on this Eye-Fi product, see this review on Engadget.

  1. Kean,

    Awesome review. You definitely do not need to share your photos online, or to any sharing site, if you don't want to. You can just turn off web sharing, and leave the card in local-mode only. That's absolutely supported.

    Once you have the card in loca-mode only, you can choose to have Relayed uploads ON or OFF. ON, means that even if your PC was off, the photos would go through the Eye-Fi Servers, stay there, and then, next time that you turn on your PC, the photos would come down to it, from our servers. It also means that if you've enabled open hotspots, and you're at Starbucks for example, the photos will get to your PC, from Starbucks, and get relayed through our servers.

    If you turn Relayed Uploads OFF, the card and your PC will need to be on the same network (LAN) and the photos will not upload, unless the PC is on, and the card is online, through your secured or open in-profile network.

    So there really is no privacy concern, if people don't want to have their photos shared.

    We're from the camp that sharing is great, and that even archiving and backing up to the cloud -- is the smart thing to do. If you upload to Flickr, for example, and your photos are private, no one is seeing them, BUT, you're building a backup of your photos, in case your hard drive will crash. So it's a good thing 🙂 That said, many people don't want to have their photos on the net, and it's totally up to them.

    Thx --

    Ziv.

  2. BTW, for your live presentation, you will get more range if you don't do ad-hoc. ad-hoc is super cool and convenient, because you don't need to carry an extra router.

    But if you want to have the card in the audience, and you needed more range, I would recommend getting a solid N router, and you'll get much more range.

  3. Good day Kean,

    indeed a good review of the card I just bought this weekend. I am certain to get a lot of fun from it. Did you install the adhoc finction laptop /camera?
    I am loosing somthing out as it won't work for me.
    And yes my card can do the adhoc as it is the pro-card.
    How did you establish that?

    Would you mind to give me a word of advice into this issue?
    Thankx

  4. Hello Jan,

    Yes - I've used the AdHoc mode. If you have the Pro card, then you should be able to, also.

    I followed the online instructions for setting up and connecting to the network, and it all worked fine.

    Best regards,

    Kean

  5. I know this comment is a bit late... but I disagree with Ziv, vehemently.

    I do NOT (I can't emphasize this enough) want Eye-Fi central servers storing my pictures or my passwords, EVER. Now, it is possibly the case that with Flickr or other photo sharing sites that this is an unavoidable engineering issue for 100% reliable service. But I really, really strongly believe that there should be an option for NOT turning that relay mode on, and making the card talk directly to the service.

    I'll listen to technical arguments about "cloud" services, but I refuse to believe that you need to relay when sending to my FTP server. What, please tell me, is the reason I should be giving some remote service access to my FTP server? And why does your widget on my Mac keep talking to your systems in Hurricane Electric every minute or so, regardless of my use of the EyeFi card? I hate opaque security risks, and your product presents a HUGE opaque security risk. This is what I see when I look at my logins after enabling upload via FTP:

    eyefitemp ftp lrrr-int.eye.fi Tue Mar 22 02:26 - 02:26 (00:00)

    WHAT?! No, no, no. Get out of my machines. This is basically giving carte blanche to your staff to walk into my systems. ("But trust us!") I want to see the card talking directly to my server, and if that doesn't work, NO RELAY. Ever. EVER. My passwords must stay in my control, not yours. If I choose to give you that ability - great. But right now this is a hidden security bomb that most users have no idea about.

    And you can't tell me that your sysadmins haven't ever seen the thousands of pictures being streamed through your servers every day. I would bet you large amounts of money that there is a secret "Best Of" directory somewhere there with all kinds of good stuff in it, but that's pure speculation.

    I've brought this up before at EyeFi when I first got my card, but I suspect there is nobody there who actually thinks this is a problem, so I'll air it publicly here.

Leave a Reply to Jan Deschepper Cancel reply

Your email address will not be published. Required fields are marked *