Project

General

Profile

Bug #10949

[rawspeed] The bad pixels are too damn high!

Added by Edgardo Hoszowski almost 4 years ago. Updated over 3 years ago.

Status:
Fixed
Priority:
Low
Assignee:
-
Category:
-
Target version:
Start date:
03/15/2016
Due date:
% Done:

100%

Estimated time:
Affected Version:
git development version
System:
Ubuntu
bitness:
64-bit
hardware architecture:
amd64/x86

Description

Hi,

I have this message "[rawspeed] The bad pixels are too damn high!" for several raw files from a Panasonic LF1. I uploaded two raw files on this link with a xmp, but just unprocessed files give the error too.

https://onedrive.live.com/redir?resid=44546736A35CF1EC!510&authkey=!ACHjXLB7jqq4CpU&ithint=folder%2cxmp

This does not happen with Nikon D7100 files I own.

I use darktable 2.1.0+657 (compiled from source)

If more test or files are needed just let me know.

Thanks,
Edgardo.

Associated revisions

Revision a47b66a4 (diff)
Added by Pedro Côrte-Real almost 4 years ago

rawspeed: disable badpixel count when not fuzzing

As it turns out some files (RW2 in particular) have quite a few
badpixels that were triggering the badpixel disabling code. Use
the new __AFL_COMPILER flag to disable that code when not running
under AFL (fixes #10949).

History

#1 Updated by Pedro Côrte-Real almost 4 years ago

  • % Done changed from 0 to 100
  • Status changed from New to Fixed

#2 Updated by Roman Lebedev over 3 years ago

  • Target version set to 2.2.0

Also available in: Atom PDF

Go to top