I think 0.18 libraw should be fine. There may be fairly minor differences with
0.19.
A much bigger effect will surely be from the version of OIIO itself. We've been
through a couple rounds of beefing up raw metadata, with some big enhancements
fairly recently and only in master.
Yeah, just now I checked the current top-of-1.8 versus today's master. While
1.8 gives the basic Exif data, master also shows a whole lot of Canon-specific
stuff that comes from the "makernote" data that the older version was just not
reading properly. So I expect you to see lots of additional metadata in a
current master if you build it. For me, 1.8 had an output of 35 lines, whereas
master output 80 lines. That's still less than exiftool's output of 328 lines,
but I'm not sure if that's "real" info or just being extra verbose by reporting
default values for all sorts of things not really in the file. In any case,
please let me know if any specific metadata you need is still not in the set
that is recognized, and I'll see what I can do.
I'm very close to branching the current master make the basis of 1.9, so that
means any master-based fixes will be in a stable release in just a few weeks.
Also it means that if there are further fixes to make, now is the time to
ensure that I can get it in before the release.
-- lg
> On Oct 4, 2018, at 9:39 PM, Deke Kincaid <[email protected]> wrote:
>
> We have it linking against libraw 0.18.2 which is from 2017. I was already
> going to look at building against libraw 0.19.0 to see if that helped so I'll
> also try building from master. I have a similar camera at home to what the
> production files I'm testing with are shot on so I can send you a sample file
> if the new build does not give the same metadata results as exiftool.
>
> ought to shove all the metadata into the exr header. Again, it depends on
> whether it's reading it correctly and fully from the cr2 in the first place.
>
> Ok good to know. We weren't getting any metadata even the limited ones which
> oiio could see. So I wanted to confirm if this was intended or not.
>
> Also note that I believe that if you don't give it any extra hints, the
> underlying libraw will debayer the data into sRGB color space, so if you want
> your exr file to be linear response or in a different color space, then you
> might want something like
>
> Yes, we already set a lot of custom attributes for this based on our current
> raw conversion tool which is in the backend Nuke with a libraw reader node (
> output to xyz, convert to color primaries needed based on the show, pull the
> metadata from exiftool and add it into the exr). We are prototyping an
> updated version with oiiotool to make sure it will work but we were running
> into the before mentioned libraw from oiio not matching what we were getting
> out of Nuke. There is also some weirdness with the image rotation enum is
> incorrect and not matching what exiftool says but we saw a thread and a pull
> request where you also updated that recently too.
>
> Thanks Larry
>
>
> On Thu, Oct 4, 2018 at 9:09 PM Larry Gritz <[email protected]
> <mailto:[email protected]>> wrote:
> On Oct 4, 2018, at 4:45 PM, Deke Kincaid <[email protected]
> <mailto:[email protected]>> wrote:
>>
>> Two questions
>>
>> 1. Is there a special way to print/extract out all metadata from a raw file
>> via oiiotool? I am trying to use oiiotool —info -v blah.cr2 but I am
>> getting 1/8th the data that exiftool is giving me. I am using oiio 1.8.10
>> btw.
>
> Yes, `oiiotool -info -v` is supposed to be the way to print all the metadata.
>
> I did recently enhance the raw reader's handling of camera metadata, which I
> think is only in master and not 1.8, and also libraw itself improves from
> version to version (and I think some of the ways to pull out metadata from
> its API only work for more recent versions).
>
> Aside: `oiiotool --help` will, at the very bottom, tell you the versions of
> all the dependent libraries, so that's one way to see which version of libraw
> is built into your oiiotool.
>
> Is it possible for you to build the current OIIO master, making sure that you
> are building against a fairly current libraw (at least 0.18) and give a try?
>
> If the oiio master + libraw >= 0.18 are still not finding the metadata you
> are interested in, then I would be very happy to receive a cr2 from your
> camera to see what I can fix in oiio to make it get the data you need.
> Doesn't have to be proprietary show data, just snap a picture with the lens
> cap on for all I care, I just want the intact file with all the original raw
> metadata as written by the camera.
>
>
>> 2. When converting to an openexr, is there an expectation of it writing all
>> the metadata from the raw file to an openexr?
>
> Yes, I believe that
>
> oiiotoool in.cr2 -o out.exr
>
> ought to shove all the metadata into the exr header. Again, it depends on
> whether it's reading it correctly and fully from the cr2 in the first place.
>
> Also note that I believe that if you don't give it any extra hints, the
> underlying libraw will debayer the data into sRGB color space, so if you want
> your exr file to be linear response or in a different color space, then you
> might want something like
>
> oiiotool in.cr2 -colorconvert srgb lnh -o out.exr
>
> I'm kind of pretending here that srgb and lnh are color spaces your
> OpenColorIO config knows about.
>
> --
> Larry Gritz
> [email protected] <mailto:[email protected]>
>
>
>
>
> _______________________________________________
> Oiio-dev mailing list
> [email protected] <mailto:[email protected]>
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
> <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
