Notices


Reply
Thread Tools
Posts: 9 | Thanked: 18 times | Joined on Sep 2012
#131
Yaay!
Can't wait for the 16:9 option.

Also, I noticed the photo is covered in weird horizontal lines (usually when I shoot in dark areas). No idea what they are.

Oh, and one more photo taken with your amazing app.
 

The Following 8 Users Say Thank You to PhilG13 For This Useful Post:
Posts: 112 | Thanked: 92 times | Joined on Nov 2010
#132
Hi qwazix,

Thanks for the nice app.

A small bug is present in fremantle version, If I close the lens cover to exit "pcam" after taking picture, I cannot run the slandered camera-UI afterwords, it gives internal error "camera" application closed.

But above doesn't occur when I end "pcam" with ctrl+backspace after taking picture.

Please ignore if this was reported earlier.

//nkirk
 

The Following 3 Users Say Thank You to nkirk For This Useful Post:
qwazix's Avatar
Moderator | Posts: 2,622 | Thanked: 5,447 times | Joined on Jan 2010
#133
Thanks, I'll look into it.
__________________
Proud coding competition 2012 winner: ρcam
My other apps: speedcrunch N9 N900 Jollacontactlaunchtimenow

Nemo UX blog: Grog
My website: qwazix.com
My job: oob
 

The Following 3 Users Say Thank You to qwazix For This Useful Post:
Posts: 115 | Thanked: 98 times | Joined on Aug 2011
#134
Can anyone who has Nokia N9 help me to post one (or all) of these?

Please check the value not from the app while taking a picture, but from the produced image.
  • What is the maximum exposure using manual exposure?
  • What is the maximum value of the ISO/Gain using manual ISO?
  • What is the minimum distance from the object to the lens using manual focus?

I'm asking for this because there are some difference between Nokia N900 and Nokia N9 sensor/lens FCam API while the CameraParameters.cpp in the source code is same.

Thank you very much!
 

The Following 3 Users Say Thank You to AWasisto For This Useful Post:
Posts: 115 | Thanked: 98 times | Joined on Aug 2011
#135
Example...

According to the "Sensor.h" FCam API of N900 ...
...
virtual int maxExposure() const {return 2489140;}
...
and N9 ...
...
virtual int maxExposure() const {return 109458;}
...
It means N900 longest exposure is about 2.5 second and N9 about 0.1 second.

In the "CameraParameters.h" of the application's source code written ...
...
str.sprintf("%ds", (int)(val+0.5));
...
float right = 1.0f;
...
The code shows that we can set the exposure up to "1s". Of course we can do it on N900 because its max exposure about 2.5s. But can we do that on N9 while its max exposure about 0.1s?
 

The Following User Says Thank You to AWasisto For This Useful Post:
qwazix's Avatar
Moderator | Posts: 2,622 | Thanked: 5,447 times | Joined on Jan 2010
#136
Interesting...

I had seen this value but I missed a digit and thought that it was 1s instead of 0.1s so I coded the max to 1s (by hand, not using maxExposure() ) and the result clearly shows that the resulting image with 1s exposure is brighter than the image with 1/10s exposure. (Also it is visible on-screen that the frames last for more than 0.1s - frames on screen are just regular frames, only 854x480 instead of 8MP) On the other hand there may be the explanation why really low light images are darker in the resulting image than in the viewfinder, but it still doesn't explain why 1/1 is brighter than 1/10. If the camera somehow capped the exposure, all photos above 1/10 should look the same.
__________________
Proud coding competition 2012 winner: ρcam
My other apps: speedcrunch N9 N900 Jollacontactlaunchtimenow

Nemo UX blog: Grog
My website: qwazix.com
My job: oob
 

The Following 4 Users Say Thank You to qwazix For This Useful Post:
Posts: 397 | Thanked: 185 times | Joined on Oct 2011
#137
Hi, great app. Had fun playing with manual shutter speed control. However, the JPG file it produced seemed way off the natural colour. As attached here shows. Does the phone take in DNG and converts to JPG later on?

1st picture is JPEG by the phone. Dynamic range suffers. Colour seemed unnatural.


2nd picture is DNG converted to JPG via Picasa on PC. Way better colour.
 

The Following User Says Thank You to kai_en For This Useful Post:
qwazix's Avatar
Moderator | Posts: 2,622 | Thanked: 5,447 times | Joined on Jan 2010
#138
DNG do not store white balance information. It's up to the software to decide how to translate color. Increased dynamic range is one of the great pro's of shooting in RAW (RAW stores 16bit of color data in each channel vs 8bit in jpeg) Now picasa clearly does it's work to obtain a good result when converting to jpg - think of it as using autofix, but with much more data to start with).

The bottom line is, if you want the best possible quality, shoot in raw.
__________________
Proud coding competition 2012 winner: ρcam
My other apps: speedcrunch N9 N900 Jollacontactlaunchtimenow

Nemo UX blog: Grog
My website: qwazix.com
My job: oob
 
Posts: 397 | Thanked: 185 times | Joined on Oct 2011
#139
Thank for the explaination bcoz I rarely see such big difference comparing jpeg and raw produced by a camera. It's unfortunate that N9 can't process DNG on the fly, could only view the files when I'm on my computer.
 
qwazix's Avatar
Moderator | Posts: 2,622 | Thanked: 5,447 times | Joined on Jan 2010
#140
You can use white balance, to tune your jpg's, and it won't affect the raw capture, so that you get closer to what you want for viewing on the phone. When you get back on the pc you still get full control.
Anyway try this beforehand just in case Im mistaken and WB does affect DNG, but I'm pretty sure it doesn't.

Of course that will not improve the dynamic range, but it's something.
__________________
Proud coding competition 2012 winner: ρcam
My other apps: speedcrunch N9 N900 Jollacontactlaunchtimenow

Nemo UX blog: Grog
My website: qwazix.com
My job: oob
 

The Following User Says Thank You to qwazix For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 15:04.