I have tagged Release-1.1.10. This is more feature-heavy than most updates we push to stable branches. But in this case, they are requested by specific users, and are sufficiently orthogonal to existing functionality that I don't see how they can break anything (and they don't alter existing API or linkage.
The release notes are as follows: (Excuse the old date; 13 Apr is when the last fix for this release was integrated into RB-1.1, but I didn't end up pushing the tag until today, Apr 22.) Release 1.1.10 (13 Apr 2013) ---------------------------- * IBA::fillholes() and oiiotool --fillholes can smoothly fill in alpha holes with nearby colors. Great for extrapolating the empty areas of texture atlas images so that filtered texture lookups pull in a plausible color at part edges. * IBA::clamp and oiiotool --clamp clamp pixel values to a scalar or per-channel min and/or max, or clamp alpha to [0,1]. * IBA::rangecompress()/rangeexpand(), and oiiotool --rangecompress / --rangeexpand compress the excess >1 values of HDR images to a log scale (leaving the <= 1 part linear), and re-expand to the usual linear scale. This is very helpful to reduce ringing artifacts that can happen when an HDR image is resized with a good filter with negative lobes (such as lanczos3), by doing a range compression, then the resize, then range expansion. It's not mathematically correct and loses energy, but it often makes a much more pleasing result. * maketx --hicomp does highlight compression -- automatically doing a range compress before each high-quality resize step, and then a range expansion and clamp-to-zero (squash negative pixels) after each resize. * DPX - when writing DPX files, properly set the pixel aspect ratio. Release-1.1.10 is the current recommended stable production version, and will never change. RB-1.1 is the tip of the stable 1.1 branch where fixes (and occasional new features) will be added to eventually become 1.1.11, but within the RB-1.1 branch we will never break backwards compatibility with the API or linkage. The "master" branch is where new, risky, or non-back-compatible changes will happen; use it at your own risk. Older branches (1.0 and 0.x) are considered obsolete and will only be patched at the request of users who are still using them. Reminder: You need to "watch" the project on GitHub to see the individual pull requests for new code. I assume that anybody interested in the code itself, or features as they are being worked on, will do so. We no longer echo each pull request to this mail list, unless there is a need for an extended design discussion that would be of interest to people not actually working on the code. -- Larry Gritz [email protected] _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
