[Digikam-devel] [Bug 142056] Save changes of image modifications with Versioning.

[Jisakiel]

------- 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 jisakiel yahoo es  2008-08-06 01:22 -------
So, having all available versions of a photo somehow "related" to the original one in the GUI would definitely help with the usability. 

Regarding how other apps do the effects processing in real time, Aperture from Apple does use the OSX 10.4++ CoreImage API, which IIRC uses the LLVM backend (sort of JIT for any code parsed by the gcc frontend) to generate code targeting the GPU present in the system, or if it isn't powerful enough, the SSE extensions available. That, of course, limits the color precision to that available from the GPU (used to be so powerful only in single mode). 

I don't know how Lightroom (as of 1.0) does it, as it doesn't seem to depend so much on a powerful GPU. I'd bet on decoding the images, processing them and storing the final results hidden from the user; it wouldn't use *more* space than saving an additional un-lossly-compressed copy of the RAW, However further processing from that snapshot would not hurt quality (it's RAW -> effect set 1 -> effect 2 vs raw -> effect set 1 (mmap-saved file?) -> effect 2). Only if you wanted to selectively undo effects would the image have to be regenerated from the original raw, which could be a case uncommon-enough.