SX160 IS porting thread - page 7 - DryOS Development - CHDK Forum  
« previous next »
Pages: 1 2 3 4 5 6 [7] 8 9 10 11   Go Down

SX160 IS porting thread

  • 101 Replies
  • 54646 Views
*

Offline tonyb

  • *
  • 14
Re: SX160 IS porting thread
« Reply #60 on: 08 / December / 2013, 01:17:46 »
Advertisements
Using the sx160is here and chdk @ 3263.

What's the best way to deal with dead/hot pixels?

On the raw menu I have:

Manual bad pixel remov [Averag.]

DNG format

'DNG' file extensiom

DNG version [1.3] also tried [1.1] with a badpixel file

Create badpixel.bin doesn't work if I select [1.3]
so I placed a file manually and used [1.1]... and it did work.
However, I still get many bad pixels.

Any suggestions? Could it be that the sx160is' chdk version is a beta version?

Got the cam for $79 at Walmart and they still have more. Is it a good cam to use with chdk?
Lots of chroma noise in low light (will chdk help?) but scripts and dng work fine, at that price couldn't ask for better.

Logged
*

Offline srsa_4c

  • ******
  • 4451
Re: SX160 IS porting thread
« Reply #61 on: 08 / December / 2013, 09:30:21 »
Quote from: tonyb on 08 / December / 2013, 01:17:46
Manual bad pixel remov [Averag.]
That's for bad pixels the camera doesn't know about, you'll have to provide a file named 'badpixel' or 'badpixel.txt' for it to work. See http://chdk.wikia.com/wiki/Badpixel_removal
Quote
Create badpixel.bin doesn't work if I select [1.3]
The 'create badpixel.bin' menu item should work independently of the selected DNG version, but the resulting badpixel.bin file is only used for DNG 1.1. If you have Adobe software (such as Photoshop) to process your images, you can use DNG 1.3.
Quote
so I placed a file manually and used [1.1]... and it did work.
However, I still get many bad pixels.
You'll have to use the 'create badpixel.bin' in the raw menu. Use one of the (semi-)manual modes - M, Av, Tv, P.
Quote
Lots of chroma noise in low light (will chdk help?)
CHDK can't fix the sensor, but you can denoise your DNGs later on the computer.
Logged
*

Offline tonyb

  • *
  • 14
Re: SX160 IS porting thread
« Reply #62 on: 08 / December / 2013, 10:29:08 »
>The 'create badpixel.bin' menu item should work independently
>of the selected DNG version

It doesn't seem to be working.

But it does work if I place a file (badpixel.bin) in the chdk folder and then select "Create badpixel.bin" from the menu.  However, I still get dead pixels so it seems like it is not taking care of the bad pixels.

Logged
*

Offline srsa_4c

  • ******
  • 4451
Re: SX160 IS porting thread
« Reply #63 on: 08 / December / 2013, 10:57:31 »
Quote from: tonyb on 08 / December / 2013, 10:29:08
But it does work if I place a file (badpixel.bin) in the chdk folder and then select "Create badpixel.bin" from the menu.
IMHO 'create badpixel.bin' doesn't care whether there is already a badpixel.bin file present. You'll get a warning - and nothing else - in play mode if you select that menu item, in rec mode the cam will take 2 pictures and compare the found badpixel counts. If the two exposures result in different number of bad pixels, the process will report a failure.
Placing badpixel.bin files with arbitrary content to the card will not help with bad pixel removal.
Logged
*

Offline tonyb

  • *
  • 14
Re: SX160 IS porting thread
« Reply #64 on: 08 / December / 2013, 11:13:07 »
Ok, thanks for looking into this.

I don't think create badpixel.bin is working at all yet, gave it another try and it failed, didn't create badpixel.bin.
 
Logged
*

Offline tonyb

  • *
  • 14
Re: SX160 IS porting thread
« Reply #65 on: 08 / December / 2013, 18:19:48 »
Found what the problem was. I usually have the cam on "Review<Hold>" and I think that was interfering with the "Create badpixel" process. I switched the cam to "Review<Off>", ran "Create badpixel" again and that took care of the problem. The bad pixels are gone now.
Logged
*

Offline sequencer

  • **
  • 51
Re: SX160 IS porting thread
« Reply #66 on: 23 / December / 2013, 20:17:00 »
Hi there, new here. I just got the SX160 IS.
One thing, the first DNG shot takes longer than the others to save. Is this normal?
Also, when creating badpixel.bin should I use iso100, iso1600? Should the lens be covered?

If there is anything you want me to test, please let me know.

Thanks!
Logged
*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: SX160 IS porting thread
« Reply #67 on: 23 / December / 2013, 20:30:01 »
Quote from: sequencer on 23 / December / 2013, 20:17:00
Hi there, new here. I just got the SX160 IS.
One thing, the first DNG shot takes longer than the others to save. Is this normal?

On my cameras it can take a bit longer; but not by a huge amount. What sort of difference are you seeing?

Quote
Also, when creating badpixel.bin should I use iso100, iso1600?

Use the highest ISO that works - there may be more bad pixels detected at high ISO.

Quote
Should the lens be covered?

Doesn't matter.

Phil.
Logged
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)
*

Offline sequencer

  • **
  • 51
Re: SX160 IS porting thread
« Reply #68 on: 24 / December / 2013, 17:26:09 »
Phil, yes the first shot is somehow slow, I guess this is normal then.
Got badpixel.bin created @ iso1600 without a problem.
Logged
*

Offline sequencer

  • **
  • 51
Re: SX160 IS porting thread
« Reply #69 on: 29 / December / 2013, 23:50:16 »
Hope I'm posting in the right place... If I set the Canon SX160IS to MF mode and Override Subj. Di [0n] [50 or other] the camera crashes. Also, sometimes it won't allow you to change the subject distance.
Logged
Pages: 1 2 3 4 5 6 [7] 8 9 10 11   Go Up
« previous next »
 

Related Topics
SimplePortal 2.3.6 © 2008-2014, SimplePortal