Re: Semi-successful Bayer-mode capture from internal camera
Are you using gstreamer or are you just accessing the camera with v4l? If you do not change the parameters V4L will just use the current settings that were set by the last program to use it. -Peter Benjamin M. Schwartz wrote: HUGE BUG: 1. After each reboot YOU MUST OPEN Record (or any other program that uses gstreamer to access the camera) BEFORE RUNNING bayertest.py. Otherwise, your images will be squished into the left half of the field. I have no idea why. It's pretty weird. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Semi-successful Bayer-mode capture from internal camera
On Thu, 2008-02-28 at 16:25 -0800, Peter Krenesky wrote: Are you using gstreamer or are you just accessing the camera with v4l? If you do not change the parameters V4L will just use the current settings that were set by the last program to use it. -Peter I'm using pyvideograb, which is based on the v4l2 example code. This may represent a bug in that code. I am not sure how consistent this behavior really is. I intend to switch to gstreamer once OLPC upgrades to a version of gstreamer that supports Bayer mode (bug #4580) --Ben ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Semi-successful Bayer-mode capture from internal camera
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have created a stepwise procedure for experimenting with Bayer mode capture: 1. su - 2. yum install python-imaging 3. wget http://dev.laptop.org/~bemasc/bayertest.tar.gz 4. tar xzvf bayertest.tar.gz 5. cd bayertest 6. python bayertest.py bayertest.py will produce a file output.png containing your picture, after interpolation by dcraw. Sample Raw bayer: http://dev.laptop.org/~bemasc/storefront_input.png Sample Interpolated: http://dev.laptop.org/~bemasc/storefront_output.png HUGE BUG: 1. After each reboot YOU MUST OPEN Record (or any other program that uses gstreamer to access the camera) BEFORE RUNNING bayertest.py. Otherwise, your images will be squished into the left half of the field. I have no idea why. It's pretty weird. Other bugs: 2. The included, patched version of dcraw assumes a bayer-grid orientation that does not match the camera's. Therefore, the temporary files are rotated by 180 degrees, and then rotated back afterwards. This is only an annoyance if you want to look at the raw data yourself. 3. The rightmost 4 pixels of each line are just repeats. I have no idea why. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHuJl2UJT6e6HFtqQRAkvoAJ4qm4++SAic3QUZD+FQdK+rPmQ9aQCeLqQB znVoSQZpGuP/OPt2UnJMHZc= =yNK/ -END PGP SIGNATURE- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Semi-successful Bayer-mode capture from internal camera
From this resource: http://www.quickcamteam.net/documentation/how-to/how-to-enable-raw-streaming-on-logitech-webcams If Bayer images are captured in any resolution lower than the maximum resolution supported by the sensor, clipping occurs. For example, if the sensor supports 1280x960 and a 960x720 image is recorded, the frame will appear clipped at the right and lower borders. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
