CR2: System.NotSupportedException: Missing SOI marker offset for tiff with old jpeg compression

Start at TiffDecoderOptionsParser.ParseCompression, where the reported Missing SOI marker offset error is raised, and inspect the linked JpegSnoopReports/Lake.jpg.txt reference alongside the supplied Berries.CR2 asset. Reproduce the Image.LoadAsync call and determine whether the TIFF decoder can support this CR2 compression; done means the asset loads successfully with suitable regression coverage.

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

3.1.2

Other ImageSharp packages and versions

Environment (Operating system, version and so on)

Windows 11 amd64

.NET Framework version

.NET 8.0

Description

In a project, I have test assets with a CR2 image

Berries.CR2.zip

which windows file explorer provides the preview for:

However, loading this image with ImageSharp fails:

      System.NotSupportedException: Missing SOI marker offset for tiff with old jpeg compression
         at SixLabors.ImageSharp.Formats.Tiff.TiffThrowHelper.ThrowNotSupported(String message)
         at SixLabors.ImageSharp.Formats.Tiff.TiffDecoderOptionsParser.ParseCompression(TiffDecoderCore options, Nullable`1 compression, ExifProfile exifProfile)
         at SixLabors.ImageSharp.Formats.Tiff.TiffDecoderOptionsParser.VerifyAndParse(TiffDecoderCore options, ExifProfile exifProfile, TiffFrameMetadata frameMetadata)
         at SixLabors.ImageSharp.Formats.Tiff.TiffDecoderCore.DecodeFrame[TPixel](ExifProfile tags, CancellationToken cancellationToken)
         at SixLabors.ImageSharp.Formats.Tiff.TiffDecoderCore.Decode[TPixel](BufferedReadStream stream, CancellationToken cancellationToken)
         at SixLabors.ImageSharp.Formats.ImageDecoderUtilities.Decode[TPixel](IImageDecoderInternals decoder, Configuration configuration, Stream stream, Func`3 largeImageExceptionFactory, CancellationToken cancellationToken)
         at SixLabors.ImageSharp.Formats.ImageDecoderUtilities.Decode[TPixel](IImageDecoderInternals decoder, Configuration configuration, Stream stream, CancellationToken cancellationToken)
         at SixLabors.ImageSharp.Formats.Tiff.TiffDecoder.Decode[TPixel](DecoderOptions options, Stream stream, CancellationToken cancellationToken)
         at SixLabors.ImageSharp.Formats.Tiff.TiffDecoder.Decode(DecoderOptions options, Stream stream, CancellationToken cancellationToken)
         at SixLabors.ImageSharp.Formats.ImageDecoder.<>c__DisplayClass3_0.<DecodeAsync>b__0(Stream s, CancellationToken ct)
         at SixLabors.ImageSharp.Formats.ImageDecoder.<>c__DisplayClass12_0`1.<WithSeekableMemoryStreamAsync>g__PeformActionAndResetPosition|0(Stream s, Int64 position, CancellationToken ct)
      --- End of stack trace from previous location ---
         at SixLabors.ImageSharp.Formats.ImageDecoder.DecodeAsync(DecoderOptions options, Stream stream, CancellationToken cancellationToken)
         at SixLabors.ImageSharp.Image.WithSeekableStreamAsync[T](DecoderOptions options, Stream stream, Func`3 action, CancellationToken cancellationToken)

I couldn't find much information whether or not Canon's CR2 support is deliberately left out. https://github.com/SixLabors/ImageSharp/blob/1f22bceef8bb79793cbdcc26ace38a726ad9b8c8/tests/Images/Input/Jpg/baseline/JpegSnoopReports/Lake.jpg.txt#L162 suggests it might not be intentional. Opening this issue just in case. :)

Steps to Reproduce

using Image berries = await Image.LoadAsync(@"C:\temp\Berries.CR2");

Images

Berries.CR2.zip