View Single Post
Posts: 5 | Thanked: 1 time | Joined on Jan 2010 @ Paris, France
#15
Originally Posted by abbra View Post
If you are programming sort of person, look at http://maemo.gitorious.org/maemo-mul...n/gst-camera.c example. In handle_element_message() it shows how to handle RAW data buffer coming from v4l2camsrc, and on_chkbtnRawMsg_toggled() shows how to trigger v4l2camsrc to produce that RAW buffer.

RAW data is 10-bit BAYER (two bytes per element) if I'm not mistaken.
I managed to build, execute, and debug the example_camera.c application that you mention, using ESBox, on my N900.

When I check the raw message checkbox, some sort of environment variable is set to CAMSRC_PUBLISH_RAW=True somehow. However when I take a snapshot afterwards, the execution flow in handle_element_message keeps going through the .rgb save path, and never goes through .raw path.

All the shots I could take with the raw checkbox checked are thus in .rgb format. I made a short python script to open, read, and dump the data into a PIL image: it is indeed an RGB 888 format, already demosaiced/debayerized.

So it seems I am not able to get any RAW really raw data. What am I missing ? The application GUI is a little messy and one or two elements seem to be a little going out of the screen, is there any other GUI element I should see that would trigger raw format ?

Thanks.