There's actually a bug in oiiotool here, fix submitted: https://github.com/OpenImageIO/oiio/pull/610
Regarding the * wildcard, if you have such long paths and many frames you might run into command length limits on Windows, it's lower than other operating systems. On Thu, Jun 6, 2013 at 4:36 PM, Andrew Wood <[email protected]> wrote: > flying blind here, but if your frame padding is 4, the string would look > like this > > __vc_beauty.####.exr > > (and with --frames 1-71 --framepadding 4) > > I believe normal cmdline * syntax works too, if you are just looking to > query the exr info. as in __vc_beauty.*.exr > > > > > Andrew Wood > Pipeline Engineer, Digital Domain > x2914 > > > On Thu, Jun 6, 2013 at 3:12 AM, Julian Johnson <[email protected]> > wrote: >> >> 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 > > > > _______________________________________________ > Oiio-dev mailing list > [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
