A590IS porting...

whim

@ewavr

Does that mean that if my CHDK binary already has settings for CAM_ACTIVE_AREA that it will use
these to crop the CRW that i'm shooting ???

@dvip

thanks, but due to my evident total lack of understanding of what CAM_ACTIVE_AREA_x2 & y2 mean, i can only
build you a binary if you supply data in a form i can grasp, like ( x1, y1, x2, y2 )

cheers,

wim

whoever

dcraw recognizes CHDK raw files by their size, and by size only, since they are truly raw so to say. Thus, A590 crw's are recognized as A720, as they are the same size, and the corresponding margins are silently assumed. Yo have to recompile dcraw with zero margins for this filesize, in order that it shows the fuul image.

dvip

@whim

X1 = 10, Y2 = 13, X2 = 3292, Y2 = 2471

ewavr

whim
Does that mean that if my CHDK binary already has settings for CAM_ACTIVE_AREA that it will use
these to crop the CRW that i'm shooting ???

No, crop settings for a620 are located inside dcraw.exe, which cannot distinguish a710's raw from a620's raw.

reyalp

ewavr
Hmm, if I convert CRW from a710, no black borders in tiff file. Because dcraw crops image before converting to tiff using settings from other camera (a620).

Yes, it turns out dcraw doesn't have a "just turn it to 8 or 16 bit and don't touch anything else" option.

Now that I think about it, dcraw also interpolates over 0 value pixels no matter what AFAIK, so it will smear over the borders (mostly down and left).

whim

dvip
@whim

X1 = 10, Y2 = 13, X2 = 3292, Y2 = 2471

Sorry dvip, here it is: http://drop.io/chdkshellbeta/asset/chdk-a590-101b-0-9-8-822-10-13-3292-2471-zip

cheers,

wim

dvip

@whim,
With CHDK-a590-101b-0.9.8-822(@10-13-3292-2471).zip
the camera won't even turn on. So I'm back to
CHDK-a590-101b-0.9.8-822(6-6-style).zip.

whim

dvip
@whim,
With CHDK-a590-101b-0.9.8-822(@10-13-3292-2471).zip
the camera won't even turn on. So I'm back to
CHDK-a590-101b-0.9.8-822(6-6-style).zip.

i tested it, this time (if it boots, that is) http://drop.io/chdkshellbeta/asset/chdk-a590-101b-0-9-8-822-10-13-style-zip

sorry again,

wim

dvip

@whim, the same, the camera won't turn on with it.

whim

dvip
@whim, the same, the camera won't turn on with it.

That truly weird - is this only the last 2 versions i posted ? I mean, does yesterday's 6-6 still work ? Does the cam boot
'normal Canon style' if you remove write lock ?
Me, i just copied the diskboot.bin over previous version and have just retested it booting in both play & shoot mode;
i've also verified the time stamp, Oct 27, 22:47

keep me posted,

wim

dvip

Whim,
Yes, it's weird. Even 6-6 from yesterday doesn't work now
either.

I tested all of them again and even deleted Cchdk.cfg and
badpixel.bin to see if that was the problem but nothing.

The cam works fine 'normal Canon style', no problem there. And
I installed CHDK a590-101b-0.9.8-822-full back again and it
works fine too.

It just doesn't want to turn on and boot with the diskboot.bin we
are testing. Feel free to send another one or let me know if I
need to delete or reset something with the new diskboot.bin.

whim

@dvip

maybe check your card in CardTricks, if it's still bootable, or try a fresh format ?
off to sleep now, maybe that brings more ideas ...

later

wim

dvip

@whim,
I'll give that a try. But if it was a boot problem
it wouldn't boot and work with the a590-101b-0.9.8-822-full.zip
at http://mighty-hoernsche.de/
It works with that one without problems.

Good night!

reyalp

I get 10 pixels top border, 12 pixel right border, 36 pixels left border 0 pixels bottom border.

Method: covert image to 8 bit with new tool. Open 8 bit as raw in photoshop (gimp should work too). Zoom way in, use the selection tool to select the border, look in the info window for height or width of selction.

So i think:

#define CAM_ACTIVE_AREA_X1 12
#define CAM_ACTIVE_AREA_Y1 10
#define CAM_ACTIVE_AREA_X2 3330
#define CAM_ACTIVE_AREA_Y2 2480

edit: i sux at teh maths

From the DNG spec:

ActiveArea
...
Default
0, 0, ImageLength, ImageWidth
...
Description
This rectangle defines the active (non-masked) pixels of the sensor.

Tool will be added to trunk tools.

edit:
attached a build for 101b, please report if this looks correct.

dvip

@reyap,
It boots fine and it looks better.

For it to work in my A590IS0-101b it still needs this trim to
make the borders disappear:

4 Pixels @left, 3 Pixels @Top, 6 Pixels @right

I think a bigger trim is needed for whim's A590IS0-101b, so we can go
with his because it will work with mine as well.

whim

I think a bigger trim is needed for whim's A590IS0-101b, so we can go
with his because it will work with mine as well.

no need to worry, for the few pics i ever postprocess i'll live with whatever magic RawTherapee applies, borderwise
reyalp's version appears fine for me - no black borders. Also, all that programs like PS (or even GIMP)
do for me is make me ill - i can think of more fun things to do with my time

what interests me is why my builds failed to work on your cam, while they work fine on mine - i'll do some more
checking (like downloading them of the drop, and then trying, etc.) Will post if i 'succeed' to make it fail 😁
reyalps' is compiled with GCC 3.4.6 BTW, mine with GCC 4.4.0

cheers,

wim

dvip

@whim, feel free to post more until we figure out
what the problem is... we'll see If it is the compiler or what...
I can always test them at night.

whim

@dvip

download still works like a charm for me, compiler version also seems unlikely - Autobuild also uses 4.4.0
here's 2 x trunk824, modified with reyalp's CAM_ACTIVE_AREA's, and compiled with 346 and 440:

[links removed, files too]

cheers,

wim

reyalp

dvip
I think a bigger trim is needed for whim's A590IS0-101b, so we can go
with his because it will work with mine as well.

This cannot be correct. All cameras of given model should have the same active area, this is a hardware feature.

4 Pixels @left, 3 Pixels @Top, 6 Pixels @right

How exactly are you determining this ? What software are you using ?

dvip

>All cameras of given model should
>have the same active area, this is a hardware feature.

@reyalp,
There are two borders, the outer one which is black,
and another one parallel to it which seems to be
touching the active area and it is not well defined. You can see
them both in the raw file that whim posted. When I compare his
borders with mine his are bigger, so
if we crop using his file as a guide it should also work for mine.

I'm not sure if it is hardware/software what is causing
the difference. Technically the active area + other
hardware should be the same.

>How exactly are you determining this ? What software are you
>using ?

To count pixels and see if the borders are present I use
IrfanView. It's what I got. It is possible that IrfanView is not showing
everything. I think IrfanView's raw engine is dcraw based.

« Previous Page Next Page »