IXUS 1000 HS Porting Thread - page 42 - DryOS Development - CHDK Forum supplierdeeply

IXUS 1000 HS Porting Thread

  • 437 Replies
  • 106577 Views
Re: IXUS 1000 HS Porting Thread
« Reply #410 on: 31 / December / 2015, 09:22:20 »
Advertisements
Am i able to change the color matrix in the newer build by myself? or i need to recompile CHDK just to embed this color matrix?
You need to recompile CHDK to change the color matrix.
Ported :   A1200    SD940   G10    Powershot N    G16

Re: IXUS 1000 HS Porting Thread
« Reply #411 on: 12 / January / 2016, 10:06:27 »
Hello, everyone!

Is there a working CHDK for 1.02e firmware out there? I tried to make this one work, but didn't succeed:

Test version for 102e

I have a 32GB Kingston Class 10 SDHC card, but I also tried the standard 32MB SD card that comes with the camera.

I tried the 'firmware update' method, copying the PS.FI2 file from a 1.02d build, but after pressing the update button, the camera just turns off and refuses to turn back on, unless I remove the battery for a couple of seconds.

I tried Stick - naturally it didn't find a suitable CHDK version for 1.02e firmware, so it just stayed at step1.

I tried EOScard (for bulids without a PS.FI2 file) - just got a 'card locked' message.

The 32GB card was formatted in FAT32 by the camera, and the 32MB card in FAT(16). The file system didn't seem to make a difference.

I've followed the sintructions for each method thoroughly (exept the improvisation with the PS.FI2 file), but nothing worked so far. The only thing I haven't tried is the dual-partition method.

I can't program, so I can't really compile/modify a build myself. I don't want to waste anyone's time, but I'd very much appreciate it of someone helped me out.

Thanks.

Re: IXUS 1000 HS Porting Thread
« Reply #412 on: 12 / January / 2016, 12:07:28 »
I tried the 'firmware update' method, copying the PS.FI2 file from a 1.02d build, but after pressing the update button, the camera just turns off and refuses to turn back on, unless I remove the battery for a couple of seconds.
The firmware version of your camera and the firmware version CHDK was built for must match.  There are a few exceptions but this is clearly not one of them.

Quote
I tried Stick - naturally it didn't find a suitable CHDK version for 1.02e firmware, so it just stayed at step1.
See this link :  STICKX

Quote
I tried EOScard (for bulids without a PS.FI2 file) - just got a 'card locked' message.  The 32GB card was formatted in FAT32 by the camera, and the 32MB card in FAT(16). The file system didn't seem to make a difference. I've followed the sintructions for each method thoroughly (exept the improvisation with the PS.FI2 file), but nothing worked so far. The only thing I haven't tried is the dual-partition method.
The IXUS1000 was released prior to 2011 and will not boot from a FAT32 partition (this is mentioned several times in the wiki instructions).  You will need a dual partition boot.   Following the STICKX instructions at the link I posted above will give that to you.

Ported :   A1200    SD940   G10    Powershot N    G16

Re: IXUS 1000 HS Porting Thread
« Reply #413 on: 13 / January / 2016, 08:08:02 »
The IXUS1000 was released prior to 2011 and will not boot from a FAT32 partition (this is mentioned several times in the wiki instructions).  You will need a dual partition boot.   Following the STICKX instructions at the link I posted above will give that to you.

Apparently I missed that part. Thank you! I managed to set up dual partitions on the card, although not without a hitch.

Initially STICK tried to make two partitions - one FAT12 (?) and one FAT32 - but it didn't create them properly and didn't copy any files. I recon this was Windows' fault. I booted Hiren's Boot CD and used the Parted Magic distro to see what was happening. STICK had indeed created two partitions, both of which were corrupt. I reformatted them properly and copied the CHDK files manually. That did the trick and CHDK finally booted on my camera.

Not much luck with RAW though - the files come out with a strong green tint and/or defective pixels, depending on the software I use to open them.

Anyway, thanks again!


*

Offline srsa_4c

  • ******
  • 4229
Re: IXUS 1000 HS Porting Thread
« Reply #414 on: 13 / January / 2016, 10:56:10 »
Not much luck with RAW though - the files come out with a strong green tint and/or defective pixels, depending on the software I use to open them.
A couple of questions:
- which raw format are you using?
DNG is recommended, if your raw converter has problems with bad pixels, then use DNG version 1.1 (can be selected in the RAW menu, but needs a badpixel file) edit: the port's notes mention that in-camera badpixel.bin creation doesn't work...
- what software are you referring to?
- how green is that green cast?
If you read back here a little (posts starting at October 2015), you can see discussions about similar problems.

If you'd like to test the (recently mentioned) color matrix modification, it's possible to create a test build with that mod.

edit:
102e port source diff (also contains the modified color matrix) attached

I'm wondering about nafraf's test binary: the source he attached is missing some required parts, so I'm not sure what was actually in it.
« Last Edit: 13 / January / 2016, 13:38:59 by srsa_4c »

Re: IXUS 1000 HS Porting Thread
« Reply #415 on: 14 / January / 2016, 07:44:23 »
I save in DNG (it's enabled by default I think). I tried ver 1.1 but saw no difference.

In Photoshop CS6 (Camera Raw 8.7.1) and RawTherapee 4.2.642 there's a green cast.

In RawHide there's a purple cast.

The 'bad pixels' in Camera Raw 8.7.1 turned out to be the shadow/highlight clipping warning. In RawTherapee there are multi-coloured speckles all over the images even with no shadow/highlight clipping warning enabled. They also appear in RawHide.

I don't know how to create builds or what to do with a .diff file. I don't have any experience with modifying CHDK.

*

Offline srsa_4c

  • ******
  • 4229
Re: IXUS 1000 HS Porting Thread
« Reply #416 on: 14 / January / 2016, 11:06:40 »
I save in DNG (it's enabled by default I think). I tried ver 1.1 but saw no difference.
Yes, unfortunately there won't be any difference because CHDK will not fix bad pixels (in DNG 1.1) if there's no valid badpixel list.
If you're using DNG 1.3 and non-Adobe software, see this thread for bad pixel related information.

Quote
I don't know how to create builds or what to do with a .diff file. I don't have any experience with modifying CHDK.
No problem, I just wanted some response before posting a build.
New, CHDK 1.5 based build is attached. Only diskboot is supported (ps.fi2 is not included).
If you're using a card with two partitions, extract the new diskboot.bin file to the smaller partition and the CHDK directory to the bigger one.

Please report whether it starts and is working properly. If possible, please also check the amount of free memory you see here: miscellaneous stuff -> show memory info.
If you give positive feedback, I'll make this port officially available.

As mentioned, the included color matrix is a different one (it comes from another port, not calibrated). User ojy_97 reported better looking DNGs with this matrix.

edit:
102e port is officially available, test build removed
« Last Edit: 16 / January / 2016, 13:32:29 by srsa_4c »

Re: IXUS 1000 HS Porting Thread
« Reply #417 on: 14 / January / 2016, 17:26:10 »

Please report whether it starts and is working properly. If possible, please also check the amount of free memory you see here: miscellaneous stuff -> show memory info.
If you give positive feedback, I'll make this port officially available.

Ok, this build works. The DNGs appear much better then before in Camera Raw and RawTherapee. In RawHide nothing's changed - strong purple cast - although I may be neglecting some setting. There is some sort of lens distortion(?) with DNGs. The 'DNG Crop Size' setting doesn't have an effect on this. Also there's some trouble with highlights - some images have blown blue highlights, others have a slight green cast on highlights that should be white.

DNG-to-JPEG:

JPEG:

Show memory info (dual-partition 32Gb card):
Free memory: 754344 bytes
CHDK size: 146192 bytes


*

Offline srsa_4c

  • ******
  • 4229
Re: IXUS 1000 HS Porting Thread
« Reply #418 on: 14 / January / 2016, 18:10:26 »
Ok, this build works. The DNGs appear much better then before in Camera Raw and RawTherapee.
Thanks. Since you're the second person reporting better colors, I'll change the color matrix data for this cam.
Quote
In RawHide nothing's changed - strong purple cast - although I may be neglecting some setting.
This cam has an unusual CFA pattern (GRBG), that might trigger a bug in that program.
Quote
There is some sort of lens distortion(?) with DNGs. The 'DNG Crop Size' setting doesn't have an effect on this.
All recent wide angle compact cameras correct lens distortion from software, so what you see is normal. Distortion becomes less toward the tele end of zoom.
Quote
Also there's some trouble with highlights - some images have blown blue highlights, others have a slight green cast on highlights that should be white.
Try some high magnification on those areas. You'll likely find that one or more color channels are saturated - the camera's JPEG engine clips highlights at a lower level and corrects false colors in those areas.
Quote
Free memory: 754344 bytes
Thanks, that's enough for running CHDK.

edit:
changes committed: https://www.assembla.com/spaces/chdk/subversion/commits/4341
trunk (CHDK 1.5) only for now
« Last Edit: 16 / January / 2016, 13:31:17 by srsa_4c »

*

Offline koshy

  • *****
  • 1046
Re: IXUS 1000 HS Porting Thread
« Reply #419 on: 31 / May / 2018, 16:17:25 »
IXUS 1000 crashes with current trunk build, that will need more attention elsewhere. I used ixus1000_sd4500-100d-1.5.0-5018-full. "Crashes" means that it locks up on pressing the power button without showing anything and no light. SD card removal does not cure that. Battery out/in is needed. Stable ixus1000_sd4500-100d-1.4.1-5012-full booted and was used to retreive attached ROMLOG
(Reminder as requested by srsa_4c)
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)

 

Related Topics