Camera Pi – DSLR Camera with Embedded Computer

Post by aortega » Sun, Aug 19, 2012, 6:34 PM UTC

nakedrobot2 wrote: post #12

StringyBob wrote: post #10

Earlier quoted context omitted.

The amazing CHDK: http://chdk.wikia.com/wiki/CHDK_in_Brief for those who aren't aware of it. If I could ensure a new camera was supported, that alone would be enough to make me buy it over any competing models.

The story of how the CHDK was born is really amazing. Remember that "print" button on your camera, the one you never use? It has a light on it. Apparently someone coaxed their camera into outputting the source code of the firmware getting the "print" button to flash on and off.....

Post by climberhunt » Sun, Aug 19, 2012, 7:33 PM UTC

tkahn6 wrote: post #2

FYI you need a powered USB hub to attach that wifi dongle. 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.

Post by beagle3 » Sun, Aug 19, 2012, 8:10 PM UTC

wpietri wrote: post #14

nakedrobot2 wrote: post #13

Here is my rant, as an experimental (panorama, gigapixel) photographer: Canon, Nikon, and the rest of them will go to their graves keeping their firmware closed and un-scriptable. It is a tragedy. Mobile phones and the Gopro are eating their lunch. The fact that there is even a (niche) market for things like the Eye-fi (wifi sd card) goes to show how utterly clueless and behind the times these dinosaur camera compani…

Yeah. A great example of how people go wrong when makers focus on the product they're building rather than the people they're building it for. 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…

Post by wpietri » Sun, Aug 19, 2012, 10:09 PM UTC

beagle3 wrote: post #25

wpietri wrote: post #14

Earlier quoted context omitted.

Yeah. A great example of how people go wrong when makers focus on the product they're building rather than the people they're building it for. 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…

That's a nice thought. But the real reason they do it is market segmentation; e.g. when I looked at it two years ago, the Canon T3i was infinitely better and cost less than any IP camera out there. If they let you stream out of it live, it would kill the ip camera market. So they don't.

Post by sliverstorm » Mon, Aug 20, 2012, 3:07 AM UTC

polshaw wrote: post #17

sliverstorm wrote: post #8

Earlier quoted context omitted.

The Pi does about 10MB/s over the network, I believe. 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.

>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.