Closed KronosTheLate closed 6 months ago
Friendly bump
The upstream bug is closed. Should this be closed?
The issue is fixed over at TiffImages, which Images.jl now defaults to (I think). When using ImageMagick directly, both the standalong program and this JL package, the image is loaded without this artifact. In other words, I am unable to reproduce this bug when using
So it would seem the issue is resolved completely, despite the only relevant change that I know of being that TiffImages.jl started supporting LZW compressed tiff-images. But I can accept an automagical fix, and will therefore close this.
This issue arises from the discussion at Images.jl issue 1017.
Essentially, it was concluded that this package has a bug, causing an artifact to be produced when this .tiff image was loaded. There was no method for loading it in Images.jl, meaning that the fallback is this package.
I will not take the time to reproduce the issue with only ImageMagick.jl, so if someone would do that, we could close the original issue (1017 from Images.jl).