> 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.
> implement support for CR3 in an open source image processing software All we really need is either non-NDA docs about CR3 format spec or some sort official "go ahead and make your own damn cr3 reader, we don't care". > Is something as high-level as "metadata and image data specification" sufficient? Yea. non-nda docs or official statement of "we don't care about you implementing your own reader" > They're also asking for company name and business address That's for business entities. darktable org isn't a business entity and is volounteer work. you can say that if they request that. > 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". pt., 13 lis 2020 o 13:50 Mikko Rasa <t...@tdb.fi> napisał(a): > 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? > > -- > Mikko > -- Pozdrawiam, Hubert Kowalski ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
