.tx files are just .tiff or .exr files that have been renamed .tx. I think as long as you generated the .tif/.exr file with maketx, it'll be the exact same thing. You can confirm by looking at your files with the "iinfo -v " oiio tool. Calling it .tx just helps in letting people know that the texture has already been optimized without forcing them to parse the file and look at the file attributes.
Just to be clear, a .exr/.tif that was not made with maketx will not perform as well since it doesn't have the AverageColor or SAH-1 oiio attributes. Finally, don't take a .tx file, rename it to .exr, edit it in photoshop, and rename to .tx. Do that and now it's no longer an optimized file. In fact, you might even get rendering artifacts since the AverageColor and SHA-1 attributes could be wrong. On Tue, Dec 22, 2015 at 5:36 PM, Bruce Tartaglia < [email protected]> wrote: > Hi all, > > I am using OIIO to manage mipmapped texture lookups, > and I have a question about the exr vs the tx format. > > In brief, is there a preferred / optimized format for the OIIO library? > Both seem to work quite well, both support mip mapping, half > data formats, maketx --oiio flag, and tiling. So is one superior to > the other? > > I suspect that tx is likely closer to an internal, native OIIO format, > so perhaps exr incurs a data conversion cost, but I have not proof of > that. > I am starting to read the OIIO code to best understand this, but I thought > I could simply ask here as well. > > Any information is appreciated, and thank you for such > useful software. > > Best, > > Bruce > > _______________________________________________ > 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
