I also tried with the OpenEXR python bindings on Linux but I found that if I imported the module into Nuke and ran it in the script editor it crashed when I used the function to read the header, although that could have been due to the site-specific installation.
It would be best if the ViewMetaData node could read the compression type, in fact I have a feature request in for this from some time ago. Michael On 22 May 2012 19:32, Josh Imbruglia <[email protected]> wrote: > the only way i found to do this was by launching a subprocess for > exrinfo and then parsing through the piped output. > > if anyone knows of a simpler way i'd love to hear it. > > -josh > > On Mon, May 21, 2012 at 7:14 PM, Rich Bobo > <[email protected]> wrote: > > Hi, > > > > Anyone know a quick way to check EXR images to see if they were saved as > > 16-scanline zips or single-scanline zips? ViewMetaData reveals nothing > > about the compression type. I'm sure there's a command line invocation > that > > will show more - I just can't find it... > > > > Thanks for any help, > > > > Rich > > > > > > Rich Bobo > > Senior VFX Compositor > > > > Mobile: (248) 840-2665 > > Web: http://richbobo.com/ > > > > > > _______________________________________________ > > Nuke-users mailing list > > [email protected], http://forums.thefoundry.co.uk/ > > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
