After some real-life testing, accelerometer mode works only in very low light, as the accelerometer produces values at maximum 100Hz. Thus when the shutter speed is fast enough, the difference between two consecutive frames returns zero and the photo is snapped right away. I will try to fix that.
Digital image stabilization using accelerometer, on N900?
Very interesting stuff, thanks a lot for this. I wonder, are there any things, that are present in fCam (Maemo), yet lacking in rawcam? Also, do you know "lowlight" - a fCam derrivative, that takes low-light images, by shotting two frames, quickly - one with low exposure and high iso, and one with opposite setting - and combining them?
I think, that accelerometer stabilization mixed with above method could produce even better results (or not, if time between frames would be too long). What do ya think?
Edit: Same applies to "HDR picture" - another fCam derrivative, that takes few frames and combines them into HDR image. I wonder, if it could benefit for accelerometer stabilization, too? Both are FOSS, BTW.
Yes I sometimes noticed this and I was debating if I should crank up the exposure a bit before capturing, but that would affect various devices differently. In normal conditions this difference shouldn't be too big, so I'm inclined to say, learn your device and adjust likewise, or later in software.
This happens even in professional SLR's where the screen (or various computer screens as a matter of fact) display the image a bit differently.
The accelerometer stablization hasn't made it to the N900 yet but it will (as soon as the autobuilder is back up). Also you can expect some more stabilization options too.
Fcamera still has some features that ρcam doesn't, like hdr capture.
Thanks for the 16:9 option, I really appreciate it!!
Remember I told you about these weird lines I had before? Well , I'm almost sure it is the result of some kind of software conflict with your app and another one (even though I'm not using any).
The app works fine for a couple of days and then these horrible lines appear again.
The only solution I found was to reinstall the app.
Do you have any ideas what could cause these artefacts?
It's really weird, please try to pinpoint it, as I won't be able to look into it if I can't reproduce it. You say that uninstalling and reinstalling fixes the problem?
Maybe try deleting the .rawcam folder from /home/user rawcam.conf file from /home/user/.config/oob/, (settings will be reset)
ρCam does nothing but save new pictures in jpg and dng format in MyDocs/DCIM (no API calls or anything, it would be the same if you just copied a picture there yourself)
It is possible that the existence of dng images in DCIM breaks something. If disabling DNG save from settings solves the problem then I can change the location that the DNG files are being saved
On the other hand the breakage might occur every time a big file is written and tracker tries to read it and create a preview.
