From what I've been following the issue, it's a problem of some of the
exiv2 maintainers fearing legal repercussions. These legal repercussions
don't seem to actually be very likely, but this is still something that
needs to be hashed out in exiv2's kitchen before darktable can do
anything about it, so posting on darktable-dev about how darktable
developers are being overly cautious isn't going to help - it isn't
*them* blocking this. The email-Canon solution was tried already, they
answered with some non-commital
we-can't-invest-resources-in-this-but-aren't-saying-anything-about-you-doing-so-either,
the exiv2 hardliners were apparently not satisfied, and the story
continued...
I suggest the exiv2 bugtracker if you'd like to keep an eye on what's
going on https://github.com/Exiv2/exiv2/issues/1229 . Once they manage
to sort out these issue, the codefix is apparently quite simple (and has
been implemented by some users in their private copies of exiv2,
apparently) so it shouldn't be long until it shows up in exiv2, and then
darktable will likely not take too long either.
I'm sure some of the darktable devs can better describe just how much
work would be to use libraw in parallel to exiv2 - I'm not an expert,
but I believe the two aren't exactly isomorphous.
Hope this helps,
Ruxandra
On 11/13/20 2:50 PM, Mikko Rasa wrote:
On 12.11.2020 21.59, Hubert Kowalski wrote:
Before you gave money to Canon, you could have checked the status of
exiv2
and rawspeed.
Maybe I should have. But it's too late for that now. I also have a
collection of Canon lenses accumulated over the years, and while there
are mount adapters available for other brands, they seem to come with
restrictions of what combinations of camera body and lens work well.
Here's what you should do:
https://discuss.pixls.us/t/canon-cr3-raw-support-your-move/14192?u=johnny-bit
Sure, I could send a request to Canon. Given that they're likely to
ask me the same information as Morgan there, perhaps you could help me
in advance with a couple of the items?
Nature of the project: I assume this would be "implement support for
CR3 in an open source image processing software" or some such?
Request: What should I put here? What's the exact information you
need? Is something as high-level as "metadata and image data
specification" sufficient?
They're also asking for company name and business address. I have my
own, but it has nothing to do with Darktable. If they don't require
an NDA, this is probably fine. But what if they do? I don't really
have the time to implement the support myself.
For time being you can convert your CR3 to DNG with no loss of image
information and metadata.
That's not an ideal solution as it requires a Windows application, but
I may end up doing that.
Remember - YOU supported canon with your purchase, you should expect
THEM
to help open source devs with CR3 support, not other way around.
Yes, Canon supporting developers would be ideal. But the fact remains
that libraw has implemented CR3 support without Canon's help. Your
link above indicates that metadata should be supported as well, though
my own experiments fail to verify this.
I'm simply interested in knowing what the holdup is. Are you being
more cautious about the legal issues than libraw and digikam
developers, or do you want to wait until the support can be
implemented perfectly, or something else?
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
