SX520HS Porting thread. - page 16 - DryOS Development - CHDK Forum

SX520HS Porting thread.

  • 209 Replies
  • 83011 Views
*

Offline srsa_4c

  • ******
  • 4451
Re: SX520HS Porting thread.
« Reply #150 on: 24 / May / 2016, 14:32:01 »
Advertisements
when this build for sx520 will become official??
Known issues, waiting to be solved:
- maximum ISO limit needs a small change in CHDK core
- there are reports about problems with exFAT cards (SDXC cards are exFAT by default)

Does any of you have problems using the CHDK file browser on SDXC (exFAT) cards? Symptom can be seen here: https://chdk.setepontos.com/index.php?topic=12418.msg128724#msg128724
Please also report if you do not have that problem.


exFAT detection is currently broken due to some unknown build system issue.
« Last Edit: 24 / May / 2016, 14:55:33 by srsa_4c »

Re: SX520HS Porting thread.
« Reply #151 on: 24 / May / 2016, 15:16:27 »
when this build for sx520 will become official??
Known issues, waiting to be solved:
- maximum ISO limit needs a small change in CHDK core
- there are reports about problems with exFAT cards (SDXC cards are exFAT by default)

Does any of you have problems using the CHDK file browser on SDXC (exFAT) cards? Symptom can be seen here: https://chdk.setepontos.com/index.php?topic=12418.msg128724#msg128724
Please also report if you do not have that problem.


exFAT detection is currently broken due to some unknown build system issue.
Mine is reported as FAT32 under Ubuntu. It's Toshiba Exceria 16Gb. I did not reformat it.

Re: SX520HS Porting thread.
« Reply #152 on: 24 / May / 2016, 15:21:07 »
when this build for sx520 will become official??
I think CHDK is a constant work in progress anyway. You are not going to get a warranty once it's released. Just use the latest test build and report any problems here. I went for a hike in mountains with test6 on Sunday - it's as good as an official build.  :D

Re: SX520HS Porting thread.
« Reply #153 on: 25 / May / 2016, 08:02:59 »
Is there any script for CHDK which will produce time lapse videos in the camera itself? (like it does in Magic Lantern) Means the video is shot by capturing the frames itself??


*

Offline reyalp

  • ******
  • 14080
Re: SX520HS Porting thread.
« Reply #154 on: 25 / May / 2016, 12:54:00 »
Is there any script for CHDK which will produce time lapse videos in the camera itself? (like it does in Magic Lantern) Means the video is shot by capturing the frames itself??
No. This is not really something that can be done with just scripting. There is some experimental work on lower frame rate video in https://chdk.setepontos.com/index.php?topic=7938.20 but nothing generally usable.
Don't forget what the H stands for.

Re: SX520HS Porting thread.
« Reply #155 on: 26 / May / 2016, 13:38:53 »
Hi everyone,

I gave the test6 a really good test today, and found a weird problem. Removal of badpixels embedded in DNG 1.1 always worked perfectly. At the end I switched the camera in P mode to ISO 400. To my surprize, only a part of badpixels was being removed.

Does anyone experience this problem?

I have tried try to regenerate badpixel.bin with ISO set to 400, and got 40k instead of 10k badpixels. Thinking about this, technically, no surprize but... how do you solve it? When shooting in ISO 100, images come really clean, so I doubt it makes sense to shoot with badpixel.bin generated with 400 at all ISOs. Of course the best solution is to have CHDK use different badpixel files depending on the active ISO, but I am surely want too much.

By the way, now that I have created badpixel file with ISO 400, are there any tricks to embed this new file into the existing photos, to save them? Canon-created JPEGs are clean, but it would be great to have clean raw files as well.

Thank you!

*

Offline reyalp

  • ******
  • 14080
Re: SX520HS Porting thread.
« Reply #156 on: 26 / May / 2016, 16:12:00 »
Quote from: ilya345 link=topic=12314.msg128750#msg128750
I have tried try to regenerate badpixel.bin with ISO set to 400, and got 40k instead of 10k badpixels. Thinking about this, technically, no surprize but... how do you solve it? When shooting in ISO 100, images come really clean, so I doubt it makes sense to shoot with badpixel.bin generated with 400 at all ISOs.
Using a badpixel generated at 400 is actually fine, as long as your camera has enough free RAM. CHDK only actually patches the pixel if it is marked bad by the Canon firmware for the current ISO. The whole badpixel.bin is just a speed optimization, because scanning the whole raw buffer is very slow. So in general, you should generate your badpixel list at the highest ISO you plan to shoot.

The alternative is to just shoot DNG 1.3, and fix the bad pixels in your raw workflow on your PC. If you use adobe software, they should be fixed automatically. For other software, you might need to generate a program specific badpixel file, or set some specific options to interpolate over 0 valued pixels.

You can use chdkptp to generate badpixel list files that some programs can use, or to fix them in the file: https://www.assembla.com/spaces/chdkptp/wiki/DNG_Processing
Don't forget what the H stands for.

*

Offline srsa_4c

  • ******
  • 4451
Re: SX520HS Porting thread.
« Reply #157 on: 26 / May / 2016, 18:59:02 »
New test build for 100b. Should fix exFAT detection and should no longer crash when overriding ISO (while flash is used).
Allowed ISO range has been limited to 100..3200.

edit:
Can someone check if crash on ISO override is gone?
« Last Edit: 26 / May / 2016, 19:04:57 by srsa_4c »


*

Offline srsa_4c

  • ******
  • 4451
Re: SX520HS Porting thread.
« Reply #158 on: 26 / May / 2016, 19:00:10 »
New test build for 100c. Separate post due to forum limitations on attachments.

Re: SX520HS Porting thread.
« Reply #159 on: 27 / May / 2016, 00:25:24 »
@srsa_4c

Crash because ISO override is gone. But only once I crashed now. After crash, again some photos are taken at same settings and No crash is observed. Attaching ROMLOG file. please have a look on that. The screen itself is showing the ISO to 3200. Even increasing ISO upto 10000 is possible in CHDK menu. but is limited to 3200.. But now for Tv=1s, ISO was previously going to 10000, now it is limited there also to 3200.

 

Related Topics