created/overwritten/copied TIFF images are invalid for Adobe Premiere Pro

[MaciejSzulborski]

Prerequisites

• I have written a descriptive issue title
• I have verified that I am running the latest version of ImageSharp
• I have verified if the problem exist in both DEBUG and RELEASE mode
• I have searched open and closed issues to ensure it has not already been reported

ImageSharp version

2.1.3

Other ImageSharp packages and versions

SixLabors.ImageSharp 2.1.3, SixLabors.ImageSharp.Drawing 1.0.0-beta14, SixLabors.Fonts 1.0.0-beta17

Environment (Operating system, version and so on)

Windows Server 2019 Standard 1809

.NET Framework version

.Net 6.0, .Net Framework 4.8

Description

Tiff files created by ImageSharp are not recognized by Adobe Premiere Pro on any try of import.
If you try to import a tiff file an error will pop up: "The file cannot be opened because of a header error"
If you take a tiff file created by ImageSharp, open it with Paint or Adobe Photoshop and save it without any changes, choosing TIFF format, Importing files to Premiere Pro becomes possible.
It seems there is an issue, when encoding the tiff image by ImageSharp since other software can save the image in format properly. I could not find any differences in metadata that would indicate which parameter is invalid.

Steps to Reproduce

using Image<Rgba32> image = new(1920, 1080);
using MemoryStream stream = new();
image.SaveAsTiff(output);

Images

[brianpopow]

What is the memory stream used for in your repro? Seems unnecessary.

The following should be enough:

using Image<Rgba32> image = new(1920, 1080);
image.SaveAsTiff("output.tiff");

I kind of doubt that there is an issue with "the file header" of ImageSharp tiff's.
tiffinfo from libtiff does not report any errors. ImageMagick with imagemagick identify -verbose does not report any error.

Also I can open ImageSharp Tiff images with any viewer I have:

• gimp
• pant.net
• xnview
• imagemagick
• irfanview
• paint

None of those complains. I do not have access to Adobe Premiere Pro.

[MaciejSzulborski]

Hi, Thank you for a prompt reply. The memory stream was my bad, I forgot to delete it after simplifying my example. I have to agree with you about the header, I took the stream of the file to decode the header into hexdec string, and read about tiff format headers. It all seems fine. I also read on various blogs that Premiere Pro "header error" is an unhandled exception for any issues when importing files. I have spent several hours with their support trying to get them to tell me what exactly makes the file crash but no luck, "file is no good" is the best I got out of them. I conducted multiple tests, creating files in all possible ways using ImageSharp. I don't have this problem with png or jpeg. I created a file in Photoshop to ensure that it works fine in Premiere pro, it's the same FullHD Black background (valid.tif attached). I thought if I load it via ImageSharp and just Save a copy of it without any changes (Copy.tif attached), the file should be identical, therefore be acceptable for Premiere Pro. using Image image = Image.Load(fileToCopy, out IImageFormat format); using MemoryStream stream = new(); image.SaveAsTiff(stream); File.WriteAllBytes(outputPath, stream.ToArray()); The output Copy.tiff file throws the same error when importing with PremierePro. Again, if I open it in Photoshop or Paint, save as Tiff, it will work just fine. I tried comparing 2 files, MediaInfo shows identical metadata, and the decoded header indicates Tiff properly. The only thing out of order is different file sizes. If I copy the files using File Explorer, the created copy has the same file size. From those two facts I presume there must be some differences between those files, and whatever it is it causes Premiere to crash. [Attachments.zip](https://github.com/SixLabors/ImageSharp/files/10030359/Attachments.zip)

[brianpopow]

Maybe try a 1x1 pixel image. Save a 1x1 black pixel image with ImageSharp and again with another program you know is working with PremierePro. Then compare those binary and see what the difference is.

Maybe it's as simple as the file extension is not as expected? Tiff instead of Tif?
A quick google search shows that this indeed can cause this issue.

Other then that, I am not sure what we can do about it. If libtiff does not complain, I am pretty sure the tiff is valid.

I really think the PremierePro supports needs to tell why this error is happening.

[MaciejSzulborski]

I created 2 1px files:
-1pxPaint.tif
-1pxImageSharp.tif

1pxImageSharp was created like so:

using Image<Rgba32> image = new(1, 1);
TiffEncoder tiffEncoder = new()
{
	BitsPerPixel = TiffBitsPerPixel.Bit24,
	PhotometricInterpretation = SixLabors.ImageSharp.Formats.Tiff.Constants.TiffPhotometricInterpretation.Rgb,
	Compression = SixLabors.ImageSharp.Formats.Tiff.Constants.TiffCompression.Lzw
};
image.SaveAsTiff(@"\\plpns01\pl-sdi\TEMP\m_szulborski\Test\DubcardGenerator\1pxImageSharp.tif", tiffEncoder);

Encoder was needed because Paint creates Tiff with LZW Compression by default, and I wanted files to be identical.

Comparing 2 files I can see:

• Different file size: ImageSharp 221KB, Paint 222KB
• Difference in header and the entire byte array (I read that header is first 8 bytes)

1pxPaint:
49492A000E0000008000205010000F00FE00040001000000000000000001040001000000010000000101040001000000010000000201030003000000C80000000301030001000000050000000601030001000000020000001101040001000000080000001501030001000000030000001601040001000000010000001701040001000000050000001A01050001000000CE0000001B01050001000000D60000001C01030001000000010000002801030001000000020000003D01030001000000020000000000000008000800080000770100E803000000770100E8030000
1pxImageSharp:
49492A000D00000080002050100E000001040001000000010000000101040001000000010000000201030003000000BB0000000301030001000000050000000601030001000000020000001101040001000000080000001501040001000000030000001601040001000000010000001701040001000000050000001A01050001000000C10000001B01050001000000C90000001C0103000100000001000000280103000100000002000000310102000B000000D10000000000000008000800080060000000010000006000000001000000496D61676553686172700000

1pxImages.zip

[brianpopow]

I created 2 1px files: -1pxPaint.tif -1pxImageSharp.tif

1pxImageSharp was created like so:

paint:
4949 byteorder
2A00 magick byte
0E00 FirstIfdOffset

imagesharp:
4949 byteorder
2A00 magick byte
0D00 FirstIfdOffset

The difference is that imagesharp ifd offset starts at offset 13 and paint starts at 14. After double checking the spec, this could be indeed a violation of the spec: "The directory may be at any location in the file after the header but must begin on a word boundary."

[brianpopow]

@MaciejSzulborski can you try opening the following tiff with premiere pro:

1pxImageSharp.zip

I have adjusted the ifd offset there to start at the word boundary.

[MaciejSzulborski]

Unfortunately Premiere Pro throws the same error.

[JimBobSquarePants]

If the adjusted tif has exactly the same bytes as the paint one then that sounds like a bug in premier pro.

[brianpopow]

Unfortunately Premiere Pro throws the same error.

That's really unfortunate, I really thought this should work now. The header looks the same as from paint now:

4949 byteorder
2A00 magick byte
0E00 FirstIfdOffset

[MaciejSzulborski]

I have decoded .tiff file you attached and it looks like header is identical now, but there are still differences in the full byte array.
1pxPaint:
49492A000E0000008000205010000F00FE00040001000000000000000001040001000000010000000101040001000000010000000201030003000000C80000000301030001000000050000000601030001000000020000001101040001000000080000001501030001000000030000001601040001000000010000001701040001000000050000001A01050001000000CE0000001B01050001000000D60000001C01030001000000010000002801030001000000020000003D01030001000000020000000000000008000800080000770100E803000000770100E8030000
1pxImageSharp from SixLabors:
49492A000E0000008000205010000F000001040001000000010000000101040001000000010000000201030003000000C80000000301030001000000050000000601030001000000020000001101040001000000080000001501040001000000030000001601040001000000010000001701040001000000050000001A01050001000000CE0000001B01050001000000D60000001C0103000100000001000000280103000100000002000000310102000B000000DE0000003D01030001000000020000000000000008000800080060000000010000006000000001000000496D61676553686172700000

And still file size is different: 222 KB vs 224KB (it was 221KB before). I am no expert in how the files are built, but if it is supposed to be the same 1 black pixel with the same setup, shouldn't the file size and byte order be identical?