A4000IS porting thread - page 4 - DryOS Development - CHDK Forum supplierdeeply

A4000IS porting thread

  • 205 Replies
  • 50027 Views
Re: A4000IS porting thread
« Reply #30 on: 09 / March / 2013, 12:40:13 »
Advertisements
I had experimented with it minimum 3 hours, until now I only found some minor issues regarding the osd.
It is a minor issue and I will explain it :

imagine the new menu ( the OSD or the ALT menu) as a (image ) layer,
well,this ALT menu it appears on top of the original information displayed (as it should be, I supose),
the problem is the (auto)focus rectangle is ¨shrouding¨or deleting part of the ALT menu,
also the original  info displayed is deleting part of the ALT menu

A 20 percent of the DNG´s are trash.....I mean that   you can not even guess how was the original picture
              - I don t remember if this happend when shooting brackets or in normal use   

I´ve tried the bracketing, wich seem to be working fine



The new paralel operating system  is USABLE ( thank you again ) , ooo , and never crashed NEVER blocked or anything similar

*

Offline nafraf

  • *****
  • 1308
Re: A4000IS porting thread
« Reply #31 on: 09 / March / 2013, 12:53:40 »
imagine the new menu ( the OSD or the ALT menu) as a (image ) layer,
well,this ALT menu it appears on top of the original information displayed (as it should be, I supose),
the problem is the (auto)focus rectangle is ¨shrouding¨or deleting part of the ALT menu,
also the original  info displayed is deleting part of the ALT menu
It's normal... see comments here: http://chdk.setepontos.com/index.php?topic=8450.msg96389#msg96389

Quote
A 20 percent of the DNG´s are trash.....I mean that   you can not even guess how was the original picture
              - I don t remember if this happend when shooting brackets or in normal use   
Do you have the same problem if you save RAW as CRW?
What is the mode that you are using? AUTO?  P?

Re: A4000IS porting thread
« Reply #32 on: 12 / March / 2013, 07:06:33 »
Quote from: nafraf
I'll send you a private message with the link to a new version.  Please test it and report.
could i also have the latest chdk for the 101a firmware? cheers,

*

Offline nafraf

  • *****
  • 1308
Re: A4000IS porting thread
« Reply #33 on: 12 / March / 2013, 12:38:54 »
Quote from: nafraf
I'll send you a private message with the link to a new version.  Please test it and report.
could i also have the latest chdk for the 101a firmware? cheers,
I sent you a PM with the link to CHDK for A4000 101a.
To load it, it is necessary to use bootable sd card method.

To start, please try the test scripts listed in http://chdk.wikia.com/wiki/Testing

Thanks


Re: A4000IS porting thread
« Reply #34 on: 16 / March / 2013, 15:04:33 »
Comparing the EXIF data in the JPG and DNG images, I see that the Focal Length is sometimes incorrect in the DNG files.  For example, I took five shots at various zoom levels (from lowest to highest), and I got the following focal lengths recorded in the JPG and DNG files respectively: (5.0, 6.9, 10.7,  24.0, 40.0) and (5.0, 6.9, 10.7, 13.4, 13.4).  The label on the camera states that the focal length goes from 5.0 to 40.0.  I have no idea if this problem is specific to the A4000, or if it is a problem with CHDK in general.

Re: A4000IS porting thread
« Reply #35 on: 17 / March / 2013, 21:47:34 »
I took several hundred shots today with a couple of A4000's, and I didn't see any massive corruption in the DNG files.  I have the 101b firmware in the cameras, so perhaps the other poster's problems are because of older firmware versions.

I did see an increasing number of black pixels in the DNG files as I took more and more shots.  I was using a 500W halogen work lamp to do the lighting, and it was pretty bright.  When I turned one of the cameras on again much later and took another shot, the number of black pixels was much lower.  Looking at the JPG files produced by the camera, I don't see those black pixels there.  I don't know whether that's because the JPG output has some kind of smoothing automatically applied, or if the production code for the DNG file is at fault.  The black pixels are in the same place from shot to shot, except that more appear as time goes on.   I'm a newbie with this kind of stuff.  Is this normal behaviour for cheap point'n'shoot cameras?  Should I wait longer between shots (I took each shot soon after the last was saved)?

Edit:  the bad pixels aren't necessarily black, they just looked that way after I post-processed the DNG file.  They are still bad, though.
« Last Edit: 17 / March / 2013, 21:59:44 by rkomar »

*

Offline reyalp

  • ******
  • 13363
Re: A4000IS porting thread
« Reply #36 on: 18 / March / 2013, 00:40:11 »
I did see an increasing number of black pixels in the DNG files as I took more and more shots.  I was using a 500W halogen work lamp to do the lighting, and it was pretty bright.  When I turned one of the cameras on again much later and took another shot, the number of black pixels was much lower.
If you are using DNG version 1.3, then bad pixels are not interpolated over in the DNG. Instead, a DNG 1.3 feature is used to tell the DNG software which pixel values are bad. Unfortunately, most non-adobe software does not understand this feature, so you will see dark spots. The spots aren't actually back, because it's an individual R, G or B element that is bad. When it's de-bayered, you will see the remaining colors.

If you use DNG version 1.1, the bid pixels will be interpolated over when the shot is taken. To enable this, you must fist create badpixel.bin

Quote
When I turned one of the cameras on again much later and took another shot, the number of black pixels was much lower.
Many cameras have multiple bad pixel maps. It's likely that the number of bad pixels increases as sensor temperature goes up. If you go the DNG 1.1. route, it's probably a good idea to let the camera warm up before generating badpixel.bin. You can enable the sensor temperature display to check. Recording video should be a good way of warming it up.

Quote
Looking at the JPG files produced by the camera, I don't see those black pixels there.
The pixels that show up as black in the DNG are the ones known to the canon firmware to be bad. When the jpeg is created, the canon firmware interpolates over them.
Don't forget what the H stands for.

Re: A4000IS porting thread
« Reply #37 on: 18 / March / 2013, 01:56:36 »
Thanks reyalp, everything you say sounds right.  I've been using ufraw to convert the DNG files to more mainstream formats (PNG or PPM), and the man page doesn't seem to suggest any support for bad pixel correction.  The light I'm using also shines on the camera (I can feel it warming up as I use it), so I don't doubt that the sensor is getting hotter.  I'll play around with the DNG version number (I have been using DNG 1.3 up until now) to see if it helps.  Is the bad pixel information in the 1.3 DNG file openly specified?  It might be worthwhile looking at ufraw to see if support for that can be incorporated.


*

Offline reyalp

  • ******
  • 13363
Re: A4000IS porting thread
« Reply #38 on: 18 / March / 2013, 03:10:07 »
Thanks reyalp, everything you say sounds right.  I've been using ufraw to convert the DNG files to more mainstream formats (PNG or PPM), and the man page doesn't seem to suggest any support for bad pixel correction.  The light I'm using also shines on the camera (I can feel it warming up as I use it), so I don't doubt that the sensor is getting hotter.  I'll play around with the DNG version number (I have been using DNG 1.3 up until now) to see if it helps.  Is the bad pixel information in the 1.3 DNG file openly specified?  It might be worthwhile looking at ufraw to see if support for that can be incorporated.
For DNG v1.3, CHDK uses DNG "opcodes",  which are part of the DNG 1.3 specification. (see chapter 7 "Opcode List Processing"  FixBadPixelsConstant)

I believe ufraw uses dcraw under the hood, so that probably where opcode support would need to be added. Having this supported in dcraw would be great for CHDK, since many other programs also use dcraw.

If you want to convert your existing DNGs, the adobe DNG validator included in the DNG SDK will convert to tiff, with badpixels patched.

DNG specs and SDK can be downloaded from http://www.adobe.com/products/photoshop/extend.displayTab2.html
Don't forget what the H stands for.

Re: A4000IS porting thread
« Reply #39 on: 18 / March / 2013, 03:32:10 »
Thanks for the link.  I'm using Linux as my desktop, and can't easily run the Adobe software for converting the DNG files.  I'll have a look at the ufraw source code to see if there's something I can do there to help out.  There are dcraw files there, but it looks like they have been adapted to C++, and I'm not sure if modifications would be easy to backport upstream.

 

Related Topics