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

Alright, will do that. I'll follow this thread and see if I can be of further help testing stuff. I don't know why it doesn't work right now and I can't find proper log files, but let's see what the future brings. Thanks so far, also for all your efforts!

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

dspjpegenc -ok (default)
jpegenc -ok (saving seems faster)
ipp - camera is black
quality at 100% & 720p & kp52

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

Yes I dont know too where to search for log files according that bug. Thank you anyway :)

ipp combined with which jpg encoder? Did you restart the phone after editing the .conf file?

Also dspjpegenc doesnt have 'quality' property so it wont read 'quality=xx' setting only jpegenc will.
dspjpegenc has quality of 90. after doing a research about jpeg quality, more than 85 is invisible for the human eye. and more than 95 scales very much with file size while actual quality improvement is very very minor. For example quality 95 will produce 2mb photo, quality 100- 4mb while the comparison will show only a slight difference in the Baseline Image (in photoshop or any other software) which is completely invisible as i said for your eyes

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

ippjpegenc seems a little bit faster in saving and accesing saved photo(quality read in info 85,5)i think the speed is due using more cpu times i have seen seen this in cpu load applet
but ippdspjpegenc seems having more quality while zooming in and better compression , pictures are few kb smaller (also 85,5 ) read by photo details
I will stay with ippdsp for now
could you share your video profiles to test them?

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

Nope, the "best photo quality" we can achieve with camera-ui2 is by using "r" on keyboard, and saving them as RAW ;) They can be post-processed on N900 using EasyDebian and UFRaw, afterwards.

This way, one can entirely avoid mess with dropping dsp jpg encoder, keeping ability to shot quickly saved, good quality, small sized jpg's for casual photographs, while still having possibility to save best quality possible (tm), important photos as RAW.

/Estel

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

Well, I think it is me to blame for the crashing dspipp. Please try the attached libgstdsp.so to see if it makes any difference and report.

What is different with the one from the 720p thread is this https://gitorious.org/~freemangordon...41fe0bdd484aea commit.

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

Agreed. But the correction I struggle with (and the default Nokia camera does VERY well), is vignetting. Extremely difficult to iradicate that lighter centre of the pic.

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

Thanks, but that didn't fix it. Still the same behaviour:
First, taking a photo the camera application shows a black screen for a sec, then returns to picture taking mode, at the second picture, it shows the taken picture for a second, at the third picture it crashes. all files are at 0 bytes eventually. So that unfortunately didn't help.

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

Well, it is something else then, as I was able to take 10-15 photos in a row, with both dspjpegenc and jpegenc.

cssu-thumb 8.2 and Harmattan DSP codecs here.

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

Good Morning. I am also having CSSU-Thumb 8.2, but codec-wise everything is stock (except that one lib). I suppose the Harmattan DSP codecs are the ones from the 720 thread? If so, I'd try that and restate if it works now or not. Also, I still have v51 power kernel, but I suppose that shouldn't matter, should it?

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

Yea, it "haunted" me for ages too - until someone came with simple yet ingenious solution. The problem is caused by ultra-wide characteristic of our lens, and, surprisingly, method used for get rid of it for biiig DSLR wide lenses, works for us too. it is nearly impossible to get rid of while manually developing from RAW files, but simple, FOSS program "CornerFix" fixes that blue'ish vignetting automagicaly.

I can't find relevant TMO thread now, but just duckduckgo.com for "CornerFix", and you're home. I'm using it myself, and can confirm that it works for 100% - just like default Nokia raw developing. The best thing, is that it does is lossless'ly at RAW level - you put in a vignetted RAW, and get out another RAW, without vignette. Then, you can develop it whatever you want.

Only drawback is that, despite being FOSS it can't be compiled for N900 for some obscure reasons (I remember it vaguely - knowledgeable ones explained it in details, and it had something to do with it being written originally for Mac), so you need windoze or mac desktop for using it :(
---

I agree, though, that Nokia's automagic RAW developing algorithms are *very* good, in other parts too... It's pity, that they're (and always will be) closed source, as while doing it, Nokians have access to all data about camera module and lens characteristic. AFAIK, no one yet made effort to re-create perfect RAW developing template (for our camera characteristic) and share it with others. (BTW, no logical reason why Nokia is keeping it closed - it won't be useful for any other product, than 2 Nokia phones using this module type...).

As for me, the best I was able to get, were photos that have *some* aspects better than Nokia's photo (but others worse - easy to compare, if you instruct camera programs to save *both* RAW and jpg, at the same time). But, for doing so, I develop every photo by hand, focusing on aspects that I'm more interested in that particular photography.
---


But, should we use the "new" thing attached to your post (some fixes?), or is version from 720p thread still "best" one to use?

/Estel

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

@Estel: works either ways, the difference with the lib on 720p thread is only the commit I posted, which is irrelevant to 720p playback/recording or whatever. It is only for dspipp which is not used by default AFAIK.

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

Really sorry but I couldn't get a definitive answer on this. I saw it was mentioned way back in the thread but didn't get what I thought was a clear answer. I am like one of the previous posters and like no Noise Reduction on my photos. It seems like camera-ui2 has a better system for noise reduction than the stock camera however I could be imagining it. Noise reduction (AFAIK) reduces grain at the expense of resolution. I used to own a digital camera that used to have no noise reduction and it produced a lovely grainy quality on black and white photos, much like a grainy film does. Anyway, is there a way short of using FCAM and processing the images by hand of removing noise reduction altogether? I tried using the built-in JPEG codec (the jpegcodec instead of the dspjpegcodec) and it seems to make the noise reduction worse.

Any ideas and apologies if this has been done before. Please also understand I've a couple of really bad experiences with FCAM and the like with lockups needing reinstalls and so forth..

Thanks in advance for any replies

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

Tell me how the RAW capturing on N900 is any good for the average user? The need to fix the light center? The need of post-processing to achieve the needed result?

Dont answer those questions cuz there are no reasonable answers to them and please stop talking 'against' me, ty

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

Correct me if I'm wrong, but AIUI, noise reduction is applied at RAW -> JPEG developing oh photos, so if you use fCam's RAW (or camera-ui2 RAW's), you got photos without it. Then, using UfRAW (or any other RAW developing software you feel fancy), you may just *no* apply noise reduction.

Stop asking question, if you're dead to answers, at the very point of asking. If it's meant only to boost your ego, you could save it for yourself.

Anyway, your logic is "astonishing" - average user doesn't need RAWs, but he need 3-5 MB JPEG files (change from 95% quality to 100% quality for JPEG), without *any* benefits perceivable by naked eye? Really?

I imagine *most* N900 users as something more than ego-monkeys, who doesn't know how to use RAW to get photos developed the way they like it - yet, like to have 10x bigger JPEGs just for sake of using more space and feeling "I'm more cool, I got display called retina same quality photos that *must* be better, because they're bigger-sized jpeg's".

If you would do at least basic research (aka "read manual" ;) ) before posting your "awesome" advices, you would realize, that setting JPEG quality to 100% is as brainless as it gets - it turns out all JPEG optimizations, at the expense of file size, without *any* real-world gains.

/Estel

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

@Estel thanks for the feedback. When these threads get long I generally don't read them. I don't even really know the capability for camui2 (not read the manual so to speak). Yeah, just non noise reduced jpegs interest me. Many body of my quesion was really about is there a different level of NR on camui2? Or is it adjustable beyond processing a raw file.

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

Ok, I will have to explain like i'm explaining to retrds

I asked un-answer-able just to point your pointless logic

My logic?! l.o.l. that was funny... Tell me
situation1:you need to capture something instantly how fast and optimal it will be to:
need to open the shutter, launch the camera, open the keyboard, press r, focus if needed and after that whole procedure actually snap a photo?
situation2:you take a photo and you want to show it to smb.: How? the need of post-processing is simply limiting you.

then again for the jpeg quality read my previous post, Nº1003, where i very carefully explained jpeg quality so everybody can pick the best that suits them, aaand i dont think that 5mb per photo is too much when you have 32gb in a N900 and space for additional memory

RAWs for me are for 'show-off' persons, look my phone can capture raws, N900 is not a photocamera, its purpose is snap-and-go.

my advices are for the everyday user, who wants to enhance the fast methods of doing something, if you are not one, dont read my advices i dont make them for you to be happy, yes some people will prefer 100 quality than the default, actually my tutorial is to be able to change the default quality and not to set it to 100.

I was clear enough and i made my conclusion about you , i wont reply to your posts anymore

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

play nice children

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

imagine the situation if you bot had pistols in hand:D btw we already have raw for better quality though its a nuiance to process them on and off device:) so we should try to achive the better snap and go quality for normal photos and people:) anyway i like raw but at times snap and go is better and would be much better if it can be alterd a bit:)

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

if you really want best picture on device without raw editing, you might want to look at porting some automated tools, similar to cornerfix suggested earlier, and make a scipt to batch process the files. the default camera setting is only applying a series of image processing algorithms, so if you can replace them with your own preferred set. string them together in the correct order and problem solved. not sure off top of head if imagemagick could provide some routines you may find helpful.

i'm getting sick and tired of some of the petty squabbles, less than helpful comments, put downs for suggesting ideas and trolling thats going on in certain threads. especially from some people I would expect better behaviour from. part of me really wants a dev only section that needs access rights given to individual users.

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

I was recording videos in 720p with device overclocked to 250-805 or 250-900. After some time of recording I noticed an intense lag and stuttering on the screen or even video preview blackout. Example result video (unplayable - tried totem and vlc) is available here: http://ubuntuone.com/12RP2T8anMerGo7AXwNkd6

Why is it happening? Using kp52, cssu thumb (iirc 8.2 - latest). Video was saved to emmc, swap on mmc1. Swappolube swappiness modifiers applied. No speedpatch nor batterypatch.

Output of `dpkg -l | grep ^ii` attached

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

Sounds like what happens when the need for IO and memory ultimately catches up to the swappiness/etc. settings, maybe.

Can you log the events if they are reproducable -- camera-ui's messages and dmesg?

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

I'll try 10 ch

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

iirc the display framerate on the screen is not representative of the recorded. Recorded file takes precedence to displayed image.

Your file is missing any codec information/moov atom. I tried running it through https://github.com/ponchio/untrunc - using one of my HD files but no luck. Might be someway of getting the information out of it.

Theres also some suggestion here http://talk.maemo.org/showthread.php?t=84800

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

It looks like camera-ui2 got closed/crashed before saving of video file ended.

I've seen similar results once, when I recorded ~2 hours long concert - after stopping recording, camera-ui2 got frozen for ages (using 99% CPU), so after 30 minutes, I killed it. The result was video with screwed container - everything was saved in practice, but wrapping it into mp4 failed. I had to use mp4 video recovering tools (and even then, it wasn't possible to restore video with 100% correct framerate & co - despite fact, that technically, all frames were saved to disc. Yes, mp4 sucks.)

Summing it up - it seems to me, that camera-ui2 sometimes get stuck, and won't finish saving video properly, no matter how long time you'll give it, to do so. Probably, it can happen for both short and long recordings (but long ones have higher probability - warning, my subjective conclusion, not based on any real research).

/Estel

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

So, what I noticed: the time of recording when it happens if various. I tried to reproduce it, and after 10 mins nothing. There was a little stuttering on the preview even before. What's interesting: the video contained a lot of movement. (playing dogs). The ultrastutter and hang appeared when I quickly turned the device, so the area recorded was dramatically changed.

A couple of other observations: the timers (time avail., time elapsed) were stuttering too.

Maybe it's the compression-intensity related?

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

And something else: why am I sometimes getting 0 bytes images from camera-ui2?

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

etc/gdigicam edit config to false and reboot

It happened like that even before editing gdigicam.conf

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

do i need to have 720p files installed in my N900 in order to raise photo quality to 100% ? editing config file doesn't raise picture quality to 100%. any help ?

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

0kb image files from camera i haven't experienced as im recall, however i do get it A LOT from microb :(

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

I am sure you did not mean to imply you take pictures with microb :-)

Of substance: I have not seen zero size images either. Stuttering yes, even with 720p libs, but with kernel-config dsp it is way better than it was with stock.

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

Exactly my thoughts, and I'm still not sure what that supposed to mean - started to think that I'm slow-thinker :)

As for merit - I haven't seen 0 sized images from camera-ui2, either. 0 sized videos are different thing, they also appear, sometimes (but not sneaky - only during crashes of camera-ui(2), most likely, early in recording).

camera-ui2 is great re provided features, but being in CSSU, it could use some debugging love. It's one of those situations, where I'm really sorry, that my coding skills aren't up to the task, yet.

/Estel

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

i just meant i hadn't encountered problem with camera iirc. the only 0kb images i have are from microb downloads messing up.

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

Reboot fixes that

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

Yeah, just annoying as hell when you set it to download, leave the page and then can't find it again later when it messes up.

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

Hi,

It's kinda urgent, 'cause I can't leave the camera lens open for a long time.

While recording a 720p video the camera-ui2 froze. I can minimize it, but the timer, preview & everything is frozen.

Can I do anything with it?

Thanks

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

According to your recent posts(on the other threads too), you suffer from "frozen" stuff a lot. I'd recommend a full reflash of your device , both rootfs and EMMC ;)

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

These are problems that existed even before a full reflash, which i was forced to do some time ago. But such problems concerned photos, not videos. Though the way it looked like was exactly the same. I had to close the lens and the camera-ui2 doesn't close. But I have to leave today, so I can't let it run forever.

/ot: the problem with freezing of browser came back after reflash too

/edit: I noticed that camera-ui process take much RAM (20%) and an insignificant amount of CPU

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

Hello guys

scince the latest updates from cssu and am having trouble with both camera and pgs

- camera is getting freezed and stuck and sometimes taking pictures but not saving it.

gps is not working at all even the I have changed settings supl.google.com

I also removed the kerenl power 52 and returend it to stock kernel because it caused a lot of battery drain and issues

Can you please fix the cam and if not can i return it to camera ui 1 the stock version

thanks