darktable-org / darktable-org/rawspeed
Panasonic bad pixel handling issues
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 456
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Description
FZ28hMULTII0100.RW2 from https://www.imaging-resource.com/PRODS/FZ28/FZ28THMB.HTM currently decodes with all pixels being zeros, which as every pixel being badpixel, so it tried to fix every pixel as badpixel.
There is a number of problems there
- Should there be a sanity check on bad pixel fixing? This is clearly broken.
- Why is that file decoded as such? Is the file just broken,
or is there some logic missing to decode it somehow differently?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with FZ28hMULTII0100.RW2 from the linked Imaging Resource URL and trace how the RAW decoder handles its all-zero pixels and bad-pixel correction. Determine whether the sample is malformed or needs different decoding logic, and ensure clearly broken all-zero data is not treated as entirely bad pixels.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-vision
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100