null54

Not directly, PSFilterPdn is feeding it bad data when the image uses those stride tricks. But I have no idea where the underlying bug is located, everything I have checked looks correct. The data copy loops I am using would be similar to: using (IBitmapLock<ColorBgra32> bitmapLock = scaledSurface!.Lock(bounds, BitmapLockMode.Read)) { for (int y = 0; y < bounds.Height; y++) { uint* src = (uint*)((byte*)bitmapLock.Buffer + (nuint)((nint)y * bitmapLock.BufferStride)); byte* dst = (byte*)dstScan0 + ((y + padding.top) * destStride) + padding.left; ImageRow.Load(src, bitmapLock.BufferStride, dst, destStride, bounds.Width, channelIndex, numberOfPlanes); } } The source BufferStride is equal to whatever PDN sets it to, and the destination buffer stride is equal to width x numberOfPlanes.

This is a known issue with the AVIF plugin. The fix is to not use the Very Slow preset. The Very Slow preset instructs AOM to encode the image using the slowest compression, without chopping it up into a sequence of smaller frames. This usually provides the smallest file size, but it is not a great user experience due to the limited opportunities for progress reporting and cancellation. Paint.NET will stop responding until AOM finishes its encoding. The plugin only reports progress and allows cancellation before and after AOM compresses a frame.

It looks like Paint.NET is padding the stride of the WIC bitmaps depending on the dimensions. This does not occur when using WIC directly. I still don't know how this is causing the code to produce a corrupt image. the loops should handle different stride values when copying the data.

Version 2.0.3 had a lot of changes to the image storage and rendering code, I converted it all from GDI+ to WIC/Direct2D. As a workaround you can delete the 64-bit version of that filter, the 32-bit version is working correctly. I am not sure what is going on with the 64-bit version, it looks like a possible bug in the pixel copying or resizing code.

Release version 2.0.8, which fixes a crash when running 32-bit filters.

It is, and I know what is causing it. For some reason ILLink is removing System.IDisposable from the trimmed runtime, despite the fact that I set the option in the project file that should make it ignore the main executable and any assemblies that are not marked as compatible with trimming. The main executable uses IDisposable in a few places, so I have no idea why ILLink thinks it can be removed. It was working when I built 2.0.6, but it obviously no longer does.

@user.by That issue has been fixed, I had forgotten to include that DLL in the zip file.

Release version 2.0.7. Changes: Improved error reporting when scanning for filters. Added the plugin version to the dialog title bar.

I have no idea what the issue could be. It works for me when I place filters in the Effects folder. What version of PSFilterPdn are you using? I probably should put the version in the title bar of the Effect dialog.

The old gmic folder should be deleted, not replaced. Replacing the folder could cause DLL conflicts. Also, you will need to update to Paint.NET 5.0.12 to use the plugin.

The x64 download has been fixed, it was missing a DLL in the gmic folder.

Release version 3.3.3, which updates G'MIC to version 3.3.3.

I don't believe that AVIF has any practical limit on the image size. The AV1 format limit on the size of an individual encoded frame can be bypassed using multiple frames in an image grid, which my plugin already does by default to improve the AV1 encoding speed. I just tested saving a 70,000 x 600 image using the default blank canvas, and it worked. A blank canvas is not a very realistic test, but it makes the file encode very quickly due to the fact that it only has to encode one AV1 frame which all of the images in the image grid use. The final file size for that test image on the Medium preset is ~3.2 KB.

Fixed in version 1.1.29. Release version 1.1.29, which fixes loading images with a restricted ICC color profile.

No support is provided for older versions of Paint.NET (other that help installing the latest version). Also, it is not a good idea to be using a Windows 7 computer that is connected to the Internet. Microsoft stopped providing security updates for that operating system on January 14, 2020. There is currently no way to prevent Paint.NET from writing EXIF or other metadata to the image, but you can use another tool to remove it (e.g. exiftool).

That file (odm_orthophoto.tif) uses BigTIFF, a TIFF variant that uses 64-bit offsets in place of the 32-bit offsets in the regular TIFF format. The TIFF format can be identified in a hex editor by the file header signature, the first 4 bytes would be: Regular TIFF Motorola/Big Endian - 0x4D 0x4D 0x00 0x2A Regular TIFF Intel/Little Endian - 0x49 0x49 0x2A 0x00 Big TIFF Motorola/Big Endian - 0x4D 0x4D 0x00 0x2B Big TIFF Intel/Little Endian - 0x49 0x49 0x2B 0x00 I have no idea why that file was written as BigTIFF, its size is well within the 4 GB limit of the regular TIFF format. As for why WIC does not support BigTIFF, that would be a question for Microsoft.

Paint.NET uses the TIFF read/write functionality that is built-in to Windows, Windows Imaging Component (WIC). There could be something about those files that WIC does not like. The other apps you mentioned have their own code for handling TIFF files that is independent of WIC, e.g. GIMP uses libtiff.

Done. Release version 1.0.11, which updates RIOT to version v2023.12.0.

Yes, that is why Paint.NET defaults to saving single-layer images as PNG.

Those images were hosted on Photobucket. It looks like the hosting server is down or that they changed the link.

You need to change the file extension to .agif for the plugin to read it. If the file has a .gif extension it will be loaded using Paint.NET's built-in GIF format, which only reads the first frame of an animated image.

Release version 1.1.28, which updates AOM to version 3.8.0.

It is not a good idea to be using a Windows 8.1 computer that is connected to the Internet. Microsoft stopped providing security updates for that operating system on January 10, 2023. The forum rules prohibit providing links to older versions of Paint.NET.

I'm sorry, but the forum rules prohibit providing links to older version of Paint.NET.

@ishanihas not logged logged in for 2 years. Fortunately, the Internet Archive saved a copy of the GenesisVFX preset collections as part of the following article: https://web.archive.org/web/20220716090858/https://www.ishani.org/projects/GenesisVFX/