In previous years, we’d remained at the venue (as a competing team, not as host) until at least 11pm usually (once past midnight – after which we had to make an hour and a half drive back home) due to waiting for technological hiccups to be overcome so that we could continue, but last year was different.
SD cards are pretty cheap these days, but that doesn’t mean we should let our smaller ones go to waste, especially when a system doesn’t fully utilise the space of a larger one that could be more useful elsewhere.
The main problem of Win32 Disk Imager is that it creates an image file the same size as your SD card, no matter how much of the card is actually being used. If you’re using a 32GB card with a 4GB partition and the rest is unallocated space it will still create a 32GB image file.
Typically, however, I think most of us will allocate the full size of the SD card to the system.
When the Eye-Fi works so well with the iPad, why would I want to seemingly make life more complicated for myself by adding more hardware into the mix?
Well, transferring to a Linux based machine like the CubieTruck offers me some advantages over the iPad. Some of them I alluded to in my previous post on this topic, but at the time, my primary thought was really just on-site backup (after making the switch from SanDisk Eye-Fi cards to Eye-Fi Pro X2 cards).
No real interaction, no file serving to viewing devices, just straight up copy the images to the CubieTruck, and then copy it all onto my network when I get back home.
This post is more of a ramble than anything else. There’s no real substance here (and feel free to agree or disagree with that), I’m just jotting down some thoughts and providing a little background for other posts I plan to make.
My current WiFi situation on Location works for me at the moment.
As I shoot, a couple of seconds after hitting the shutter, the images come up on my iPad screen. I can immediately see which images have hit their focus and are nice and sharp without unwanted motion blur.
I can get a better overall view of the scene on the iPad so I don’t have to spend hours fixing something in Photoshop that I missed on the tiny LCD on the back of the camera. I can just see it and fix on set before taking another shot.
As I’m planning to turn the CubieTruck into a portable backup storage device for use on location, I thought “What if I could transmit via WiFi to the Cubie (or Raspberry Pi) instead of the iPad?”
When I first heard of AirPlay, I figured “Apple only”, being the proprietary types that they are. I’d always seen it bandied about with words like “Apple TV“, “iMac” and “Macbook Pro“.
As the only Apple devices I own are iPhones and iPads, I never really looked much further into it.
A few days ago, I started trying to see if I could find an application that would allow me to record my iPhone or iPad display to a video file, for including in a tutorial video I was putting together.
As it turns out, there ain’t an app for that – at least not one that runs on the device itself.
Cross compiling is something I’ve never really had a need to do before. All of my past Linux machines have been your standard 32Bit or 64Bit x86 based PCs, and have been fast enough that I’ve been able to compile on the machine it’ll be running on.
But, if a 15 hour XBMC compile taught me anything (other than the fact that XBMC doesn’t work fantastically on the CubieBoard), it’s that I need to setup a decent Linux box, and learn to cross compile for ARM based hardware.
I’ve also always wanted to create my own Linux setup from scratch for a long time. The CubieBoard gives me the opportunity to do this, but it will require some cross compiling to get things started.