darktable
darktable copied to clipboard
Canon CR3 Burst-mode support
DT doesn't seem to support the CR3 RAW burst-mode file. It only shows the initial image from it. It would be nice to support all the frames available in the file, as well as the ability to extract them all in 1 operation.
I don't know that mode but RAW support for CR3 is provided by Libraw. So you probably need to ask to Libraw team on their repository before. I am quite sure darktable team can't do anything about that. @kmilos: as you know more that part, if you have something to add to my comment!
Not what you requested but maybe it helps: https://github.com/dnglab/dnglab can extract all frames as DNG with a single command:
dnglab convert --image-index=all burst_roll.cr3 /tmp/all_frames/
I tried dnglab but it returns errors when trying to process the file (the analyze option returned: thread 'main' panicked at 'called Result::unwrap()
on an Err
value: Unsupported { what: "Unknown camera", model: "Canon EOS R6m2", make: "Canon", mode: "raw" }', bin\dnglab\src\analyze.rs:36:61). But that would be a handy utility if it supported the file format and/or camera (not real sure which is causing it to fail).
R6m2 isn’t supported by libraw yet - see https://github.com/darktable-org/darktable/pull/13684
That's unfortunate 😒. We'll keep waiting anxiously!
@vvpeter Sorry, R6MK2 support was added to dnglab back in June, but I've not released a new version yet. I've published 0.5.2 now with R6MK2 support. If you have still problems, please raise an issue.
I downloaded the new version. The analyze option now works, but when I try the extract option I get this error: Error: General error: TIFF: don't know marker 0x0.
This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.
I think this issue still happens in darktable 4.6.1. When opening a CR3 burst in darktable, I just see the first frame.
Yes, I think the issue still exists, even though libraw v0.21.0 lists support of "Canon CR3 filmrolls/RawBurst". So I'm not sure if it's now back in the dt court to leverage the functionality and determine how best to handle those files. I'm assuming that dt would need to extract all the images as separate filesystem files as an initial step so the xmp sidecars could be generated. Otherwise it would have to be a single xmp that somehow manages all the images contained w/in the single file and I'm not sure if dt supports that technique.
This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.