SX230 1.01A CHDK .jpg files too small - page 3 - General Help and Assistance on using CHDK stable releases - CHDK Forum supplierdeeply

SX230 1.01A CHDK .jpg files too small

  • 42 Replies
  • 9856 Views
*

Offline srsa_4c

  • ******
  • 4426
Re: SX230 1.01A CHDK .jpg files too small
« Reply #20 on: 01 / April / 2013, 09:53:20 »
Advertisements
Using the CHDK version you suggested it reported: 335448

What does that tell us?
That number is the size of currently available memory in bytes. If you try to run the script in record mode or even in movie mode, it will be less.
The non-exmem version of CHDK and all memory it requires would have to fit in that.

I have attached another script. Can you run it on your current 1.2 CHDK? You'll have to enable Miscellaneous stuff -> Enable Lua native calls in the CHDK menu before, and you need to have the full CHDK release on your card, or else you'll get errors.

I also send you a PM with a link to a non-exmem CHDK build, please re-run this exmeminf script with that. The script will create *.log files in the root of the card.

Re: SX230 1.01A CHDK .jpg files too small
« Reply #21 on: 01 / April / 2013, 10:47:03 »
Using the CHDK version you suggested it reported: 335448

What does that tell us?
That number is the size of currently available memory in bytes. If you try to run the script in record mode or even in movie mode, it will be less.
The non-exmem version of CHDK and all memory it requires would have to fit in that.

I have attached another script. Can you run it on your current 1.2 CHDK? You'll have to enable Miscellaneous stuff -> Enable Lua native calls in the CHDK menu before, and you need to have the full CHDK release on your card, or else you'll get errors.

I also send you a PM with a link to a non-exmem CHDK build, please re-run this exmeminf script with that. The script will create *.log files in the root of the card.

Attached are the two log files from running the script you sent on CHDK ver 1.2 and the special version you PM'd me.  Thanks,

Re: SX230 1.01A CHDK .jpg files too small
« Reply #22 on: 01 / April / 2013, 11:18:02 »

I also send you a PM with a link to a non-exmem CHDK build,

Re-running photo tests with this build I did get a differentiated result for CHDK file sizes as follows (MBs):

CHDK mode:
Superfine 3.6
Fine 2.1
Normal 0.9

Canon mode:
Fine 2.1
Normal 0.9

Just one test, simple indoor scene, and I haven't closely evaluated the photos yet, but looks promising.

Would there be any reason not to use this build if jpgs check out OK?

*

Offline srsa_4c

  • ******
  • 4426
Re: SX230 1.01A CHDK .jpg files too small
« Reply #23 on: 01 / April / 2013, 13:49:33 »
Re-running photo tests with this build I did get a differentiated result for CHDK file sizes as follows (MBs):

CHDK mode:
Superfine 3.6
Fine 2.1
Normal 0.9

Canon mode:
Fine 2.1
Normal 0.9
Yes, that was expected.
Quote
Would there be any reason not to use this build if jpgs check out OK?
There are several CHDK operations which consume larger amounts of memory. If free memory is too low, Canon firmware functions can start to fail. This mostly shows up as a crash (cam stops with extended lens).
Some memory hungry CHDK stuff:
- Lua scripting, the Lua module itself is over 100kB
- zebra, histogram, edge overlay
- large amount of bad pixels (large badpixel.bin)
- ptp communication
- language file, when loaded
- extra fonts, when loaded
- ... there's probably more

If you find that the camera remains stable, there's no reason not to use the no-exmem version.


Re: SX230 1.01A CHDK .jpg files too small
« Reply #24 on: 01 / April / 2013, 14:50:15 »
Quote
Would there be any reason not to use this build if jpgs check out OK?
There are several CHDK operations which consume larger amounts of memory. If free memory is too low, Canon firmware functions can start to fail. This mostly shows up as a crash (cam stops with extended lens).
Some memory hungry CHDK stuff:
- Lua scripting, the Lua module itself is over 100kB
- zebra, histogram, edge overlay
- large amount of bad pixels (large badpixel.bin)
- ptp communication
- language file, when loaded
- extra fonts, when loaded
- ... there's probably more

If you find that the camera remains stable, there's no reason not to use the no-exmem version.

I don't use any of those except the badpixel.bin which is 55k, so I'll give it try for day-to-day use.  Can I turn off or delete anything, like the Lua module, to save space?

If the camera crashes I assume I can turn it off, or pull the battery to reset it - nothing permanent, correct?

Thanks, really, this was very much appreciated.
« Last Edit: 01 / April / 2013, 14:54:54 by sx230user »

*

Offline reyalp

  • ******
  • 13444
Re: SX230 1.01A CHDK .jpg files too small
« Reply #25 on: 01 / April / 2013, 16:37:42 »
I don't use any of those except the badpixel.bin which is 55k, so I'll give it try for day-to-day use.  Can I turn off or delete anything, like the Lua module, to save space?
The modules will only be loaded if used (for example, if you run a lua script), so there's no need to delete them.

If you use DNG 1.3 instead of DNG 1.1, you don't need badpixel.bin. To fix the badpixels with DNG 1.3, you will have to use a converter that either understands DNG opcodes (mostly Adobe tools) or can be told to patch 0 valued pixels.
Quote
If the camera crashes I assume I can turn it off, or pull the battery to reset it - nothing permanent, correct?
Normally, the crash will cause the camera to shut down, and you just have to turn it back on. Sometimes you need to remove the battery for a second to get it to start again.

Of course, there is never any guarantee with CHDK.
Don't forget what the H stands for.

Re: SX230 1.01A CHDK .jpg files too small
« Reply #26 on: 01 / April / 2013, 17:56:39 »


If you use DNG 1.3 instead of DNG 1.1, you don't need badpixel.bin. To fix the badpixels with DNG 1.3, you will have to use a converter that either understands DNG opcodes (mostly Adobe tools) or can be told to patch 0 valued pixels.


So in that case I leave Manual Bad Pixel Removal in the RAW menu set to OFF?

Thanks,

Re: SX230 1.01A CHDK .jpg files too small
« Reply #27 on: 01 / April / 2013, 18:16:55 »
Hope it is not too off topic, but are there any applications which can edit the badpixel.bin file

unlike with older canon cameras such as the a560 where you could use an additional supplementary badpixel file which would have values such as 2176,1535=160  (not sure what the stuff acter the = sign means but I know the first 2 are x and y locations)

the bad pixel file is not used with the chdk on the sx230hs. if we can spot a bad pixel within an uncorrected dng file which the badpixel.bin did not catch, is there a way to edit that file to manually specify the bad pixel? (eg on my camera, there is one located near the center of the image, and I can get the x and y location of it using the ruler tool in photoshop


*

Offline srsa_4c

  • ******
  • 4426
Re: SX230 1.01A CHDK .jpg files too small
« Reply #28 on: 01 / April / 2013, 18:47:40 »
So in that case I leave Manual Bad Pixel Removal in the RAW menu set to OFF?
That's the other bad pixel related facility: http://chdk.wikia.com/wiki/CHDK_User_Manual#Bad_pixel_removal and is only effective when there's a user provided badpixel list. Just set DNG version to 1.3. You can check the available free memory in the CHDK menu (Miscellaneous stuff -> Show memory info), so you can compare the difference between the DNG 1.1 and 1.3 case.


unlike with older canon cameras such as the a560 where you could use an additional supplementary badpixel file which would have values such as 2176,1535=160  (not sure what the stuff acter the = sign means
it's the raw pixel value (generated by the show_bad program, but is ignored by CHDK)
Quote
but I know the first 2 are x and y locations)

the bad pixel file is not used with the chdk on the sx230hs.
??? It should work on this camera too.
The source of show_bad and show_bad_b is available, and could be modified to be usable for new cameras.

Re: SX230 1.01A CHDK .jpg files too small
« Reply #29 on: 05 / April / 2013, 18:48:18 »
CHDK mode:
Superfine - 1.88
Fine - 2.11
Normal - 1.85
Off - 1.85

Canon mode:
Fine - 4.63
Normal - 2.33
There is something very wrong here if  Override JPEG Quality [ Off ]  produces a jpg any different than when CHDK is not even loaded!

Update : a quick look at the code in shooting.c  suggests that once you have change the quality to anything other than Off,  then I think you will need to reset the camera after you return it to the off position.  Setting a different quality value changes a PROPCASE value,  but setting it to Off does not reset that value.

I have 3 CHDK versions at this point: 1.1 (stable), 1.2 (new dev.), and non-exmem, for want of a better name.  I've retested 1.1 and 1.2 again, resetting the camera after setting Quality Override to Off.  In both cases the jpg size is limited to about 2.1 MB when shooting the same scene in Canon mode yields 2.8 MB files.

The only version of CHDK that allows Canon Fine compression is non-exmem.

 

Related Topics