Hi,

Apologies for such a newbie question but I'm just evaluating oiio and the prebuilt Windows binaries of 1.11.0 hosted here:

http://www.lfd.uci.edu/~gohlke/pythonlibs/#openimageio

with a view to making my own build and integrating with some our existing studio tools (and ocio) and failing spectacularly to get the prebuilt oiiotool to 'batch' convert or display info using wildcards (including using the new --frames and --framepadding options).

Here's the simple argument string:

oiiotool -v --info \\flabby\jobs\coors_bionic_can_3070\3d_data\CBC_coors_bionic_can_beach_sdb\Render_Pictures\shot_07\CBC_beach_07_R_lighting_v29__vc\CBC_beach_07_R_lighting_v29__vc_beauty.0001.exr

Which works fine and displays 'info' for a single .exr. But when I try with a wildcard:

oiiotool -v --info \\flabby\jobs\coors_bionic_can_3070\3d_data\CBC_coors_bionic_can_beach_sdb\Render_Pictures\shot_07\CBC_beach_07_R_lighting_v29__vc\CBC_beach_07_R_lighting_v29__vc_beauty.#.exr

I get:

Could not open file '\\flabby\jobs\coors_bionic_can_3070\3d_data\CBC_coors_bionic_can_beach_sdb\Render_Pictures\shot_07\CBC_beach_07_R_lighting_v29__vc\CBC_beach_07_R_lighting_v29__vc_beauty.#.exr'

I've tried numerous options (including setting --frames 1-71 --framepadding 4) but with the same result.

Should this be working in 1.11.0 and is it just a question of building it from scratch instead of relying on the prebuilt binaries? or, am I just making some stupid mistake with the command line options?
Julian

_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org

Reply via email to