[Digikam-devel] [Bug 142056] Save changes of image modifications with Versioning.
Unai Garro
ugarro at gmail.com
Tue Aug 5 20:04:31 BST 2008
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=142056
------- Additional Comments From ugarro gmail com 2008-08-05 21:04 -------
Mikmach
Yes, processing the whole image is very cpu costy. That's why I was
suggesting to use it only for the raw importer tool. Raw files are
always processed from scratch anyway, so this isn't an issue, and
there's no need to store the whole history of changes.
What I don't know is how other raw processing apps manage to do this in
real time. Processing only the view on screen might help, which can be
600-800kpx only versus the full image which is 10Mpx. Which is around
10-15 times faster. But then each time the image is scrolled, they need
to be reprocessed, and some tools cannot be applied unless they are done
over the whole image.
More information about the Digikam-devel
mailing list