Active Topics
-
[ANNOUNCE] MeeShop - new app store (8)
to Applications by Maemish - 3 hrs, 56 mins ago -
HTTP-401 Sfos-Builder when using /etc/ssu credentials (0)
to SailfishOS by insanelysexy - 8 hrs, 26 mins ago -
Longtime users: What device(s) are you using today? (54)
to General by ryu1 - 2 days, 13 hrs ago -
Registering (1)
to General by Halftux - 5 days, 6 hrs ago -
Applications Wishlist (55)
to Maemo 7 / Leste by sixwheeledbeast - 6 days, 8 hrs ago - more...
 |
|
2009-09-21
, 18:31
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#22
|
It's lardman's fault. He should have posted on my thread not this ancient, crusty thread.
And sorry, daperl, I haven't tested your scripts yet. My brain was refusing to go into "work" mode all weekend. It just wanted to sit around on the couch and drink beer.
And sorry, daperl, I haven't tested your scripts yet. My brain was refusing to go into "work" mode all weekend. It just wanted to sit around on the couch and drink beer.
__________________
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
|
|
2009-09-21
, 19:18
|
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#23
|
Sorry, I thought this was the thread you were talking about!
|
|
2009-09-21
, 20:10
|
|
Posts: 5,335 |
Thanked: 8,187 times |
Joined on Mar 2007
@ Pennsylvania, USA
|
#24
|
Originally Posted by qole
It's lardman's fault. He should have posted on my thread...
Originally Posted by lardman
Okay, enough of that; I've moved the posts to the proper, non-"crusty" thread. So, now you're all in the right place, but your side discussion about being in the wrong place will confound future readers.
Sorry, I thought this was the thread you were talking about!
__________________
maemo.org profile
maemo.org profile
| The Following User Says Thank You to sjgadsby For This Useful Post: | ||
|
|
2009-09-21
, 21:28
|
|
Posts: 196 |
Thanked: 141 times |
Joined on Aug 2007
|
#25
|
Originally Posted by sjgadsby
Like me
Okay, enough of that; I've moved the posts to the proper, non-"crusty" thread. So, now you're all in the right place, but your side discussion about being in the wrong place will confound future readers.
|
|
2009-09-21
, 22:51
|
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#26
|
So while we're at it, what are the thoughts on camera focusing?
There are v4l2 hooks there in ad5820.c iirc, and it looks like the camerabin component (or photography interface) can use them.
However as I'm currently writing in Python, that's not so great. There is the v4l2camsrc, which looks like it's linked to the above, but I'm not sure I can do anything with it (as it just appears as a source afaict).
Otherwise I'm considering talking to the ad5820 directly using ioctls, but then I need to work out how to pull in the isp_af functionality, or implement my own (which would be interesting, but ultimately a waste of time).
So, anyone have any bright ideas?
There are v4l2 hooks there in ad5820.c iirc, and it looks like the camerabin component (or photography interface) can use them.
However as I'm currently writing in Python, that's not so great. There is the v4l2camsrc, which looks like it's linked to the above, but I'm not sure I can do anything with it (as it just appears as a source afaict).
Otherwise I'm considering talking to the ad5820 directly using ioctls, but then I need to work out how to pull in the isp_af functionality, or implement my own (which would be interesting, but ultimately a waste of time).
So, anyone have any bright ideas?
|
|
2009-09-22
, 05:07
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#27
|
lardman: this is output from Fremantle VLC that you might find useful:
Code:
opening device '/dev/video0'
V4L2 device: omap3/et8ek8/ad5820/adp1653 using driver: omap3 (version: 0.0.0) on
the device has the capabilities: (X) Video Capure, ( ) Audio, ( ) Tuner
supported I/O methods are: ( ) Read/Write, (X) Streaming, ( ) Asynchronous
video input 0 (camera) has type: External analog input *
device supports chroma UYVY [UYVY, packed, UYVY]
device supports size 2592x1968
device supports size 1296x984
device supports size 864x656
device supports size 640x492
device supports chroma YUY2 [YUYV (YUV 4:2:2), packed, YUYV]
device supports size 2592x1968
device supports size 1296x984
device supports size 864x656
device supports size 640x492
device codec BA10 (Bayer10 (GrR/BGb)) not supported
'/dev/video0' is a video device
Extended control API supported by v4l2 driver
Available control: Brightness (980900)
integer control
valid values: 0 to 255 by steps of 1
default value: 0
current value: 0
Available control: Contrast (980901)
integer control
valid values: 0 to 255 by steps of 1
default value: 16
current value: 16
Available control: Exposure time [us] (980911)
integer control
valid values: 33 to 33132 by steps of 33
default value: 33132
current value: 33133
Available control: Gain [0.1 EV] (980913)
integer control
valid values: 0 to 40 by steps of 1
default value: 0
current value: 0
Available control: Color Effects (98091f)
menu control
0: None
1: B&W
2: Sepia
default value: 0
current value: 0
Available private control: Focus, Absolute (9a090a)
integer control
valid values: 0 to 1023 by steps of 1
default value: 0
current value: 79
Available private control: Flash strobe (9a090d)
button control
Available private control: Flash timeout [us] (9a090e)
integer control
valid values: 1000 to 500000 by steps of 54600
default value: 500000
current value: 500000
Available private control: Flash intensity (9a090f)
integer control
valid values: 12 to 19 by steps of 1
default value: 12
current value: 12
Available private control: Torch intensity (9a0910)
integer control
valid values: 0 to 1 by steps of 1
default value: 0
current value: 0
Available private control: Indicator intensity (9a0911)
integer control
valid values: 0 to 7 by steps of 1
default value: 0
current value: 0
Available private control: Test pattern mode (9a107e)
menu control
0: Normal
1: Vertical colorbar
2: Horizontal colorbar
3: Scale
4: Ramp
5: Small vertical colorbar
6: Small horizontal colorbar
7: Small scale
8: Small ramp
default value: 0
current value: 0
Available private control: Focus ramping time [us] (9a10af)
integer control
valid values: 0 to 3200 by steps of 50
default value: 0
current value: 0
Available private control: Focus ramping mode (9a10b0)
menu control
0: Linear ramp
1: 64/16 ramp
default value: 0
current value: 0
__________________
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
|
|
2009-09-22
, 08:56
|
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#28
|
Good, at least the focus components are available through v4l2 on the device. No auto focus there, but just altering it would be good as a starting point.
|
|
2009-09-22
, 09:25
|
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#29
|
Hmm, using v4l2camsrc, I get a frame which is 61440 in size.
Now that is 640 x 480 x 2
But the camera is not supposed to return that frame size, and also it seems an odd encoding, either you get a one-to-one YUV, or the U and V data are a 1/4 the size of the Y data, so I'd expect the total frame to be 640 x 480 x 1.5.
Though I guess there are other encodings available (and this seems to be the same one I saw before).
Perhaps it's just the fact it's morning
Indeed just morning. As the encoding is UYVY (or something like that), for every 2 Y pixels we have a total of 4*8 byes = 32bytes. 32/2 = 16bytes total per pixel -> the frame is twice the size of the resolution. Doh!
Last edited by lardman; 2009-09-22 at 10:09.
Now that is 640 x 480 x 2
But the camera is not supposed to return that frame size, and also it seems an odd encoding, either you get a one-to-one YUV, or the U and V data are a 1/4 the size of the Y data, so I'd expect the total frame to be 640 x 480 x 1.5.
Though I guess there are other encodings available (and this seems to be the same one I saw before).
Perhaps it's just the fact it's morning
Indeed just morning. As the encoding is UYVY (or something like that), for every 2 Y pixels we have a total of 4*8 byes = 32bytes. 32/2 = 16bytes total per pixel -> the frame is twice the size of the resolution. Doh!
Last edited by lardman; 2009-09-22 at 10:09.
|
|
2009-09-22
, 15:57
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#30
|
What does the line, "device codec BA10 (Bayer10 (GrR/BGb)) not supported" mean I wonder? What's Bayer10 (GrR/BGb)?
__________________
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
N9: Go white or go home