On 13.11.2020 19.36, Andy Dodd wrote:
As to Canon - the problem is no longer them. The issues that have been
raised by the exiv2 team aren't Canon-specific with ISOBMFF, and in fact so
far have been bogus.
The only cases where Canon themselves might be problematic are reading the
actual CR3 codec - but guess what, that code is already available because
despite actually having IP liability concerns, it's not in exiv2's
wheelhouse, and the developers of the components actually responsible for
the codec are being more reasonable/less paranoid, it's the metadata that
is the problem.
Well, I had already contacted Canon before your message. Perhaps not
too surprisingly, I got back a largely noncommittal response saying how
they can't provide support to me in using Darktable and they recommend
using their Digital Photo Professional software.
Their message did contain this interesting bit though: "Unfortunately,
Canon does not provide the CR3 format specifications to application
developers. Third party software developers will update their software
after studying and reviewing the CR3 file format. You would need to
reach out to the developers of Darktable for further assistance."
This seems to indicate that any software vendor - including big ones
like Adobe - is expected to figure out the CR3 format on their own.
While this is not a legally binding statement, it does seem like we'd be
fine just using the reverse engineered implementation. Since you said
the problem is no longer Canon, I don't think it's worth pursuing
further answers to them. Let me know if you'd still like me to try and
get an actual promise out of them.
--
Mikko
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
