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

I noticed, that photos took in RAW mode via CSSU'ish camera-ui lack info about camera white balance (while every other info is present - for example, ufraw properly detect camera 2.8/5.s characteristic, and can use it to adjust photo geometry - great stuff!). As result, every RAW white balance must be adjusted manually (by user or by program algorithms), without any use for white balance calculated by camera software during photo-taking. No big deal, still, it would be great to have it.

Is there any way to "fix" (as if something that wasn't there before could be fixed even more ;) ) it, or is it some kind of limitation? While taking RAW's via fcam, white balance is preserved, but I know that fcam use different drivers, so no idea if it's related.

/Estel

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

I am not an expert on raw image data, but
isn't the whitebalance stuff a postprocessing step
after capturing the raw data?

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

so after upgrading cssui to T1.1 i need to downgrade cameraui from v8 to v7 posted 4.11.11 for hd recording ? or is v8 ok to keep ?

update... yes downgrade for hd recording options :)

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

Right, and that gives you dependency error when running apt-get. Is there a way to ignore the dependency error?

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

AFAIK, not without changing the CSSU's dependencies. (see https://bugs.maemo.org/show_bug.cgi?id=12203)

In the meantime you can try upgrading for any apt action and manually downgrading again afterwards.

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

I see, well its a workaround atleast.
Or I stick with ver. 8 untill 7 is uppgraded to 9 or something.

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

Rest assured, it is.

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

Why dont you integrate the camera-ui with HD resolutions to CSSU?

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

Or can we have the updated camera-ui + HD?

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

Stay tuned ;)

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

It is, but camera software - also one in our N900 - got some predefined WB "presets" (light bulb, sunny, cloudy etc), that are literally values of "gain" ratio between R,G, and B. I'm also not specialist in such things, but somehow, this values can be exported with RAW - maybe as EXIF data, or whatsnot?

Before someone start to mock me - I know that these things are implemented in software (like UFRaw) as profiles, but *somehow8 people contributing values for so many models are able to get them from camera itself, right? At least, that is how I understand from:
http://ufraw.sourceforge.net/Contribute.html
Still, I don't have a clue, how to get it from N900-created RAw's (I got "no camera white balance data available"), and more complicated things, like getting rid of vignette, isn't covered on this instruction at all.

When camera-ui take RAW image, it also automatically save post-rendered .jpg (nice feature, by the way). Is there any way to "check" white balance (temperature), and other adjustment values used there? It would be very useful, for post-processing using - for example - UFRAW, on desktop computer or N900 itself via Easy Debian.

Now, we can apply manual white-balance, etc, nut no matter how hard I try, overall quality of my resulted image (from RAW processing) is much worse than automatically created .jpg. It's mainly result of white balance *and* vignette. Thinking about that, the latter effect is IMO much more PITA to properly correct, than white balance. I tried every single setting about "vignetting" in ufraw, to no avail. Probably, I'm just noob :p

Anyway, getting values used by N900 software to create jpg's would be awesome - cause, in other aspects, RAW's give much more opportunities, to create high-quality images. It's just those two twings (white balance and vignette) that ruin final image. ho ever, I remember some discussion - probably, even on this very thread - about nokian's .jpg correction algorithms being closed source - that would be sad news, making RAW capture only a curiosity, without possibility to get really great images (and our N900 camera *is* able to take them, seriously!). Unless, someone reverse-engineer optimal correction values for our camera optics, and publish them.

/Estel

// Edit

The ideal situations, would be to have proper correction values for our optic characteristics (vignette etc), + basic white balance presets, then, sending them to UFRAw (or other Open Source RAW processing tool), to have it included automatically.

This way, when we import our RAW, we got "standard" must-have correction applied automatically, then, we can manually adjust whatever we want, to suit our needs. That would result in super-quality images, that no one expect from N900.

This is, how it works for plentora of digital cameras - even ones from manufacturers, that aren't very friendly to Open Source idea (when it comes to RAW and post-processing documenting), to say at least. does anyone know how people get correction values from such cameras? I don't believe every single one is properly reverse-engineered. - really.

Without such methods - knowing our "Nokia friends" and they openness - superb quality images from N900 are in real of dreams :( And that's quite annoying, cause we actually got hardware capable of doing so (at least, kicking a** in comparison to *any* other "phone" camera-, even over-advertised N8/N9 one)

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

I am! =)
Thank you very much!

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

...did we get anywhere with the geotagging option constantly getting turned off?

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

To me that does not work for video. When I give the display record gets focus, you see a picture but the rest of the GUI disappears and I can not leave without killing the application.

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

Forget it, I'm so stupid that I crushed the camera-ui update that comes with the latest CSSU.

Sorry for the confusion.

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

What do you mean?

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

Vignetting? what are you talking about, the optical phenomenon or the artistic effect that is sometimes used? I am not aware that the N900 introduces this when capturing images. If yes, maybe it's simple pixel vignetting?

(Vignetting shows as a reduction of image's brightness / saturation at the image's corners /sides, in difference to the image center, for those that don't know what we're talking 'bout)

Vignetting (will not differentiate between the types here) mostly occurs if:
- (extreme) wide-angle is used so that the lens' body mechanically blocks light from reaching the sensor (49mm lens adapter on Canon Powershot G1 instead of proper 52mm one, f.e.)
- the sensor size doesn't match up with the chosen lens diameter / image circle (2/3" sensor used with S-mount lenses, f.e.)

And i still don't get what you want with whitebalance metadata ion the RAW. Do you want to compensate for individual sensor gain and noise characteristics? The Color filter array data?

EDIt: Btw, my second-favorite denoiser sw provides an user-submitted dcraw profile:
http://www.neatimage.com/noise-profi.../download.html

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

I whant to ask something...

Its better to add higher bitrates on videos, because bitrate is the quality factor...

Who care... HD 720P with only 8-10mbps bitrate is ****... its like take a photo then add 85% compression... will look like ****.

If can record 960x480, at stable 30 FPS at 15-18mbps that should be perfect, no pixelations.

Is there any way to modify manually the bitrate?

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

I don't take many pictures...but when I do, the Geotagging option is almost always disabled (I'd say always, but I can't be 100% certain), even though I always enable it.

There were posts on TMO about this problem that were related to profiles (using the stock UI as well, I believe), but the threads seemed to dry up. I'm still experiencing it with cameraui-2 however.

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

The geotagging options aren't preserved after reboot.
I don't know how the stock camera-ui behaves.

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

I think that's the request... that they be preserved across reboot. Most people don't just causally turn it on and expect it to turn off sometime later because of a reboot. (Though the stock camera-ui behaved just that way, as does your version.)

I personally would like to set it so that by default, any picture I take has geotags enabled, regardless of if I just rebooted or not. Would it be possible to store this in a gconf based value and on camera-ui startup force that value, instead of forcing an "off" value. That would allow the app to normally retain the expected behavior of the original program, and allow those of us that want to force/tweak this to default to always on the ability to do that.

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

It looks like the new cssu installs 1.1.29.2+0cssu8 version of camera-ui, so if I reinstall your version (cssu7), I get 'unmet dependencies' error when I try to use apt-get later.
Can somebody make the new package with the same version as the cssu?

Thanks,
Ivan

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

Is there a menu option for raw files? I see people are using them but how do you enable it.

had a small glitch with latest cssu T1.1 version. opened camera shutter, took one pic, showed result fine. problem was when it went to take the next picture. screen changed back to preview, took another picture, heard a slighty odd noise from camera mechanism and app crashed. reopened app, tried another picture but crashed again. closed camera shutter, reopened and tried again worked fine.

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

Keyboard shortcut only.
R/r enable/disable raw image mode (raw files have the
normal image name with .dng extension)

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

Digital Negative as in the Adobe specification?

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

yes,

nicolai

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

I`ll wait for the cssu update with the 720p integrated.Lot`s of steps to do it again from the start.I`ve lost the HD option when I upgraded to the latest CSSU.

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

I am not saying that waiting for a cssu update is a bad idea, but it is not that much work to regain the HD option. This is what I did, and it worked:

as root, cd to the directory where you saved the three files for freemangordon's HD version of camera-ui2, and type
(maybe only reinstalling the camera-ui .deb is sufficient, I did not test)

I suppose that does introduce the 'unmet dependencies' error ivanrajkovic mentioned, but I have not seen that yet.

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

@maartenmk
you are correct, from my experience: only have to reinstall camera-ui, introduces the unmet dependencies error, but it works.
still its a bore since there are other programs that require the fix of the unmet dependences, like OMP, so you have to fix it, upgrade the app, and downgrade camera-UI once again...

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

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

:(..way too advanced for me i am affraid..

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

@ALL

until freemangordon release a new camera-ui (cssu8)
i did what don_flacon suggested
repacked the old camera-ui with version cssu8
for people who has limited experience

although i recommend ignoring dpkg message and wait the next release //EDIT : except if you are using FAM

download from attachments

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

Ignoring doesn't help when you want to update several packages with FAM ;)

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

after dpkg of 3 files posted from freemangordon, capturing any kind of video is impossible.. after 1s it freezes and adios.. taking pictures too.. :confused:

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

Did you reboot your device? If not it will solve the issue.

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

yes, i rebooted the device, twice, but nothing. the screen is black after 1s and nothing happens.

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

Hmm... strange... today i decided to try out the Harmattan DSP packages. Anyway, i reverted back to the manually extracted ones, but i'm still unable to capture videos... this happened after installation of libgdigi* and camera-ui.

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

had some major issues with playing anykind of video, not just 720p, but after reinstal the omap deb files nothing changed(video delay).. so now i'm not able to take video(pictures yes, but with problem).. :(

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

@don-falcone
I'll post sample of raw vignette-affected image, and it's .jpg counterpart (saving automatically by camera-ui, so it's exactly same frame).

@Nicolai or other camera-ui devs
Can I suggest adding 1 sec option to time-delay shutter trigger?

Rationale: N900 doesn't have IR receiver, so it's not possible to trigger shutter remotely. On the other hand, using HW or on-screen button, can cause vibration and "ruin" a little photo took with N900 mounted to tripod.

This can be avoided using time delayed trigger, but shortest available option is 3 sec (then 6 if I recall correctly). In many cases, it's too long to catch thing that we want to photograph. 1 second would be enough to physically stabilize device (itself) after touching it's screen, but short enough for most photos.

Of course, best thing would be to make time delayed trigger customizable, instead of currently-present pre-defined options, but even plain adding of 1 sec as option (for good start) would be a feature-saver.

/Estel

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

estel: how about using a bluetooth keyboard to trigger? i do see your point though, sounds like a good idea.