Doesn't ring a bell for me, but 2.1.9 is from late 2019, so maybe it's something that has long since been fixed?
https://github.com/microsoft/vcpkg/blob/master/ports/openimageio/vcpkg.json <https://github.com/microsoft/vcpkg/blob/master/ports/openimageio/vcpkg.json> Seems to indicate that the current vcpkg recipe for OIIO will build 2.3.10.1. That's not the very latest, but it's pretty close. So you ought to be able to build that with vcpkg easily and test a relatively up to date version. -- lg > On Jan 28, 2022, at 2:31 PM, Jonathan Tilden (2K) <jonathan.til...@2k.com> > wrote: > > Hey there! > > I’m writing images with OIIO 2.1.9 in Python 3.7 x64 on windows. It was built > using vcpkg. > > I’m seeing some issues where the output of different image types (such as jpg > or tif) are getting “corrupted.” I use the quotes because that’s what > Photoshop tells me, but sometimes it can actually read the pixels just fine. > > This can happen with a simple bit of Python: > - Create an ImageBuffer for a file > - Immediately write it out as a different file > > I’m wondering if that’s an issue a few of the other Windows users have seen? > > My alternative approach would be to rebuild the libs “by hand” like I did > with OIIO 1, and see if I can get a better result. > > Thanks! > -J > _______________________________________________ > Oiio-dev mailing list > Oiio-dev@lists.openimageio.org <mailto:Oiio-dev@lists.openimageio.org> > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org > <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org> -- Larry Gritz l...@larrygritz.com
_______________________________________________ Oiio-dev mailing list Oiio-dev@lists.openimageio.org http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
