Notices
Page 107 of 114 « First 97105106 107 108109 Last »
Reply
Thread Tools
handaxe is offline handaxe
2013-09-04 , 12:46
Posts: 1,378 | Thanked: 1,604 times | Joined on Jun 2010 @ Göteborg, Sweden
#1061
Originally Posted by Half-Life_4_Life View Post
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.
Last edited by handaxe; 2013-09-07 at 23:22.
 

The Following 4 Users Say Thank You to handaxe For This Useful Post:
vetsin is offline vetsin
2013-09-07 , 19:42
Posts: 535 | Thanked: 598 times | Joined on Apr 2011 @ Republic of the Philippines
#1062
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?
 

The Following 4 Users Say Thank You to vetsin For This Useful Post:
nokiabot's Avatar
nokiabot is offline nokiabot
2013-09-08 , 04:16
Posts: 1,974 | Thanked: 1,834 times | Joined on Mar 2013 @ india
#1063
post them please i also get a bright spot in middle specially in macro mode. thumb and fcam drivers installed
 

The Following 2 Users Say Thank You to nokiabot For This Useful Post:
vetsin is offline vetsin
2013-09-08 , 17:43
Posts: 535 | Thanked: 598 times | Joined on Apr 2011 @ Republic of the Philippines
#1064
Ok. Dunno how this can be useful though.
First: Stock Camera on Thumb2 (with FCam Installed)


Second: Stock Camera on Thumb2 (FCam uninstalled, phone restarted)


Third: Stock Camera on PR1.3 (no FCam installed)


Fourth: Stock Camera on Thumb2 (no FCam installed)


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/
Last edited by vetsin; 2013-09-08 at 17:52.
 

The Following 4 Users Say Thank You to vetsin For This Useful Post:
tanago's Avatar
tanago is offline tanago
2013-09-08 , 17:51
Posts: 215 | Thanked: 448 times | Joined on Aug 2012 @ Burgas, Bulgaria
#1065
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.
 

The Following 5 Users Say Thank You to tanago For This Useful Post:
pali is offline pali
2013-09-08 , 18:01
Posts: 2,154 | Thanked: 8,464 times | Joined on May 2010
#1066
Originally Posted by tanago View Post
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 ^^^
 

The Following 8 Users Say Thank You to pali For This Useful Post:
tanago's Avatar
tanago is offline tanago
2013-09-08 , 19:13
Posts: 215 | Thanked: 448 times | Joined on Aug 2012 @ Burgas, Bulgaria
#1067
Originally Posted by pali View Post
Originally Posted by tanago View Post
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.
 

The Following 9 Users Say Thank You to tanago For This Useful Post:
nicolai's Avatar
nicolai is offline nicolai
2013-09-09 , 10:19
Posts: 1,637 | Thanked: 4,424 times | Joined on Apr 2009 @ Germany
#1068
Originally Posted by pali View Post
@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.
__________________
my contributions:
Desktop Clock Widget|Calendar Home Widget|Lens Cover Reminder|ConnectNow|Scout|App Search Widget|ProfilesX|
Desktop-Switcher|SMS-Messageblocker

-Donate-
 

The Following 3 Users Say Thank You to nicolai For This Useful Post:
vi_ is offline vi_
2013-09-09 , 10:53
Posts: 1,680 | Thanked: 3,685 times | Joined on Jan 2011
#1069
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.
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
 

The Following 7 Users Say Thank You to vi_ For This Useful Post:
misiak is offline misiak
2013-09-09 , 11:03
Posts: 804 | Thanked: 1,598 times | Joined on Feb 2010 @ Gdynia, Poland
#1070
Originally Posted by nicolai View 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.
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...
 

The Following User Says Thank You to misiak For This Useful Post:
Reply
Page 107 of 114 « First 97105106 107 108109 Last »

Tags
camera-ui, fremantle

« Previous Thread | Next Thread »

 
Forum Jump


All times are GMT. The time now is 00:54.

Contact Us - Home - Archive - Top