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

maemo.org - Talk (https://talk.maemo.org/index.php)

- Multimedia (https://talk.maemo.org/forumdisplay.php?f=32)

- - camera-ui2 (now a part of CSSU) (updated 09. May) (https://talk.maemo.org/showthread.php?t=70870)

Re: camera-ui2 (now a part of CSSU) (updated 09. May)

Quote:

Originally Posted by Half-Life_4_Life (Post 1371995)

I didn't get any change whatsoever.
And the difference between -0.5 and -1 is really big.

That is strange as others see the difference. Let me check: you removed the fcamdrivers and not just the fcamera application?

The smallest effective ev difference is large because unlike -1,0 etc ev the setting -0,5 does nothing. For most cases a 1,0 ev change is too large.

Re: camera-ui2 (now a part of CSSU) (updated 09. May)

hi tanago!
i just reflashed my phone and i took pictures before flashing (i was on thumb with fcam), after (with stock everything), and after installing thumb. do you still need the pictures?

Re: camera-ui2 (now a part of CSSU) (updated 09. May)

post them please:) i also get a bright spot in middle specially in macro mode. thumb and fcam drivers installed

Re: camera-ui2 (now a part of CSSU) (updated 09. May)

Ok. Dunno how this can be useful though. :)
First: Stock Camera on Thumb2 (with FCam Installed)
http://farm4.staticflickr.com/3833/9...c8096ab2_o.jpg

Second: Stock Camera on Thumb2 (FCam uninstalled, phone restarted)
http://farm3.staticflickr.com/2883/9...30c7735f_o.jpg

Third: Stock Camera on PR1.3 (no FCam installed)
http://farm3.staticflickr.com/2809/9...956a406f_o.jpg

Fourth: Stock Camera on Thumb2 (no FCam installed)
http://farm4.staticflickr.com/3712/9...d67d8cc9_o.jpg

Question: How do I know camera ui version? (Didn't notice change in UI after flashing --> thumb2, was just busy pressing the shutter button EDIT: just read thread title, so I'm on camera-ui2 when I installed thumb)

Links:
1: http://www.flickr.com/photos/22568752@N03/9703625688/
2: http://www.flickr.com/photos/22568752@N03/9703621204/
3: http://www.flickr.com/photos/22568752@N03/9703615644/
4: http://www.flickr.com/photos/22568752@N03/9703611196/

Re: camera-ui2 (now a part of CSSU) (updated 09. May)

Thank you, vetsin, I dont need anymore pictures.

nokiabot, this bug maybe not camera-ui bug, sounds more like gdigicam bug for me. camera-ui is just the user interface(what you see on the screen), gdigicam is the pacage responsible for capturing photos and videos(what's under the hood)

I'm currently in a shortage of free time and cant work on improving camera-ui.

Re: camera-ui2 (now a part of CSSU) (updated 09. May)

Quote:

Originally Posted by tanago (Post 1371075)

Is somebody still working on camera-ui?

Bug N1: Quality of photos made with camera-ui is worse (more pixelized) than taking a photo with the following simple command line:

Code:

gst-launch v4l2src num-buffers=1 ! dspjpegenc ! filesink location=test.jpg

Bug N2:

Code:

gst-launch v4l2src num-buffers=1 ! dspjpegenc encoding-quality=0-100! filesink location=test.jpg

tunes compression quality.

Setting

Code:

[imageenc]

element=dspjpegenc

encoding-quality=0-100

in gdigicam-camerabin.conf does NOT work(may be related to gdigicam packages)

Bug N3:
Setting

Code:

[filter-caps]

tab in gdigicam-camerabin.conf does NOT work(may be related to gdigicam packages) and I can't change the default pixel format (UYVY) to (better) YUY2

I can prove all these 3 bugs if needed.

@nicolai: see this post ^^^

Re: camera-ui2 (now a part of CSSU) (updated 09. May)

Quote:

Originally Posted by pali (Post 1372942)

Quote:

Originally Posted by tanago (Post 1371075)

Is somebody still working on camera-ui?

Bug N1: Quality of photos made with camera-ui is worse (more pixelized) than taking a photo with the following simple command line:

Code:

gst-launch v4l2src num-buffers=1 ! dspjpegenc ! filesink location=test.jpg

Bug N2:

Code:

gst-launch v4l2src num-buffers=1 ! dspjpegenc encoding-quality=0-100! filesink location=test.jpg

tunes compression quality.

Setting

Code:

[imageenc]

element=dspjpegenc

encoding-quality=0-100

in gdigicam-camerabin.conf does NOT work(may be related to gdigicam packages)

Bug N3:
Setting

Code:

[filter-caps]

tab in gdigicam-camerabin.conf does NOT work(may be related to gdigicam packages) and I can't change the default pixel format (UYVY) to (better) YUY2

I can prove all these 3 bugs if needed.

@nicolai: see this post ^^^

after hours of reading the source codes and experimenting, what i found out:

Bug N1 was a user mistake, I was capturing at widescreen resolution (-.-)

Bug N2 is related to gdigicam package: the settings in gdigicam-camerabin.conf must be declarated in the source for them to work.

Let me explain in detail for those who dont know much about it:
We have (1)declarated properties in gdigicam package, (2)gstreamer element properties, (3) gdigicam-camerabin.conf properties settings

Examples:
Declarated properties in gdigicam are quality(for pictures) and bitrate(for videos)
Element properties - jpegenc properties (ALL available element properties can be obtained with

Code:

gst-inspect jpegenc

(you can see that there is a property named quality)
If we can match declarated properties and element properties then we can change their setting with the .conf file
We have such property (quality) so we can set it in the conf file.

About dspjpegenc:

Code:

gst-inspect dspjpegenc

We see that there is a property 'encoding-quality' which will alter jpeg compression level, but since there is no such property declared in gdigicam source code even if we set it using the .conf file it will NOT work.

Declared properties are very very few just 3-4 and every element has lots of properties. dspjpegenc's encoding-quality can be fixed 2 ways: declaring the property in gdigicam source, modifying the property name from 'encoding-quality' to 'quality'

Bug N3: thus every capture mode needs different "caps", "caps" are being set(by gdigicam package) before every capture of video or image, change of source code is needed to use the better setting.

Re: camera-ui2 (now a part of CSSU) (updated 09. May)

Quote:

Originally Posted by pali (Post 1372942)

@nicolai: see this post ^^^

Yes, just like tange already said.
http://gitorious.org/community-ssu/g...am-camerabin.c

has to properly parse the conf file for additional properties.

Re: camera-ui2 (now a part of CSSU) (updated 09. May)

The jpeg quality of dspjpegenc is hardcoded in libgstdsp (or something). You can set whatever you like in the gdigicam conf file, it will not do anything. IIRC, FMG set the quality to maximum in his 720p libgstdsp files.

If you are not using the 720p codecs your only option is to use the software jpeg encoder (jpegenc?). The software jpeg encoder respects the quality setting.

Re: camera-ui2 (now a part of CSSU) (updated 09. May)

Quote:

Originally Posted by nicolai (Post 1373082)

Yes, just like tange already said.
http://gitorious.org/community-ssu/g...am-camerabin.c

has to properly parse the conf file for additional properties.

So many FIXME's... Line 1364:

Code:

/* FIXME: once camera bin has support for quality, use proper API. */

is there something relevant to quality settings ignoring near that line? Just quickly looked at the sources and found that...