FYI, I'm thinking that the OIIO release plan is as follows:
VERY SOON, I will commit the last scheduled API change for OIIO core (allowing
channel subsets to be input) and then branch to enshrine that in a stable
Release 0.11. That will also contain all the other recent fixes in the trunk,
including the presence of oiiotool and deprecation of iprocess.
At that point the master trunk will be, we hope, the path to an official 1.0
release. The most important thing I want in 1.0 (and possibly the only thing
to alter the API further in that time frame) is integration of OpenColorIO.
Once that's done, I'd like to finally call it 1.0 and again create a stable
release.
In a very similar situation to OCIO, OIIO has been in production for years and
is very mature, but we've always hesitated to call it 1.0 because there was
always one more thing we wanted to squeeze in that might break the APIs. But
now we truly are down to just one more thing that would have a big impact on
the APIs -- OCIO. In truth, it will have little or no impact on the core APIs,
probably will only affect some of the utility functions and how the viewer
works.
-- lg
On Sep 6, 2011, at 2:14 PM, Jeremy Selan wrote:
FYI, OpenColorIO hasn't yet been integrated with OpenImageIO. But
we're looking to get that done this fall, once OCIO hits a 1.0 release
(hopefully just a few weeks away).
-- Jeremy
On Tue, Sep 6, 2011 at 2:06 PM, Kevin Wheatley
kevin.j.wheat...@gmail.com wrote:
Larry,
well I was trying to use as close to a stable release as possible, oh
and we don't use git, so I didn't want to track some development
stream in a tool I'm not familiar with, but if you can recommend a
revision to work from then I'm ok with trying it.
In particular if the core IO parts are stable but the tools are less
so, that is something I can OK for the rest of the team to work from,
as they are interested in file IO mostly. We're also interested in
working with OpenColorIO, if that impacts anything at all.
Thanks,
Kevin
On Tue, Sep 6, 2011 at 5:45 PM, Larry Gritz l...@larrygritz.com wrote:
How important is it to you to be locked to 0.10? In the development trunk,
we have iprocess being rapidly made obsolete by oiiotool, so I'm a little
hesitant to put any work into fixing iprocess.
-- lg
On Sep 5, 2011, at 8:45 AM, Kevin Wheatley wrote:
Hi,
Using oiio 0.10.2, I am unable to resize an image:
iprocess z.exr --resize 32 32 -o out.exr
fails with an 'assertion' at line 357 of iprocess.cpp
I'm assuming this is due to the files being half float and not 32 bit
float, is this expected?
Thanks
Kevin
--
Larry Gritz
l...@larrygritz.com
___
Oiio-dev mailing list
Oiio-dev@lists.openimageio.org
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
___
Oiio-dev mailing list
Oiio-dev@lists.openimageio.org
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
___
Oiio-dev mailing list
Oiio-dev@lists.openimageio.org
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
--
Larry Gritz
l...@imageworks.com
___
Oiio-dev mailing list
Oiio-dev@lists.openimageio.org
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
