Christoph Gohlke

Great. Thanks for re-running the benchmark! Are there any warnings from tifffile in the log output? > A remaining question is the first shot performance between the two. I think...

Thanks. Those are the same kind of warnings I get on files produced by MicroManager 2.0.0. I'll double-check my code against the [file format spec](https://micro-manager.org/Micro-Manager_File_Formats). The "coercing invalid ASCII to...

Turns out that some files written by Micro-Manager are > 4GB while the offsets in classic TIFF and the Micro-Manager header are 32-bit (< 4 GB). Hence the offsets to...

Moreover, the display settings, which should be UTF-8 JSON strings, are always (?) truncated and invalid JSON.

ImageJ metadata are also wrong for multi-file or combined multi-position datasets... Tifffile 2023.2.28 contains potential speed improvements and fixes for reading some corrupted metadata.

Those timings make sense. The tifffile series interface is a little faster because it now only reads the indexmaps from the beginning of the files and the OME-XML from the...

Tifffile v2023.3.15 includes a new parser for MMStack series and reverts the MicroManager specific optimizations for OME series. Positions are now returned as a dimension in the series rather than...

> Unfortunately, although tifffile can read arbitrary tiff files, it appears to be tripped up a bit by this one. For some reason tifffile doesn't produce a valid zarr view...

Duplicate of #100.

> ImportError: DLL load failed: %1 is not a valid Win32 application. Try to open `pymol/_cmd.cp37-win32.pyd` using [Dependencies](https://github.com/lucasg/Dependencies/releases) and check for missing or conflicting DLLs.