darktable
darktable copied to clipboard
Canon EOS R50 Noise Profile
Hey there, I have created a noise profile for Canon EOS R50, I hope this is helpfull.
Fyi, there is no base support for the R50 yet: https://github.com/darktable-org/darktable/issues/14549#issuecomment-1558554926
Oh hey, thank you for the heads up! Interesting, I was able to open and edit the RAW and cRAW files... Well I will then wait for it to be officially supported and create the noise profile again after that. Just in case something changes with interpreting these files.
Interesting, I was able to open and edit the RAW and cRAW files...
Yeah, the underlying LibRaw library used for reading CR3s doesn't necessarily give up (or warn you) for new/unknown cameras, but gives you a best string match - in this case you're probably getting the input profile of an R5...
@ralfbrown Please change the label to "noise profile" for this one and assign @rawfiner
Done. But if there isn't actually proper base support for the R50 yet (rather than your surmised fuzzy match by LibRaw), shouldn't this also be tagged "camera support"?
We'll deal w/ base support (pretty much for all new Canons at once) when LibRaw releases it. I guess we could have both labels, why not...
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.
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.
Does the new Libraw release mean that Darktable now has, or will soon have, support for the R50?
Does the new Libraw release mean that Darktable now has, or will soon have, support for the R50?
Unfortunately not yet - it is only a minor bugfix release, not a "major" public snapshot w/ added camera support: https://www.libraw.org/#updatepolicy
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.