While there are some great efforts, like Magic Lantern, to reverse engineer and improve the firmware, I wish the producers just made the source part of their product. (I don't believe their trade secrets are that valuable to be honest. Not more valuable than letting people builds apps for your camera, at least)
[1] - http://magiclantern.wikia.com/wiki/Magic_Lantern_Firmware_Wi...
As a programmer, my natural inclination is to sit in my fortress of arrogance and build the thing that I "know" they need. But learning how to do user testing, user interviews, and customer development has persuaded me that the important moment isn't when the product ships, it's when somebody actually uses it.
I almost never use my non-phone camera anymore because the point for me isn't taking a picture, it's doing something with it. Which camera companies would know if they treated anthropologists with the same respect as CCD scientists.
Nikon and Canon's target market, photographers, want to spend their time taking photos, not writing code for their camera.
Besides, most of the "possibilities" listed in the article are already available on a lot of cameras (like the intervalometer), better done in post processing (like previewing on ipad), or easily done using a $20 wireless remote control.
Don't get me wrong, it's cool that he's hacking on his camera, but I don't see Nikon and Canon ever promoting it or going out of their way to make it easier.
For those more familiar with the Raspberry Pi, does it actually have enough performance to move big RAW files around? A 5D3 will output ~30MB RAWs and in a shoot you may end up with 500+ of them. Having a Pi transfer/move/adjust them sounds like a slog.
As for image manipulation, sadly, the Pi is fairly fast by embedded standards, but running general-purpose software on a full-blown OS takes a lot away.
For comparison, the original Xbox used an x86 of the same clock speed.
Which is why we any predefined image manipulation should avoid the ARM core and jump straight to the rather powerful GPU. I think it even supports OpenCL, so there should be software out there that could work with it.
>For comparison, the original Xbox used an x86 of the same clock speed
which is fairly useless as a point of comparison, as not only is it the completely different arm architecture, but it is also Arm V6 (arm11), whereas even our smartphones have been arm v7 (cortex A8, A9, A15) for the last couple of years. If i had to equate it to an x86 clock speed, i'd say 400mhz was possibly a fraction generous.http://www.extremetech.com/electronics/134190-nikons-android...
I also got one of those small Realtek RTL8188SU wifi dongles and found that it worked very poorly. I don't know if it was the particular vendor I got mine from or the drivers or that particular chipset, but the interface would just stop working if you tried to do anything data intensive or prolonged on it. SSH and VNC were unusable.
I steam 720p video for hours on end over a IOGear GWU625 (Realtek RTL8191S) with no problems.
(Requires powered hub AFAIK, I don't think I tried it without though).
http://www.amazon.com/Airlink-compatible-Wireless-Mini-USB-A...
I suppose a thing that small and cheap is too good to be true.