I've tagged OIIO Release-1.1.4, which contains a variety of fixes and low-risk 
additions that people have asked for.  Release notes are as follows:


Release 1.1.4 (27 Jan 2013)
---------------------------
* ImageBufAlgo::make_texture() allows you to do the same thing that
  maketx does, but from inside an application and without launching a
  shell invocation of maketx.
* oiiotool now recognizes --metamatch and --nometamatch arguments which
  cause metadata names matching (or only info NOT matching) the given
  regular expression to be printed with --info.
* oiiotool --zover does z (depth) composites (it's like a regular "over",
  but uses the z depth at each pixel to determine which of the two images
  is the foreground and which is the background).
* ImageBufAlgo::fixNonFinite didn't work properly with 'half' image buffers.
* Performance improvements when reading and writing images.
* Fix error when writing tiled 'float' TIFF images, corrupted output.
  (Could easily happen when using 'maketx' to convert float images into
  TIFF textures.)
* Eliminate warnings when compiling with Clang 3.2.
* New CMake variable "USE_EXTERNAL_TBB" can optionally be set to force use
  of an external TBB library rather than the embedded one.
* Additional testsuite tests (doesn't affect users, but makes bugs easier
  to catch).
* Fix build problem with SHA1.cpp on some platforms.


Reminders:

1. The 'Release-1.1.4' tag is the latest tagged, stable production release.  It 
will never change -- additional low-risk important improvements will be 
back-ported to the RB-1.1 branch, but the next official release tag there will 
be for 1.1.5.  In any case, nothing added to RB-1.1 will ever (we believe) 
change existing API calls or break binary or link compatibility.

2. The "master" branch is where new development happens. This will eventually 
become the stable 1.2 branch, but for now, we make no guarantees about 
compatibility changes in "master" -- changes could happen at any time that 
alter the API or break linkage compatibility.

3. We're happy to back-port important fixes to earlier release branches (1.0 or 
even 0.10) if we can, but at this point, such back-ports to older branches only 
happen if people specifically request it.

--
Larry Gritz
[email protected]


_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org

Reply via email to