Agree. On a different note, If only Mari would integrate OIIO, and also support mipmap for both import and export, It would save use a lot of disk space. Generating ready-to-render texture straight out of painting package is very useful. So doing it for Nuke would be great too, as long as performance isn't affected.
my 2 cents. Dave. Dave Lajoie R&D Director | Directeur R&D [image: Digital-District] <http://www.digital-district.fr> 5605 Avenue de Gaspé, Suite 408 | Montréal, QC H2T 2A4 Tel (514) 360-3253 ext. 130 On Mon, Oct 13, 2014 at 4:48 PM, Larry Gritz <[email protected]> wrote: > For those of you who read the mail list but don't "watch" the GitHub > project to get alerts to all the individual pull requests: > > https://github.com/OpenImageIO/oiio/pull/973 > > This proposed patch builds Nuke nodes to read and write OIIO's style of > texture files. (And PRMan's as well, for places that use the TIFF or > OpenEXR variety, not the old proprietary format.) The writer is particular > neat -- it basically is like having 'maketx' bundled up in a Nuke node, > writing out as a tiled MIPmap whatever image is fed in from upstream. > > Of course, this only builds if Nuke dev libraries are found on the system > at build time, otherwise it smoothly skips over them, just like happens for > various file formats when the underlying libraries are not found. > > It all seems like a good idea to me, potentially useful (obviously so, for > the people who wrote it, so presumably for others as well), but since I've > never written Nuke plugins myself, it would help me out for others to > review the code who know more about it than I do, for example, people who > know enough about the Nuke internal APIs to recognize if it's being > implemented sensibly and in the common style for such things. Also, those > who think such a plugin might be useful for themselves, please do comment > on whether the functionality is in line, or if other controls need to be > added, etc. > > Thanks. > > -- > Larry Gritz > [email protected] > > > > _______________________________________________ > 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
