Jump to content

null54

Moderator
  • Posts

    1,962
  • Joined

  • Last visited

  • Days Won

    89

Posts posted by null54

  1. 8 hours ago, Rick Brewster said:

    Is the "corrupt" bitmap being drawn by the 8BF plugin?

     

    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.

  2. 7 hours ago, Fagon Viendra said:

    CPU always reaches 80 to 90 percent. How to fix that?

     

    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.

     

    7 hours ago, Tactilis said:

    1. Are you able to Cancel the save or is paint.net completely unresponsive now?

     

    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.

    • Hugs 1
  3. 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.

    • Like 1
  4. 11 hours ago, user.by said:

    It's work v2.0.2 and earlier versions but dont work 2.0.3 and later versions. Like this

     

    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.

    • Like 1
  5. 1 hour ago, Rick Brewster said:

    That appears to be the same crash reported in the post above yours by @user.by

     

    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.

  6. 3 hours ago, Otto04 said:

    Yet.... i get no filter to choose:

     

    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.

  7. 1 minute ago, flash said:

    Then when I try G'MIC I get a long list of the issues. Should I have just copied 3.3.3 over 3.3.1 ?

     

    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.

    • Thanks 1
  8. 4 hours ago, Rick Brewster said:

    AVIF is a good modern format and it might support larger sizes

     

    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.

  9. 10 hours ago, ArmorSlave said:

    Greetings. I have tried opening an avif image in Paint.NET with the latest plugin (1.1.28), but I am getting an error message:

     Fixed in version 1.1.29.

     

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

    • Upvote 6
  10. 17 minutes ago, Reusability said:

    Please may I request from the community a method compatible for Paint.NET 4.3.8 (Windows 7 Version) to prevent the automatic applying of EIFF Metadata to saved files.

     

    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.

     

    17 minutes ago, Reusability said:

    Well, you're not quite being tracked - but it's easier for someone to narrow down where your photos have came from. This is due to whenever a .jpeg, .jpg, .jpe, .jfif, .exif, .tiff, .tif is saved using Paint.NET, by default it applies EIFF:software metadata 'paint.net {version}' to the file.

     

    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).

    • Upvote 2
  11. 5 hours ago, Rick Brewster said:

    So it is definitely not a TIFF, at least not by WIC's understanding of them, even if it has a file extension of .tif / .tiff.

     

    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.

    • Upvote 1
  12. 58 minutes ago, KadinNova said:

    I tried to load/reopen a gif I was working on, but it isn't loading the individual frames! It is simply acting as if the first frame is all there was, like a static picture. Can anyone help?

     

    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.

    • Like 2
  13. 2 hours ago, xoxococo said:

    I just want to say I'm pissed about having to go to a sketchy virus-laden third-party download source for a version of Paint.NET that works on Win8.1. This is a specialized rig, not a daily driver machine. Updating the OS is not an option for me in the context I need it because of certain software compatibilities.

     

    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.

    On 2/7/2007 at 11:40 AM, Rick Brewster said:

    8) Do not ask for older versions of Paint.NET. This is a corollary to #7, but I'm spelling it out separately anyway. We will not provide download links for them -- you are on your own to find them (hint: try a search engine). Along with this, don't ask about Windows 2000 (or XP, Vista, 7, 8, or 8.1) support. Seriously. You may think you have some new question or insight, and that's definitely possible, but this is not something that will be added back in to a future release of Paint.NET. End of discussion. If you want to complain about this, then don't talk about it here -- just write on your blog or talk to your therapist or something instead, please.

    • Upvote 1
  14. 4 hours ago, Elixir said:

    I want that version because I only have one x86 processor (32bits) and the latest version of the program (5.0) is no longer compatible with that architecture, please if someone would be so kind :) 

     

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

     

    On 2/7/2007 at 11:40 AM, Rick Brewster said:

    8) Do not ask for older versions of Paint.NET. This is a corollary to #7, but I'm spelling it out separately anyway. We will not provide download links for them -- you are on your own to find them (hint: try a search engine). Along with this, don't ask about Windows 2000 (or XP, Vista, 7, 8, or 8.1) support. Seriously. You may think you have some new question or insight, and that's definitely possible, but this is not something that will be added back in to a future release of Paint.NET. End of discussion. If you want to complain about this, then don't talk about it here -- just write on your blog or talk to your therapist or something instead, please.

    • Upvote 1
×
×
  • Create New...