I upgraded to 4.2 and I still see a lot of bad/hot pixels. And I feel so clumsy because I can't seem to find preferences icon in Raw Therapee.
It's accessed from an icon with sliders file browser tab. See
http://50.87.144.65/~rt/w/index.php?title=Getting_Started (bottom left of the first screenshot, but may vary depending on setttings)
Here is print screen of a Raw Therapee: http://i.imgur.com/X01YOrn.jpg (You can also see a lot of bad/hot pixels on this image even though I've checked dead/hot pixel in Preprocessing).
...
2) Do I have to do something else beside enabling dead/hot pixel in Preprocessing?
It looks like those are mostly clusters of multiple pixels together. Some cameras do this. Perhaps raw therapee dead pixel code doesn't handle those.
edit:
If your camera has enough free RAM that the badpixel.bin doesn't cause low memory problems, using DNG 1.1 should be fine. The performance impact from patching is pretty minor, generally tens of milliseconds IIRC.
Of course that doesn't help with shots you already took.
Assuming you generated the bad.txt with chdkptp, you could just use it to fix your existing files, something like
dngbatch path/to/files {mod -patch; save -over -keepmtime}
This will overwrite the existing files, so you might want to make sure you have a backup copy first in case something goes wrong, or use the odir option to as in the example on the chdkptp wiki.
