Webp images are being processed and come out 10x larger

[thomas-gregg-bz-agency]

piranha.core/core/Piranha.ImageSharp/ImageSharpProcessor.cs

Line 147 in a605dc5

public void AutoOrient(Stream source, Stream dest)

As per the title when we upload an image in webp format, the resulting image comes out roughly 10 times bigger. We have not seen this for other image formats

[tidyui]

Could you try asking the same question at the https://github.com/SixLabors/ImageSharp repo as we have no control over what happens inside the actual image processing. The current version of Piranha uses the latest released version of ImageSharp (2.1.3) but maybe there is a bug on their side related to this.

If you open an issue there, please reference this issue and make sure to include the code that seems to do the faulty processing, i.e:

using (var image = Image.Load(source, out IImageFormat format))
{
    image.Mutate(x => x.AutoOrient());
    image.Save(dest, format);
}

A workaround would be to remove the default registration in App.MediaTypes.Images and add it back with image processing disable with

App.MediaTypes.Images.Add(".webp", "image/webp", false);

[thomas-gregg-bz-agency]

Hi Håkan, I will make a post of this as instructed and I can confirm your workaround works perfectly. Thanks for your speedy help. Thanks Thomas. From: Håkan Edling ***@***.***> Sent: Friday, 27 January 2023 7:32 PM To: PiranhaCMS/piranha.core ***@***.***> Cc: Thomas Gregg ***@***.***>; Author ***@***.***> Subject: Re: [PiranhaCMS/piranha.core] Webp images are being processed and come out 10x larger (Issue #1975) Could you try asking the same question at the https://github.com/SixLabors/ImageSharp repo as we have no control over what happens inside the actual image processing. The current version of Piranha uses the latest released version of ImageSharp (2.1.3) but maybe there is a bug on their side related to this. If you open an issue there, please reference this issue and make sure to include the code that seems to do the faulty processing, i.e: using (var image = Image.Load(source, out IImageFormat format)) { image.Mutate(x => x.AutoOrient()); image.Save(dest, format); } A workaround would be to remove the default registration in App.MediaTypes.Images and add it back with image processing disable with App.MediaTypes.Images.Add(".webp", "image/webp", false); — Reply to this email directly, view it on GitHub<#1975 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AISZ3WU6OH6FP4UI5F7CCJLWUOIZPANCNFSM6AAAAAAUICSPT4>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[thomas-gregg-bz-agency]

@tidyui I have raised an issue over at ImageSharp and they have referenced a couple of other issues that seem to resolve the issue. Is there something that needs to be done like defining the encoding configuration?

[tidyui]

Hi there! As far as I know this bug has been fixed in ImageSharp 3.x, which has a different licensing model. We will need to look into if this model can be used from an open source library without impacting users of the library.

Best regards

[karl-sjogren]

Sounds like this was the bug with lossless encoding (since no quality was specified when saving). It was backported to 2.x in https://github.com/SixLabors/ImageSharp/releases/tag/v2.1.4 so just updating to that (or rather 2.1.6 which has some security fixes as well) should solve this.

[tidyui]

Fixed in commit be0c6da