A3000IS poring thread - page 8 - DryOS Development - CHDK Forum supplierdeeply

A3000IS poring thread

  • 142 Replies
  • 30904 Views
*

Offline TT34

  • *
  • 12
    • PromEnergy Group, Ltd.
Re: A3000IS poring thread
« Reply #70 on: 10 / February / 2011, 15:09:01 »
Advertisements
Hi, Again.

Seems I can't open RAW files that my cam made. Photoshop is telling me that is not valid file format CR2 or CRW. There are params I should set in chdk to perform opening in PS? Or its FW bug?

*

Offline whim

  • ******
  • 2013
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: A3000IS poring thread
« Reply #71 on: 10 / February / 2011, 16:46:32 »
@TT34

In short: You will need to do some post processing to do so, or shoot as DNG.
Because a lot can be - and has been said about this, the forum dedicates
an entire board to Raw Shooting and Processing

have fun,

wim

Re: A3000IS poring thread
« Reply #72 on: 12 / February / 2011, 18:13:20 »
After some tests with my A3000IS 1.0C:

I was not able to activate DNG format option.
Always having a message

"Cannon load CHDK/badpixel.bin.
Please run
CHDK/SCRIPTS/TEST/badpixel.lua"

*

Offline ERR99

  • ****
  • 339
Re: A3000IS poring thread
« Reply #73 on: 13 / February / 2011, 02:36:36 »
Thanks for the fine answers.
I think I managed to run the script - here is the output romlog file.
Hope you can get something out of it.

Hmm, the ROMLOG show the same error message (ASSERT!! ReadFDir.c Line 442, Task name: FsIoNotifyTa0) what i got (sporadic) on my camera, its a error handling in the original Canon opendir function:

ROM:FFDF6214 opendir                                 ; CODE XREF: sub_FFD2BCF4+24p
ROM:FFDF6214                                         ; sub_FFDE312C+30p ...
ROM:FFDF6214
ROM:FFDF6214 var_20          = -0x20
ROM:FFDF6214
ROM:FFDF6214                 STMFD   SP!, {R3-R9,LR}
ROM:FFDF6218                 MOV     R6, R0
ROM:FFDF621C                 LDRB    R0, [R0]
ROM:FFDF6220                 BL      sub_FFC51190
ROM:FFDF6224                 MOV     R8, R0
ROM:FFDF6228                 BL      sub_FFC524C4
ROM:FFDF622C                 MOVS    R5, R0
ROM:FFDF6230                 BNE     loc_FFDF623C
ROM:FFDF6234
ROM:FFDF6234 loc_FFDF6234                            ; CODE XREF: opendir+150j
ROM:FFDF6234                 MOV     R0, #0
ROM:FFDF6238                 LDMFD   SP!, {R3-R9,PC}
ROM:FFDF623C ; ---------------------------------------------------------------------------
ROM:FFDF623C
ROM:FFDF623C loc_FFDF623C                            ; CODE XREF: opendir+1Cj
ROM:FFDF623C                 MOV     R0, #0x44
ROM:FFDF6240                 BL      sub_FFC295F8
ROM:FFDF6244                 MOVS    R4, R0
ROM:FFDF6248                 MOVEQ   R1, #432
ROM:FFDF624C                 ADREQ   R0, aReadfdir_c ; "ReadFDir.c"
ROM:FFDF6250                 BLEQ    Assert
ROM:FFDF6254                 CMP     R5, #4
ROM:FFDF6258                 MOV     R7, #0
ROM:FFDF625C                 STREQ   R7, [R4,#4]
ROM:FFDF6260                 STREQ   R7, [R4,#8]
ROM:FFDF6264                 BEQ     loc_FFDF6288
ROM:FFDF6268                 MOV     R0, #0x8000
ROM:FFDF626C                 BL      sub_FFC296AC
ROM:FFDF6270                 MOV     R1, #0x8000
ROM:FFDF6274                 CMP     R0, #0
ROM:FFDF6278                 STMIB   R4, {R0,R1}
ROM:FFDF627C                 LDREQ   R1, =442                  <-------------- Assert
ROM:FFDF6280                 ADREQ   R0, aReadfdir_c ; "ReadFDir.c"
ROM:FFDF6284                 BLEQ    Assert
ROM:FFDF6288
ROM:FFDF6288 loc_FFDF6288                            ; CODE XREF: opendir+50j
ROM:FFDF6288                 MOV     R0, 0xFFFFFFFF
ROM:FFDF628C                 STR     R0, [R4]
ROM:FFDF6290                 STR     R7, [R4,#0xC]
ROM:FFDF6294                 STR     R7, [R4,#0x10]

Currently i am not sure whats causing this problem, i have to take a deeper look a this. ;)


*

Offline ERR99

  • ****
  • 339
Re: A3000IS poring thread
« Reply #74 on: 13 / February / 2011, 02:41:10 »
After some tests with my A3000IS 1.0C:

I was not able to activate DNG format option.
Always having a message

"Cannon load CHDK/badpixel.bin.
Please run
CHDK/SCRIPTS/TEST/badpixel.lua"
And what exactly is the problem? Do what the message says, and the message is gone...

*

Offline msl

  • *****
  • 1262
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: A3000IS poring thread
« Reply #75 on: 13 / February / 2011, 03:35:47 »
Since trunk rev. 1035/1049 there is a build-in function to create badpixel.bin. The script does not work.

msl
CHDK-DE:  CHDK-DE links

*

Offline ERR99

  • ****
  • 339
Re: A3000IS poring thread
« Reply #76 on: 13 / February / 2011, 04:38:10 »
The A3000IS builds here are all based on a chdk trunk version from end of december 2010, so the "old" script to create the badpixel.bin is still working (at least the scripts creates a badpixel.bin file, so in camera DNG development is working).

*

Offline AST

  • *
  • 1
Re: A3000IS poring thread
« Reply #77 on: 14 / February / 2011, 05:04:27 »
Hi! First of all, many thanks for porting chdk to A3000IS :)
What do I have to do in order to get a hdr-script running? I tried the UBASIC "HDR with stacking"... It partially works but does not change the eV between pictures. I used this script with an Ixus 70 and A610 so I should know how to operate it.
What do I have to modify for an A3000IS 1.00d?

Thanks in advance!


Re: A3000IS poring thread
« Reply #78 on: 18 / March / 2011, 17:15:03 »
Hey, new user here. Have there been any workarounds for the power drain issue so far?

*

Offline whim

  • ******
  • 2013
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: A3000IS poring thread
« Reply #79 on: 18 / March / 2011, 17:52:39 »
So far, consensus seems to be that CHDK hardly has any influence on power consumption, see the
wiki FAQ here
This FAQ also has a link to detailed measurements for some camera's

hope that helps,

wim

 

Related Topics