[digiKam-users] Hot pixel tool

[Gilles Caulier]

As the image parsing is multi-threaded (or at least must use one separated
thread), this must be acceptable.

I don't remember if i patch this code to use multi-core in the past. If
it's not the case, it's easy to do, as i do with other editor tools.

We can limit the max number of hot pixel with a setting in tool view.

Gilles Caulier

2018-08-14 23:39 GMT+02:00 Maik Qualmann <metzpinguin at gmail.com>:

> The black image has 2701 hot pixels ...
> I notice no speed problem if we maybe increase the value to 5000?
>
> Maik
>
> Am Dienstag, 14. August 2018, 23:33:43 CEST schrieben Sie:
> > The image exceeds const int maxHotPixels = 1000, so it will be canceled.
> >
> > From code:
> >
> > // If you accidentally open a normal image for a black frame, the tool
> and
> > host application will
> > // freeze due to heavy calculation.
> > // We should stop at a certain amount of hot pixels, to avoid the freeze.
> > // 1000 of total hot pixels should be good enough for a trigger. Images
> with
> > such an amount of hot pixels should
> > // be considered as messed up anyway.
> >
> > Maik
> >
> > Am Dienstag, 14. August 2018, 23:21:22 CEST schrieb Lutz Epperlein:
> > > You can download both files from my piwigo:
> > > <https://epperleinberlin.name/piwigo/index.php?/category/46>
> > >
> > > Thanks
> > > Lutz
> > >
> > > Am Tue, 14 Aug 2018 23:06:21 +0200
> > >
> > > schrieb Gilles Caulier <caulier.gilles at gmail.com>:
> > > > Can you share the image to process and the hot pixel one. I would to
> > > > try in my computer.
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20180815/e3f353fa/attachment.html>