Release of OME Files C++ 0.2.1

The OME team is pleased to announce the release of OME Files C++ 0.2.1

back to Announcements

OME Files is a reference implementation of the OME Data Model and OME-TIFF file format for the storage and interchange of biological imaging data and metadata. It provides support for:

The major focus of this release was to port the most recent changes from the OME-TIFF reader and writer from Bio-Formats Java to OME Files C++. This means that the support for reading broken, non-standard and complex OME-XML and OME-TIFF files is much improved. It is now possible to read all OME-TIFF metadata using the 2007-06 schema and above.

Note that the predecessor to OME Files, Bio-Formats C++ 5.1, is no longer maintained or supported, and no further releases will be made. If you are using Bio-Formats C++, upgrading to OME Files is strongly recommended.

Major changes in this release include:


The software release is available at archived downloads.

This page includes links to the individual repositories and source releases, as well as the documentation and binary builds of the collection for several common platforms, including Windows, Linux and MacOS X.

Changes since OME Files C++ 0.2.0

OME Common


OME Files

OME QtWidgets

Super-Build 0.2.1

Future changes

Upcoming improvements include:

OME Files


Note that this is a work in progress and subject to change.


Support for building on Windows with msbuild is currently non-functional; please use Ninja for the time being.

Debug builds on Windows may display “Run-Time Check Failure #2 - S” when reading some OME-TIFF data; this will be addressed in the next point release.

On Windows, “ome-files info” will display an error if run from a directory containing a space in it. As a workaround, use “libexec\ome\files\info.exe” directly.

The “ome-files” command on Windows may not work fully on every single Windows version due to being new and having not been tested with every possible Windows configuration. If you encounter any problems, please let us know and we will correct them for the next release.


For problems or comments, please use the OME Forums or mailing lists

back to top