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. Not a single person raising patent fears with respect to exiv2 ISOBMFF support can point to a specific patent that they have concerns with. This is despite the fact that all known patent issues with the various MPEG codecs are with the actual AV codecs themselves, and not the container format. There's also the fact that AOM has chosen to adopt the ISOBMFF container format for AVIF, proving conclusively that *ISOBMFF itself does not have patent liability issues* but certain exiv2 developers refuse to have a logical argument on the subject... On Fri, Nov 13, 2020 at 11:25 AM Mikko Rasa <t...@tdb.fi> wrote: > On 13.11.2020 15.45, Hubert Kowalski wrote: > >> Sure, I could send a request to Canon. > > > > Point is to do the request politelly and explain that you use free/open > > source software, just to make canon aware of growing userbase that wants > > their cameras supported. > > > >> Are you being more cautious about the legal issues than libraw and > > digikam developers [...] > > > > Problem arose with exiv2 holdup relating to possible legal issues > > concerning developers/implementors/endusers of exiv2 and without exiv2 > > darktable can't move forward with raw decoder implementation as metadata > > reading relies on exiv2 metadata support. The exiv2 works to have it > > cleared and futureproof, so we're constantly "clear". > > All right, fair enough. I'll see if I can extract any better response > from Canon. One could hope they'd have warmed up to the idea in the few > months since the last time this was asked (that I know of). > > -- > Mikko > ___________________________________________________________________________ > darktable developer mailing list > to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > > ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
