![]() |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Quote:
|
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Quote:
Just a frame(full screen) which pops up by pressing a buton in menu, or settings and for that frame we can select any arbitrary png image with transparency. for example that image containing a nice curved line and the rest transparent , so I could draw that line on a paper looking on the phone screen while drawing with hand. i hope u understand. |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Quote:
video-capture-height it seems, these parameters don't exist in maemo 5s camerabin |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Quote:
I was hoping for a something like a slightly more accurate/useable feature similar to the white-balance correction, as well as something like the B setting most SLRs have. It would be genius if something could be lifted from Meego for this, now I know the relevant functions are in fact in sealed binaries. Re: colour correction Is there an intrinsic fault with the light sensor that favours shorter wavelength light, thus reducing the amount of red in the image? Or does the image pipeline cull the bpp to suit the screen, or something else that reduces quality? Is it a hardware or software porblem? I ask because I might see whether I can knock up a lightweight post-process tool to enrich the red values, which might be less workable if the image is RGB565 or reduced in some other way. |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
I mean the API, not the programs using the API; make your program use the fcam API to tweak the camera parameters.
|
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
camera-ui is not meant to be fCam based - it's replacement for stock camera GUI. fCam API's are Open, AFAIK, so everyone is free to write "uber" camera application using those. Still, there is no rationale for making camera-ui fCam only (thus, limiting available options for users - now everyone interested in fCam - like me - can use it together with camera-ui2, or even write something new for fCam drivers).
|
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
If it's intended to replace the original, shouldn't all efforts be done to include all the functionalities of the original regardless of which path is taken in the background, so that people won't need to pass on using it 'cause it's missing stuff?
|
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Where in the original You have shutter speed control?... AFAIK camera-ui2 (now camera-ui) implements all options from original + indeed many enhancements, that are do-able from GUI.
fCam drivers are totally different topic and while I *do* like them very much, there is no place for them in camera-ui replacement. We *don't* want do-it-all hybride here, that will fail due to over-specific-dependant-chain. You know old linux mantra - write programs that do one thing at once, but do it best. While it's not *literally* true nowadays, it stil got rationale - why to create behemot, when anyone interested can write useful, independent program using fCam drivers, and anyone interested can use it (or not, therefore is not forced to install fCam drivers with CSSU, which would not be the case if camera-ui start implement fCam dependencies). Anyway, it's quite academic talk, cause I'm pretty sure Nicolai don't even consider rewriting camera-ui to *such* degree. Hopefully... (fixme if I'm wrong). |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Click on the wrench, you got iso sensitivity and exposure compensation.
|
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Quote:
|
| All times are GMT. The time now is 06:43. |
vBulletin® Version 3.8.8