We were testing image rendering against some of our test set, and noticed one of them - pages.tif (included in the zip below) - was rendering incorrectly.

pages.zip

Iterating over the frames and saving each off as a PNG using the latest ImageSharp package releases (ImageSharp 3.1.11, ImageSharp.Drawing 2.1.7), we got back some sort of grid corruption:

However, then testing with all the latest changes in main cloned from the source repos, the problem was fixed:

Which is awesome! (Although I'm not sure yet what the actual merge that fixed it was. I presume one of these - https://github.com/SixLabors/ImageSharp/issues?q=is%3Aissue%20tif%20state%3Aclosed - but I'd have to dig into it more to find which specific one did it.)

Now on our end, we're just trying to figure out the plan for getting the fix incorporated. We still have a couple months before we need to package up our own code incorporating ImageSharp, and so if there's a minor version fix upcoming that'll include the tiff fixes, we can just wait for that. Otherwise, we'll probably need to clone the repo and cherry-pick out the tiff fixes onto one of the existing 3.1.X release branches. And that's doable, but not ideal in our setup, so if the tiff fixes can be packages in the near future, it would make things a lot simpler for us.

Either way, thank you for the work maintaining and cleaning up these edge case bugs in the decoders!