A3000IS poring thread - page 11 - DryOS Development - CHDK Forum
« previous next »
Pages: 1 ... 6 7 8 9 10 [11] 12 13 14 15   Go Down

A3000IS poring thread

  • 142 Replies
  • 56426 Views
*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: A3000IS poring thread
« Reply #100 on: 27 / November / 2011, 00:49:05 »
Advertisements
Quote from: greggyh on 26 / November / 2011, 23:34:56
Hello,

I recently installed build a3000-100d-0.9.9-1425 on my A3000.  I'm unable to open DNG files produced with this version using ACR or Lightroom.  I get a generic "don't support this camera" error.  I downloaded and managed to build the dng_validate executable from the Adobe DNG SDK.  This utility informs me that the DefaultCropOrigin is invalid.

I haven't yet built CHDK, but from inspection I think I see a problem.  In chdk/platform/a3000/platform_camera.h there are the defines:

#define CAM_JPEG_WIDTH  3648
#define CAM_JPEG_HEIGHT 2736
#define CAM_ACTIVE_AREA_X1 8
#define CAM_ACTIVE_AREA_Y1 8
#define CAM_ACTIVE_AREA_X2 3616
#define CAM_ACTIVE_AREA_Y2 2736

These are used in dng.h to construct the crop origin:

#define CAM_DEFAULT_CROP_ORIGIN_W ((CAM_ACTIVE_AREA_X2-CAM_ACTIVE_AREA_X1-CAM_JPEG_WIDTH )/2)
#define CAM_DEFAULT_CROP_ORIGIN_H ((CAM_ACTIVE_AREA_Y2-CAM_ACTIVE_AREA_Y1-CAM_JPEG_HEIGHT)/2)

The JPEG width is larger than Active area X2-X1 (and Y2-Y1), so this computation underflows and returns 0xffffffec and 0xfffffffc for the crop origin width and height.

I don't know how to determine the active area numbers.  I made a guess at sensor size of 3720x2772 for dng4ps2, but don't know if those are correct or how to derive the active area.

Regards,
Greg

Those values definitely look wrong.

In DNG4PS-2 set:
- sensor size and jpeg size to 3720 x 2772
- x1, y1 to 0, 0
- x2, y2 to 3720 x 2772

This should convert a CRW from CHDK to a DNG using the full sensor (instead of cropping out the unused bits).
You should be able to load this into an editor and then find the correct X1, X2, Y1 & Y2 values.
X1, Y1 should be the first usable pixel, X2, Y2 should be the last usable pixel + 1.
All four values must be even so increase X1, Y1 and decrease X2, Y2 if needed.

Once the active area is set the JPEG image is cropped from the center of the active area if the JPEG size is smaller than the active area size.

Post the correct values and I can update the source code.

If this doesn't work upload a CHDK RAW file to a file share and post a link and I'll take a look.

Phil.
Logged
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)
*

Offline greggyh

  • *
  • 5
Re: A3000IS poring thread
« Reply #101 on: 27 / November / 2011, 14:06:50 »
The usable area seems to be:

X1 = 0
Y1 = 0
X2 = 3700
Y2 = 2772

That is there are 20 pixels on the right edge that are black or garbage.  The left edge looks clean and full height is also clean.  I could be convinced that the last pixel or two on the right edge are a little dodgy even at 3700, but then there are plenty to be clipped to get down to 3648x2736.
Logged
*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: A3000IS poring thread
« Reply #102 on: 28 / November / 2011, 02:29:11 »
Quote from: greggyh on 27 / November / 2011, 14:06:50
The usable area seems to be:

X1 = 0
Y1 = 0
X2 = 3700
Y2 = 2772

That is there are 20 pixels on the right edge that are black or garbage.  The left edge looks clean and full height is also clean.  I could be convinced that the last pixel or two on the right edge are a little dodgy even at 3700, but then there are plenty to be clipped to get down to 3648x2736.

I've updated the active area with your values. This should be in build 1435 which will be on the autobuild server within a few hours.

Let me know if it still has problems.

Phil.
Logged
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)
*

Offline greggyh

  • *
  • 5
Re: A3000IS poring thread
« Reply #103 on: 28 / November / 2011, 10:11:25 »
I tested build 1436.  It works great with Adobe Camera Raw 6.5

Thank you!
Logged
*

Offline r-care

  • *
  • 3
Re: A3000IS poring thread
« Reply #104 on: 29 / November / 2011, 14:59:04 »
Quote from: r-care on 21 / November / 2011, 09:43:44
Hi there. i am using the 1.00c version. 1st, i tried download from SVN server. Not working. after pressed "update" the screen turn off and nothing happened. then i tried all version, same, nothing work. Finally i decided the 1st release which ERR99 post on February. ERR99, can u make update for 1.00c?

also, sorry for my lame question, can i make this chdk auto boot in my camera?

Hi, any other 1.00c user here can verify latest version on SVN working?
Logged
*

Offline reyalp

  • ******
  • 14080
Re: A3000IS poring thread
« Reply #105 on: 28 / December / 2018, 22:08:44 »
@cagiva reported this port has very little free RAM (~300KB in playback, without lua running)

Attached is a test build for A3000 100d ARAM with enabled and some additional memory savings. Please check that it works, report the free memory from memory info, and check whether you still have the problem with KAP_UAV

edit:
attachment deleted, bad build.
« Last Edit: 30 / December / 2018, 19:01:33 by reyalp »
Logged
Don't forget what the H stands for.
*

Offline cagiva

  • *
  • 33
Re: A3000IS poring thread
« Reply #106 on: 29 / December / 2018, 01:53:22 »
@reyalp, let me make sure I follow.  Are you asking me to replace the files in the two partitions of my SD card with the ones attached in your zip file?
Logged
*

Offline reyalp

  • ******
  • 14080
Re: A3000IS poring thread
« Reply #107 on: 29 / December / 2018, 01:58:51 »
Quote from: cagiva on 29 / December / 2018, 01:53:22
@reyalp, let me make sure I follow.  Are you asking me to replace the files in the two partitions of my SD card with the ones attached in your zip file?
Yes.

The DISKBOOT.BIN should go in the root of the small partition, and the CHDK directory should go on the large one. Overwrite existing files. PS.FI2 can go on both, but is only need if you load manually with firm update.

I believe stick has an option to install a manually downloaded build if you prefer that: http://www.zenoshrdlu.com/stick/stickx.html
Logged
Don't forget what the H stands for.
*

Offline cagiva

  • *
  • 33
Re: A3000IS poring thread
« Reply #108 on: 30 / December / 2018, 18:42:17 »
@reyalp, I used Stick 'manual' procedure to install your attached build, but the camera doesn't even power ON when I install your test image in the SD card.  I also copied them manually on top of the original release files, but same result (camera doesn't power ON).  However, if I install back either the 1.3 or 1.4 build (Stable or Trunk), then the camera powers ON fine, but of course I get the loading error when I try to run the kap_uav.lua script.

I'm testing this using two A3000IS cameras and two different SD card, but same behavior.  Other scripts like the interval.lua run perfectly fine.
« Last Edit: 30 / December / 2018, 19:00:42 by cagiva »
Logged
*

Offline reyalp

  • ******
  • 14080
Re: A3000IS poring thread
« Reply #109 on: 30 / December / 2018, 19:01:10 »
Quote from: cagiva on 30 / December / 2018, 18:42:17
@reyalp, I used Stick 'manual' procedure to install your attached build, but the camera doesn't even power ON when I install your test image in the SD card. 
Oops, looks like I messed up a critical part :-[. Try this one.

Thanks
Logged
Don't forget what the H stands for.
Pages: 1 ... 6 7 8 9 10 [11] 12 13 14 15   Go Up
« previous next »
 

Related Topics