maemo.org - Talk - View Single Post - camera-ui2 (now a part of CSSU) (updated 09. May)

	nicolai	2011-03-21 , 12:42
	Posts: 1,637 \| Thanked: 4,424 times \| Joined on Apr 2009 @ Germany	#139

Hi geohsia,

thank you for reporting this.

Originally Posted by geohsia

Hi,
Not sure what type of bugs I'm supposed to report.

All bug reports are helpful. I can not test all use cases myself.
So I am happy for any help.

Originally Posted by geohsia

In RAW mode and (no pictures to review) mode the app freezes after taking a photo (the display is back) and returns a) if you switch to another app and then switch back b) close and open the lens cover.

Ah, yes, the RAW mode is coupled with the preview mode as I am using
the preview image as the embedded preview for the raw file :-)
The app may get confused when preview mode is disabled and the
preview image arrives from the camera api.

Originally Posted by geohsia

Also in RAW mode there are instances when it says its using ISO 800 and I think its actually higher. I try to use the same exposure for Camera-UI2 as FCAM and FCAM would be at ISO 1600/ 3200 and Camera-UI2 says its at ISO 800.

Yes, as I wrote, the image tags for the raw file are not complete
some are missing and some are wrong (I hardcoded 800 as ISO-level
for all raw files)

Originally Posted by geohsia

Is there a way to display the shutter speed? I know it was already mentioned that shutter speed was impossible to set but if there is a way to show it so I can see it that would be great. In the DNG the shutter speed is not displaying properly.

The problem with the image tags for the raw file is, the camera
capture parameter like iso and shutter speed are there, but
not directly accessible from my application. I searched the last
days to find a way to capture these parameters.
The more technical explanation:
The camera api is based on gstreamer. There are multiple
gstreamer elements involved. A camera source (gstv4l2camsrc)
reads the camera capture parameter and send this data
as gstevent. This events go through the gstpipeline
get caught by the metdatamux which converts them to exiftag
data for the filesink.
Until yesterday I couldn't find a way to catch this data. I searched
for a way to monitor or listen for this gstevents.
But it seems to be a uncommen requirement. Finally I found
this method gst_pad_add_event_probe()
which is exactly what I need.

Nicolai

Quote & Reply |

The Following 4 Users Say Thank You to nicolai For This Useful Post:
fw190, geohsia, handaxe, Mentalist Traceur