Open Source Camera For Computational Photography
David Orenstein writes "Stanford Computer Science researchers are developing Frankencamera, an open source, fully programmable and finely tunable camera that will allow computational photography researchers and enthusiasts to develop and test new ideas and applications — no longer limited by the features a camera manufacturer sees fit to supply. Disclosure: The submitter is a science writer for Stanford and wrote the linked article."
Please make a camera with:
1. A built in clock that actually keeps time.
2. Built in GPS.
3. Some sensible connectors to upload videos in real time using appropriate external devices, or,
4. Built in Wifi/3G.
5. And all the good camera stuff.
In one device. Oh, and if you can actually make a scanning range finder at a sensible price and embed that too, that'd be great.
How we know is more important than what we know.
My PowerShot S3-IS is scriptable. (example) And it's not even a cutting edge camera. Lots of cams support scripting.
I work for the Department of Redundancy Department.
Not exactly revolutionary. CHDK has been adding features to Canon firmwares for years.
This looks promising. But optics being optics. a version with swings & tilts would be really exciting for landscape/architectural/product photographers.
My knee-jerk reaction was that the proprietary lenses (Canon) and imaging chip (Nokia) would limit customization. But they could be interchangeable, like monitors and printers on personal computers.
I haven't tried it yet, as my current camera is a Canon G5, which isn't supported, but this site really wants my next camera to be another Canon: http://chdk.wikia.com/wiki/CHDK
Help! I'm a slashdot refugee.
http://sdk.nikonimaging.com/apply/
D5000, D3x, D90, D700, D40, D60, D3, D300, D200, D80
And NEF (RAW) files
i wish i could stop
I have always wanted an Open Source printer. One that can be built and whose consumables made by those with the means without worrying about patents and all the nonsense. Think about what this could do for students and government departments.
I am personally sick and tired of shelling cash to the Lexmarks, HPs and Epsons of today. Why hasn't this taken off [yet]?
Look, here's the disclaimer: I am a software engineer. No, not hardware, software.
But I've written camera drivers from schematics and datasheets alone. It's *just not that hard*. Even for a software guy. I don't have an EE, just an interest in electronics.
And digital electronics are, quite frankly, rather simple. If you know ohm's law, and can read a datasheet or two, you could very easily put together a digital camera module. PCB express will happily etch the board for you, and you *might* have to do some soldering. Unless, of course, you buy one of the cameras from sparkfun or other hobby supplier.
If you can't learn drag and drop PCB design, or can't master basic electronics (ohm's law doesn't even require an understanding of calculus), maybe you shouldn't be tinkering with cameras at the circuit level. A fast fourier transform is far more complicated and difficult to understand than the electronics which go into camera sensors, and yet, is the foundation for all modern video and image compression. If you can't understand that, you will most likely not be contributing much of value to computing applications involving a camera.
Granted, I like open source stuff. But there's already plenty of it out there today - just pick the resolution, frame rate, sensitivity, etc... and go. You don't need the frankencamera. You just need the time and interest, and be willing to spend a few bucks on the hardware.
The society for a thought-free internet welcomes you.
When the best cameras in the world use the F-mount ;)
and hands-off too, which is what people want. When I was souping B+W with the right combo of film, over exposure and under development I could manage over 12 stops without burning or dodging the print. Post-WWII the army developed film and techniques to cover 22 stops. This camera is easier, certainly, but hardly a breakthrough. Well, it is color, I'll give you that.
It appears that they are using a Canon EF or EF-s mount, but Canon is missing in the list of sponsors (Nokia, Adobe Systems, Kodak, and Hewlett-Packard). So they either reverse-engined the communication protocle between the lens and the camera, or they just skip that part all together. Either way, it's not a completely open source camera unless lens manufacturers open up their mount designs.
This kit is FREE open source for the Cannon Powershot, with many of the features mentioned in the article, including HDR. Download it onto a cf flash, and it replaces the Cannon OS. Many amazing images 1/50,000 milkdrop captures, night scenes etc can be found at http://chdk.wikia.com/wiki/CHDK
This sounds like an academic trying to make a name for himself again by labeling something that already exists with his own label. "Computational photography"? Well, how exactly did digital photography ever work without that?
Open source camera OS? Nice try, but the reason manufacturers haven't standardized on anything yet is because the technology keeps changing.
However, FWIW, Canon cameras effectively can be reprogrammed using the CHDK firmware.
When I see "Computational Photography", I think of the flatcam, a button-sized wafer with a photon-sensing surface. No lens, it instead computes the image of its surroundings. Described in fictional "Michaelmas" by Algis J. Budrys.
... once they have infected the camera with their spyware, is leave the camera collecting images constantly, looking for any personal identifying, security, or financial info, and send it over to their servers in a foreign country when network access is available.
now we need to go OSS in diesel cars
it is about time.
..That's what I read. Must be early in the morning.
Ermm, Just where, exactly, is the source? Links to CAD designs, specs, software, etc? As far as following the Stanford links is concerned, I can't see how this project can be labeled "Open Source" without this...
What I would really love is a CCD or CMOS without bayer color matrix nor antialiasing filter. This camera would be limited to black and white photography (or studio pack shot with 3 exposures behind R,B,G filters), but I expect the result would be outstanding. At the moment, we're fighting with slightly fuzzy shots (thanks to the AA filter) to recreate true pixels intensity after they've been distorted by various digital process. There's been one digital b&w camera, made by kodak. It's said the production number was 80, but from reviews, images were already gorgeous with 6 Mpix 10 years ago. Today, bayer matrix and AA filters are glued on the chip in the manufacturing process, and it's impossible to get rid of it afterwards.
Some cameras already use technologies to optimize the dynamic range e.g. using Apical solutions: http://www.dpreview.com/news/0903/09031801apical.asp not really like multiple shots with different exposures, but still very effective. Moreover, I prefer to leave such things to the post-processing phase of my work flow. Still nice that the camera is open, I hate manufacturers issuing dozen of new cameras every six months with very small increments in the feature set every time.
The camera does alignment and bracketing of an exposure series on-site. That would be really neat and much cheaper than current HDR sensors. At the moment I need to do this offline using Hugin and QtPfsGui.
I have a Samsung SGH G-800 phone. It has 5 megapixel camera and optical zoom to 3x (digital zoom to 6x). The whole phone cost about 300 euros a year ago. I'm sure you could get one for significantly less these days or alternatively spend the same money on a phone with a lot better quality camera. (I think I've seen one with 8 megapixel camera a while back)
Those aren't as good as actual cameras, of course. The flash is pretty weak and without it the shutter speed needs to be so slow that pictures get very easily less clear unless you put some effort into taking it... So they aren't quite there yet.
However, they've come a LONG way from what they used to be a few years ago. I used to think "Why would anyone want a camera to their cellphone? Those are so low quality that I couldn't really use it for anything..." but that isn't true anymore. I think it is safe to say that given only a few more years they will be at the level where nobody (except professional photographers, of course) will have any interest in owning any other camera.
On another note, an open source camera will be very well received by the astronomy community who have had to deal with non-configurable equipment for years.
*** Don't be dull.***
Free oftware is important, but o are open tandards... a Four irds mount, sD or Compact Flah torage, TIFF/EP 6 or Adobe DNG output...
Leandro Guimarães Faria Corcete DUTRA
DA, DBA, SysAdmin, Data Modeller
GNU Project, Debian GNU/Lin
Wouldn't the life be a lot better, if there weren't any evil, scheming, lying manufacturers to begin with? Seriously — whatever a commune of happy altruistic enthusiast can not create, can be created by a friendly government agency...
In Soviet Washington the swamp drains you.
If you look at the picasa album of pictures taken with the Frankencamera (linked from TFA through their homepage), you'll notice an incredible amount of chroma noise and banding. The caption ("can you PS camera do better ?") is ridiculous. I would be shamed if my PS produced that crap.
If you could build a printer yourself, it would be more than ten times slower than a commercial printer, probably have ten times poorer resolution, and cost more than ten times as much.
The DIY crowd has wisely skipped over 2D printers, and moved directly to 3D fabricators.
The first time I read the title I thought it said computational pornography.
craigslist is a centralized network of online communities, featuring free online classified advertisements â" with sections devoted to jobs, housing, personals, for sale, services, community, gigs, résumés, and discussion forums.
craiglistadposting
What about an Arduino-style platform where you have a standard base, and based on what you want you can add on components (such as a range finder or a GPS receiver or beyond-visible-light spectrum sensors or time-dilation modules or flux capacitors)?
Notice the url, at the end, says "apply"? This means Nikon gets to dictate what you can and cannot do with that SDK. I know it is the fashion these days amongst developers to hand over all control of their own software to someone else (cough... iPhone ... cough) but seriously are you that willing to give up your freedom just so you can use a fashionable platform?