A1000IS porting...

matze1503

Firmware😀

whim

@matze1503

yeah, lock card and start up in play mode - if your setup is OK you might see CHDK logo (if already implemented)
pop up for a second, but then you would typically not notice CHDK anymore.

Now press <Alt> (should be the Direct Print button on your cam) -> you will see <Alt> @ bottom center screen.
With <Alt> visible, press "Menu" and the CHDK main menu should appear.

If you can't get to the main menu, you:

- didn't prepare the card properly (unlikely if you used CT 😁)

- maybe did not download latest DISKBOOT.BIN ?

More keys ? go here FAQ - CHDK Wiki

hope that helps,

wim

PS Note I don't have this cam, so i don't know what is already/is not yet implemented ...

PS2: where's my manners: welcome to the forum, hope you'll have fun !!

EyP3

Matze,
yes, just switch the Camera on, if the write protect mode is on, you should either correctly see the CHDK message or the camera would say 'card is locked', this is when CHDK is not recognized.
Norbert

matze1503

Thanks for your replies! But I still can't use CHDK on my camera...
What I'm doing is:
- Putting the SD-Card in my computer
- Starting CardTricks (1.43) and I use the DryOS-Button. After that, there are 5 files on the card (diskboot.bin, dryos.bin, empty.dum, newdryos.bin, vxworks.bin)
- I replace the diskboot.ini by the one diablo postet before at the 8th of decembre
- I remove the disk from my computer and lock it
- I put it into he camera again and I try to start it the normal way
But nothing happens at all..the camera doesn't start up.
Am I doing something wrong?

With kind regards,

Matze1503

whim

@matze

Yes...you are. What you're doing there is creating a udump card, this is only necessary as a first step
before porting the cam ... which diablo is doing/has already done.

what you need to do: card in reader -> start CardTricks & select card.
click 'Format as FAT', and then 'Make Bootable'.

Done, now put DISKBOOT.BIN (from this thread)
on your card, lock it, and put in camera. Start camera.

wim

PS if this does not work, your firmware is probably different than the 8 dec. one ...

to test: - same card as above in cam, but no write protect
- start cam, press and hold 'Func' and press 'display'
- real firmware version is shown as 'GM 1xxx'

matze1503

Thanks for your help so far!

My Firmware is form July the 0th 2008...1.00b

Is there a way to make an update?

Matze

tyrantt23

matze1503
Thanks for your help so far!

My Firmware is form July the 0th 2008...1.00b

Is there a way to make an update?

Matze

whim

Canon only very rarely issues 'updates', and only they know if cams with
different firmwares are totally identical hardware-wise.
So, each firmware version requires it's own port.
You can dump your firmware, and compare it with the existing dump, though.
If you're very lucky, they are identical enough not to require a separate porting process
(based on previously ported cams, there's only a couple of % chance though)

wim

Basically, you don't need an update for that camera. CHDK is far better than any update you'll ever get from Canon. 😀

tyrantt23

whops... double post by accident and don't know how to delete it. 😖

michaelkenward

matze1503
My Firmware is form July the 0th 2008...1.00b

Is there a way to make an update?

I didn't know there was anything after 1.00b. I asked the same question about 1.00a. Same answer.

These things don't seem to have the same update regime as Canon's digital SLRs.

whim

There's only official Canon updates for older P&S ' s ...

For the newer ones, Canon has come up with a brilliant scheme:

they just release new cams i.o. firmware updates, keeping them pesky hackers so busy
that they don't have time to start messing with their precious DSLR's 🤣

wim

diablo

I couldn't work on the bugs posted for a couple of weeks now. Also I am going for a 10-day vacation. Sorry for being lazy in uploading the diff/patch to make this camera's CHDK available on autobuild. I will be doing it in the new year.
Hope to see more bugs reported when I come back.

It would be great if someone can get the color profiling done for this camera to be used for RAW conversion.

EyP3

Diablo,
have great Christmas holidays!
Many thanks for your work!
Norbert

EyP3

Hope to see more bugs reported when I come back.

Well, to me it looks like I found one.

A 1000 IS, Firmware Rev 100b

Aperture override seems not to work correctly.

My settings:

- 'P' or 'AUTO' mode
- any ISO value, e.g. AUTO ISO
- Disable Overrides 'Off' or 'disable'
- all overrides 'off' (except override ap), custom ISO not enabled
- override aperture set to e.g. '3.17'
- displayed (top left) override aperture: AV: 3.17
- displayed (center bottom) and used aperture: 8

other override values of aperture wouldn't work either
automatic aperture with 'disable overrides' set to 'on' would be 2.77

Could somebody confirm this bug?

Thanks
Norbert

tyrantt23

diablo
I couldn't work on the bugs posted for a couple of weeks now. Also I am going for a 10-day vacation. Sorry for being lazy in uploading the diff/patch to make this camera's CHDK available on autobuild. I will be doing it in the new year.
Hope to see more bugs reported when I come back.

It would be great if someone can get the color profiling done for this camera to be used for RAW conversion.

Don't be silly Diablo, we're already really glad that the CHDK port for this camera is coming a long way. I hope you have fun on your vacation... enjoy it. 🧑‍🎄

As far as the color profiling, I'm needing some help with what step I need to take next. I've already taken the RAW/Jpeg pictures of the color palette, but I don't know what to do from there.

From what I've read, I need to be able to open the RAW to get the matrix values for the color profile, but from what I understand, RAW can't be opened until the color profile is done. I've tried a pletora of different programs, but nothing works. So its like a "what comes first, the chicken or the egg" type of question.

If some CHDK whizz could point me in the right direction of what I need to do with the RAW/Jpeg of the color palette, I'll gladly take care of it. Thanks. 😀

EyP3
Aperture override seems not to work correctly.

The same happens on my camera. I used your values and the same happened, even when I changed the aperture value.

Note:
I have my CHDK to "Show Real Aperture Value" ("Av" on top right) and it always displays 2.68 no matter which aperture I try to set it to.
So here's the break down of the values that show on the camera with the settings posted by EyP3:
- top left: Aperture chosen on override aperture
- center bottom: always 8
- top right: always 2.68

Can someone else confirm this?

EyP3

- top right: always 2.68

Can someone else confirm this?

Yes, confirmed. Always 2.68
(Btw., if anybody wants to try: the clock display has to be turned off, otherwise the values wouldn't show)

Thanks for checking.
Norbert

ewavr

All Canon cameras without aperture priority mode have no real diaphragm, only ND filter (ND Filter - CHDK Wiki) - why a1000/a2000 should be an exclusion?

tyrantt23
If some CHDK whizz could point me in the right direction of what I need to do with the RAW/Jpeg of the color palette, I'll gladly take care of it.

For example, DNG4PS-2 0.2.3 Beta 16, settings->camera options (add new camera)->calc. color profile. Read all instrunction on web page .

EyP3

All Canon cameras without aperture priority mode have no real diaphragm, only ND filter

Then the aperture overrides wouldn't make much sense either? Too bad.
How is this handled in CHDK normally with these types of cameras?

Norbert

fe50

EyP3

All Canon cameras without aperture priority mode have no real diaphragm, only ND filter

Then the aperture overrides wouldn't make much sense either? Too bad.
How is this handled in CHDK normally with these types of cameras?

The aperture things are disabled then (defines in camera.h), only ND filter related things are enabled (e.g. no Av bracketing menu item, only Tv bracketing, additionally ND filter menu...)

When looking directly into the optics (use a strong light, e.g. a pocket lamp) you should see either the aperture changing or the ND filter swinging in & out.
If there's only a ND filter the Canon OSD has only 2 F-stops, e.g. F/2.8 (ND filter off) and F/8.0 (ND filter active, swung in) - only with the zoom you'll get other F-stops...

EyP3

When looking directly into the optics (use a strong light, e.g. a pocket lamp) you should see either the aperture changing or the ND filter swinging in & out.

Just tried that, it's obviously the ND filter kicking in ... 🙁
Thanks for the explanation!
Norbert

whoever

fe50

All Canon cameras without aperture priority mode have no real diaphragm, only ND filter

Then the aperture overrides wouldn't make much sense either? Too bad.
How is this handled in CHDK normally with these types of cameras?

This is all correct and fine, but still it doesn't necessarily invalidates the idea of aperture override in such cameras.

As an example, I own an IXUS950 that lacks iris aperture. Still, I'd like to be able to set "shutter priority" for shots of rapid motion. How would I go about it? Setting "ND filter out" override? But that invalidates camera's exposure metering, so I'd have to go completely manual. It'd also invalidate the LCD preview.

My solution is this -- define "shutter_priority" and set it in the menus, and then:

void shooting_expo_param_override(void){
// NOTE: should probably check for tv and ND overrides, flash mode, etc... Or use the brain when shooting!..
 extern int shutter_priority;
 short av,tv;
 if (shutter_priority) {
  _GetPropertyCase(PROPCASE_AV, &av, sizeof(av));
  if (av>512) { // Ixus950: ND filter is used  (max without ND = 480, min with ND = 563)
   av = av - 275;	// remove the filter (275/96 = 2.86 full stops in Ixus950)
   _SetPropertyCase(PROPCASE_AV, &av, sizeof(av));
   _GetPropertyCase(PROPCASE_TV, &tv, sizeof(tv));
   tv = tv + 275;	// compensate exposure
   _SetPropertyCase(PROPCASE_TV, &tv, sizeof(tv));
  }
 }
...
}

« Previous Page Next Page »