Coincidentally, I was just looking into this a couple weeks ago.
You can download their SDK for free, and while you obviously can't redistribute
it, ordinarily there would be no particular reason why you couldn't link
against it if you built the software yourself (i.e., an optional dependency
that would enable r3d support if the r3d SDK was found on the system and
presumably properly licensed by the studio at the time that they built their
in-house copy of OIIO).
But, reading their license, I found it ambiguously worded to the point of being
incomprehensible. It was just not clear if they disallowed only distribution of
their code (which would be expected) or if they were trying to disallow even
*calling* its API (which would be very unusual). It seemed clear that it was OK
to call it for in-house software, but the wording was such that it didn't spell
out the rules for open source software. It's not a matter of trade secrets;
like I said, anybody can download their SDK and headers from their site.
I wrote them a letter explaining the situation and asking for clarification,
but never got a reply at all.
If anybody knows somebody there who could be put in touch with me, please let
me know. I would think that in a reasonable world, they would recognize that
OIIO support could only help their customers and would be of no particular help
to their competitors. So I can't even fathom what the objection would be. But I
won't do it if I can't get a clear word from them that it's not violating their
license.
-- lg
> On Jul 22, 2019, at 6:19 PM, Colin Doncaster <[email protected]> wrote:
>
> If I recall R3D requires a specific license from Red to use and there might
> be sticky specifics about integrating into open source libraries, this could
> be the reason why libraw may have discontinued updates?
>
>> On Jul 22, 2019, at 6:07 PM, Alex Hughes <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> Hey I was wondering if OIIO supports reading r3d files.
>>
>> I was looking through the release notes for libraw and that states that it
>> could read r3d files.
>> https://www.libraw.org/node/1299 <https://www.libraw.org/node/1299>
>>
>> However, that was in 2011 and I would imagine things could have changed
>> since then.
>>
>> My oiiotool seems to seg fault when I try to read r3d files and I was
>> wondering if ti was even supposed to support r3d or if my build was just
>> broken in some way.
>>
>> I know Red likes to sell their SDK, but I was sort of hoping that LibRaw had
>> an implementation that we could rely on.
>>
>> Thanks
>> -Alex
>> _______________________________________________
>> Oiio-dev mailing list
>> [email protected] <mailto:[email protected]>
>> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
>
> _______________________________________________
> Oiio-dev mailing list
> [email protected]
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
--
Larry Gritz
[email protected]
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
