Hi guys,
2 super simple questions about DPX metadata -- my apologies if these are
obvious:
(using OIIO 1.1.2 on CentOS 6.2)
1. I notice if I simply read in a DPX with a PixelAspectRatio of 2 and
write it right back out without any ops, the PixelAspectRatio changes to 1
-- dpx:Signal also seems to
Thanks for the quick update Larry.
Since the userData isn't available quite yet, might you be able to verify the
correct syntax to set the DPX metadata using a key that is working? e.g.
"PixelAspectRatio"? I was thinking it would be this:
oiiotool my.dpx --attrib "PixelAspectRatio" "0.5" -o tes
Hi guys,
Using the OIIO Python bindings (compiled against OCIO), how do I get the
equivalent of the C++ API's ColorConfig or the command line’s “—colorconfig”
so I can use multiple OCIO configs within a single Python function? Looking at
the 1.6 docs, I’m only seeing it for C++.
Many thanks,
Thanks for confirming, Justin.
I’ve submitted a pull request (#1187) that exposes the ability to specify
different ColorConfigs via the python bindings.
___
Oiio-dev mailing list
Oiio-dev@lists.openimageio.org
http://lists.openimageio.org/listinfo.cgi/o
Hey Justin,
That commit of Larry’s appears to be for the ColorConfig on C++ side of things.
My pull request simply exposes the ability to specify which colorconfig to use
when using the python bindings' imageBufAlgo methods.
With regard to the contexts, as you said, it’s a matter of updating OI
Hi everyone,
I'm guessing the answer is right in front of me in the docs and I'm just
missing it but...
Is there a way to do a 2d transform using the OIIO Python API? In this case,
I'm looking for an integer based reposition to avoid filtering but I'm sure
I'll need sub-pixel transforms in the
Thanks Larry.
The integer based transform worked like a charm.
The warp, however, wasn’t working as expected. I tried it in both OIIO 1.6.4dev
and 1.6.10. Basically, when I enter any value other than “0” (zero) as a
transform value in the matrix, I get a very dark (if not negative) image. I’ve
laid out wrong. Instead of
> >
> >> oiio.ImageBufAlgo.warp(xform, src, (1, 0, x_offset, 0, 1, y_offset, 0,
> >> 0, 1))
> >
> > you want
> >
> > oiio.ImageBufAlgo.warp(xform, src, (1, 0, 0, 0, 1, 0, x_offset,
> > y_offset, 1))
> >
&
I second the vote for #2
On Sep 21, 2016, at 9:59 AM, Deke Kincaid wrote:
> I like #2.
>
>> On Wed, Sep 21, 2016 at 9:36 AM, Larry Gritz wrote:
>> So in following the spirit of OIIO's core mission to allow a single generic
>> API to shield users from the gory details of each individual forma
Hi everyone,
Is it possible to pass more than one OCIO context key/value pair to the
ImageBufAlgo functions via the C++ and Python API’s?
Passing a single key/value pair to ImageBufAlgo’s ociolook function is simple —
I’m looking for a way to pass multiple pairs.
Cheers,
Jep___
Thanks Larry.
I’m in the camp for keeping it flexible, if possible. Along the lines of your
point, I hadn’t needed more than one key/value pair for years; and now I’m
finding I need two, possibly three. Would passing a map/dictionary be the way
to go?
Also, would it be possible to roll-in what
Thank you for the options.
Options 1 and 4 have the appeal of keeping the key/value pairs together; and of
the two, I do like option 1 for the fact that it’s foolproof. However, wouldn’t
this require adding a new version to each OCIO related function?
Option 3 would be backward compatible and I
This is great to see — thank you, Larry.
Is it possible to add this context magic to ImageBufAlgo’s “colorconvert”
function as well? Both the C++ and Python API’s allow us to pass a
“colorconfig” so it would be great to be able to set the context(s) in the
function. While it will add an additio
Thanks again, Larry. I built it last night but haven’t yet had a chance to put
it through it’s paces. I’m looking to test it this evening and get back to you.
This will be very helpful for facilities that use a $SEQUENCE/$SHOT_NUMBER
paradigm; and in the cases where colorspace definitions contai
I’ve tested ociolook and colorconvert; and both are working as expected when
passing a comma delimited string for multiple context keys and values.
I haven’t been able to confirm ociodisplay yet due to the fact that it
segfaults without passing any context whatsoever — even on previous builds. I
15 matches
Mail list logo
