Bug 390683 - Batch processing creates 0 byte files on Fujifilm RAF RAW images with lens correction
Summary: Batch processing creates 0 byte files on Fujifilm RAF RAW images with lens co...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Bqm-LensCorrection (show other bugs)
Version: 5.8.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-18 14:02 UTC by Michael Dawid
Modified: 2018-02-19 20:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 5.9.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Dawid 2018-02-18 14:02:23 UTC
I am trying to apply lens correction in the batch queue manager, but the resulting image is a 0 byte image. When using the batch queue manager I add the lens correction tool to the tools tab and click on run. When I set the checkbox in lens correction to 'use metadata', the lens correction fails due to missing lens and camera information in the lensfun db -> this might be ok.
But when i uncheck 'use metadata' and run the batch, the lens correction fails too. Additionally a 0 byte image as output is created -> it think this should not happen. 
I am using Fujifilm RAF format from my XT-20 in compressed mode. Please find attached a black image, for reproducing the error.
Comment 1 Maik Qualmann 2018-02-18 16:22:48 UTC
With a test image from the web even automatic detection works here. But that depends on the lens, whether it is available in the Lensfun DB. To your problem, when you edit an RAF file in BQM, you have to add as a last tool, a conversion to a writetable file format (TIFF, JPEG, PN ...). A RAW file can only be read.

Maik
Comment 2 Maik Qualmann 2018-02-18 18:33:11 UTC
Git commit ec518fe618a9e70650204898c1a9aba9f4a90f79 by Maik Qualmann.
Committed on 18/02/2018 at 18:31.
Pushed by mqualmann into branch 'master'.

do not save or overwrite files if the new file size is 0 bytes in BQM

M  +8    -4    utilities/queuemanager/manager/task.cpp

https://commits.kde.org/digikam/ec518fe618a9e70650204898c1a9aba9f4a90f79
Comment 3 Michael Dawid 2018-02-18 21:23:18 UTC
thanks for the info and the bugfix. that was surprisingly fast!

just one last question, is DNG writable by digikam? I think this format might be a nice workaround for my issue, but maybe also for other Fujifilm users. At least conversion to DNG is capable when importing from camera (or SD card).