Improve Capture One
Request a new feature, or support for a camera/lens that you would like to use in Capture One.
Request a new feature, or support for a camera/lens that you would like to use in Capture One.
What problem do you see this solving?
Capture One will not allow import of DNG files processed in any Adobe raw tool once the file has been processed into a DNG using Adobe's Enhance Denoise reduction tools.
At present, Adobe's Denoise is buying me the equivalent of at least a stop - perhaps two - of high ISO shooting capability through its noise reduction techniques. Although I'd much prefer to use Capture One to process the resulting Enhanced DNG files, Capture One will not enable this as it will not allow import of such files.
When was the last time you were affected by this lack of functionality, or specific tool?
This is affecting me within my regular workflow, so it's a constant and ongoing limitation. I'm presently having to use Adobe tools as I'm unable to use Capture One to process these DNG files.
|
Current workaround
Are you using any workarounds or other solutions to achieve your goals in Capture One? There are no workarounds that I'm aware of, other than (reluctantly) migrating to use Adobe tools to process these DNG files rather than Capture One. |
It appears that this is now "Implemented" in 16.3.4.5.
I updated Capture One today and all Enhance-NR.dng files are now appearing and editable.
...however, there are no lens corrections available for the resulting DNG file in Capture One, as the file is not corrected for distortion, and no Distortion, Sharpness or Light Falloff settings are available for the image (shot with a Nikon 14-24S on a Z9) even though the metadata for the file does correctly reference the lens, focal length, aperture, and camera used to create the original raw file.
To the moderators here. Should this feature request now be tagged as "Being Worked On" or whatever the appropriate tag is for something that Capture One has acknowledged they will implement?
Agreed - I have LR Denoise images that were converted at that time which were, and still are, readable in Capture One, but any images processed after the change to how LR compresses the Denoise-processed images has now resulted in Capture One not being able to even see those images as importable files.
I'm really missing having Capture One to use in processing my images, and hope this can and will be resolved soon.
A real problem that seriously impedes workflow and limits my low-light situations to Lightroom. Reported it back in early November. Understand it is now on their bug list. Agree that when Adobe first introduced LR denoise there was no issue, those dng files still can be worked on. Sadly didn't remain that way for long, fingers crossed remedied soon.
This started when Adobe updated their DNG format. Capture One doesn't yet support the newer DNG format.
If this is something that used to work and now no longer works, you may benefit from filing a support request and marking it as a bug report.
I believe this limitation started with the new release of Capture One 16.3 (when they introduced the AI subject masking)...because I remember using this technique a few months ago with version 16.2 and didn't have issues importing the DNG created by Adobe Camera Raw back into Capture to continue my manual process.
Maybe is a combination of Adobe Camera Raw 16 and Capture One 16.3
In any case, please find a solution to make this files accessible to CaptureOne please
There's lots of discussion about the DNG format that results from using Enhance against raw files on Adobe and other sites, so my hope would be that Capture One would be able to deal with this using the information that's in the public domain.
I don't feel it's appropriate to link to other sites here, but a quick search on the web will turn up plenty of information.
I would guess that Adobe is creating a newer version of the DNG spec and C1 is not yet ready to read that. David, perhaps you could add to your report what DNG version Adobe is producing? If you're on a Mac, here's a way to tell. You can presumably do something similar on Windows or perhaps exiftool will show it.