![]() |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Quote:
Hijacking threads with off topic issues doesn't help anyone. No other person is experiencing the listed issues above. I recommend you reflash and start a fresh if you are having so much trouble. |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Quote:
|
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Quote:
I have just put one thread explaining my issue and it was removed so can you please help me to find the solution why the camera is not working or saving properly |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Quote:
You can accept thgat the camera-ui2 issue is not the first kind. So, reflash and see if that fixes it. Then install CSSU and see if camera-ui2 works, before installing anything else. Then install other things. See if camera-ui2 works etc. That way you learn what your device likes and what not. I have CSSU-testing & thumb, KP52, fcam and blessn900 installed and camera-ui2 works for me. |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Quote:
I have reflashed five times before and all went fine with camera and other functions when i install the cssu again or reinstall it from backup menu it makes issues and getting stuck and not saving taken photos i have tried to reinstall stock camera but no use so please advice |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Not directly related to camera2-ui (also affect camera-ui per se), but couldn't think of better place to bring it to experts:
Anyone got diea WTF? http://talk.maemo.org/showpost.php?p...&postcount=284 http://talk.maemo.org/showpost.php?p...&postcount=281 Why the hell just *installing* fCam drivers changes the way *stock* camera exposes pictures? /Estel |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Is possible to associate some key for autofocus?
Because my N900 got wet and camera button is dead. So I have the only one way to capture images - with this app. |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
I have the latest version of CSSU installed by don't seem able to use the features described in this thread (eg key shortcuts). Is there something I need to do to select this UI over stock?
|
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Nope, should be available for you already. Are you using CSSU-Testing (or thumb)?
CSSU-Stable is severely outdated, and putting politics away, I would never recommend anyone to use it. /Estel |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Ah, no, I'm on stable. Mainly as my N900 is my main device and I'm somewhat loath to use anything that's less than stable...
Which version of CSSU /would/ you recommend? |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
I use CSSU-Thumb, which is CSSu-Testing compiled for thumb + sometimes, more bleeeding-edge versions of some packages (although, considered safe for use).
Hoever, while CSSu-Thumb is latest and greatest re N900's performance, it require kernel containing approriate fixes, and at least slight understanding what the whole thumb thing is all about. If you don't feel confident with it, and/or don't have time to read upon it and learn what it is about, you should be perfectly safe using CSSU-Testing. In perfect world, the Stable version you're using would be perfect for your use case - but in reality it is extremely poorly maintained (lack of people interested in it, versus Testing, which leaves individuals immersed in Maemo to rather shallow level, as Stable maintainers), updated "once in a great bell", thus, as you noticed yourself, severely outdated, lacking major improvements and functionalities. /Estel |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
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 Code:
gst-launch v4l2src num-buffers=1 ! dspjpegenc encoding-quality=0-100! filesink location=test.jpg Setting Code:
[imageenc] Bug N3: Setting Code:
[filter-caps] I can prove all these 3 bugs if needed. |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
As requested in http://talk.maemo.org/showthread.php...41#post1371341 I took not 1, but even 3 pictures with my N900 (CSSU Stable - 21.2011.38-1Smaemo6.1, kp52, camera-ui 1.1.29.1+0m5). Here are the pictures:All settings on "Auto", first two were made from 15-20 cm, third from ~30 cm.
|
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
here is one taken with CSSU-T:
http://farm4.staticflickr.com/3757/9...120bf29d_o.jpg This was taken with stock camera but I also observed that there's a difference in the exposure of images with and without the fcam driver. There is a tendency for the images to overexpose when fcam is installed and the white balance also seems affected (in my own experience). I don't know how that affects stock camera behaviour/processing but that is what I observed which is somewhat reflected in the opinion of other people here. http://talk.maemo.org/showpost.php?p...postcount=1046 |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
yup fcam drivers mess with camera its very annoying
|
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
I uninstalled the fcam and I still get slightly overexposed shots..
And when i try to underexpose a shot, the viewfinder gets black and the camera app turns off. Any suggestions? IF shots are needed I'll provide them. PS I managed to get a few underexposed shots with Auto ISO but if i put ISO to 100, I get the problems mentioned above. :( And I use my N900 for macro so it really is annoying to not have good contrast and blown out highlights. EDIT: I'm using CSSU-Testing. |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Quote:
In my experience the only ev failure is -0,5. iso 100 is very insensitive so the screen may look dark if lighting is sub-optimal. App closing not known to me. |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
The reboot didn't solve anything (I rebooted it in the first place)
So I must underexpose almost all the time. IT's ok if I don't change the ISO. |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Did you get any change in exposure behaviour with the removal of blessn900/fcam? IOW are you saying changed but it still sucks or there is no difference at all.
The -0,5 ev failure was a biggie for me as IME it is the most used and so I use fcamera and blessn900 mostly. |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
I didn't get any change whatsoever.
And the difference between -0.5 and -1 is really big. |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Quote:
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:
|
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Quote:
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 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 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:
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:
Code:
/* FIXME: once camera bin has support for quality, use proper API. */ |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
I'm more interested, why the hell installing fCam drivers change exposure of stock camera-ui and camera-ui2 photos? Any technical explanation to this phenomena?
/Estel |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Once again I found camera-ui2 not finishing videos and leaving them corrupt. Should I upload the video?
|
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Is there a fix for the slow launch of camera-ui2 ?
|
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Seems that only way to refocus during recording is to press camera button half-way.
If continuous autofocus is not possible, maybe option to refocus after n seconds? Even focus button on display makes refocusing lot easier as it not easy to half-press camera button when you use some case on your phone. |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Quote:
Sometimes the videos would finish, but most of the time they don't after pressing stop video recording. Then when I try to close the camera UI I get "Camera is not responding". I would appreciate any hints to solve this issue as I cannot use video recording anymore. Thanks. |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
I found a workaround (that works for me) to finish the videos and thus avoid camera UI freezing when stopping video recording: instead of stopping the video with stop button, press display to exit full screen and then press upper left corner to minimize camera. At this moment camera enters in standby and the video recording stops correctly. So?
|
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Seems like tons of bugs (counting already existing ones), and camera-ui2 doesn't seem to be maintained anymore, sadly. Anyone with coding skills willing to pick it up?
Seriously, it's so broken in so many places, that if not for HD video recording being allowed by replacement camera-ui only (in convenient way, at least), I would opt for removing it from CSSU. /Estel |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Quote:
https://bugs.maemo.org/buglist.cgi?q...arch=camera-ui |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
You're absolutely right, I'll try to prepare list of known issues and do my own tests to check if I can reproduce all of them, then submit list via BMO. Well, as time permits anyway :|
It would be great to see our little FOSS camera-ui purged of (at least critical) bugs, so I encourage others to do the same (you will probably get to it faster than I could). /Estel |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
I have an idea how to improve camera-ui. A script could be run before and after recording (e.g. to automatically OC the device for HD recording)
I might code and make a merge request, but 1. When should be the system(...) call made 2. Where should the scripts be located? |
All times are GMT. The time now is 16:37. |
vBulletin® Version 3.8.8