Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extracting RAW Images from Canon Raw Burst Mode file (CSI prefix, .CR3 extension) doesn't set output DNG image previews correctly #447

Open
carsongmiller opened this issue Apr 30, 2024 · 4 comments

Comments

@carsongmiller
Copy link

When you extract DNG's from a canon raw burst mode file, each of the resulting DNG's has the same image preview attached to it--the preview of the original CR3 file. This means that in lightroom, in the library module it doesn't show the actual image--just the incorrect preview. This is also true in the develop module for a few seconds before loading each image as you flip through them, and in windows explorer.

This makes using DNGLab to do this task much less useful. Would be great if there was a way to generate a new preview image for each output DNG so that each DNG's preview represents it correctly

@Gendra13
Copy link

Hi,
what command line options do you use? I assume --image-index all --embed-raw false.

Did you try including --dng-preview false --dng-thumbnail false?
For my test images it seems to fix this issue because then lightroom is forced to create the preview image on its own.

Unfortunatly I currently don't have access to a R7 oder R6II and the test files I have here are without much "action" between the single images.
Would it be possible to share a .cr3 testfile where there is an obvious difference between the embedded images?

@carsongmiller
Copy link
Author

Interesting idea, but I just tried it and unfortunately it doesn't give me the results I'm looking for. Now when looking at photos using the built in photos app on windows, it does indeed load the full DNG. But importing those same new DNG's into lightroom yields the same behavior as before: in the library module, the images all look identical, and in the develop module, when you flip to an image it initially shows the image preview of the first shot in the roll, then switches to the actual DNG after a second or two. Not a great experience, and I'd rather actually just extract individual images in-camera, since that actually seems to be the lowest-pain option.

If you do want a test raw burst mode image to test with (from a Canon R8), here is a google drive link to one.

@Gendra13
Copy link

OK, that's unfortunate. I wonder where lightroom takes his preview image from when there shouldn't be one embedded into the dng.
However, what seems to work in my case is to create an 1:1 preview in lightroom on import. Of course this requires a lot of additional processing, but at least then the correct images are display in the library.

Of course it would be much better if it would be possible to directly include the correct preview when creating the dng (or for canon to fix this b***hit way of creating a roll file instead of single raws) .

@carsongmiller
Copy link
Author

Oh so did you actually get it work work in lightroom where I did not?

Yeah, I really do think at this point just selecting candidates in-camera is the way to go. It's really not much of a hassle. But definitely ridiculous that Canon does give a software solution but that it sucks this bad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants