Jump to content

anybody

Newbies
  • Posts

    1
  • Joined

  • Last visited

About anybody

  • Birthday 01/01/1970

anybody's Achievements

Newbie

Newbie (1/14)

  • First Post
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. Is there any chance that while you're at it, improvements can be made to the resulting PNG filesize (already discussed for example here) ? For example, loading a 1.9MB JPEG File Photo, 2272x1704, and saving it again as PNG produces the following filesizes: Paint .NET 3.08 : 9,47MB Paint Shop Pro 11: 6,29MB I don't have Photoshop installed, but from tests I have done earlier i'd say that Photopshop's resulting filesize is slightly below Paint Shop Pro's. But even when trying to use pngcrush to reduce the filesize, the Paint .NET png file remains larger! pngcrush(Paint .NET PNG File): 9,47MB => 6,93MB pngcrush(Paint Shop Pro PNG File): 6,29MB => 5,96MB Or when using pngout, a program which the paint.NET development team seems to be familiar with: pngout(Paint .NET PNG File): 9,47MB => 6,79MB pngout(Paint Shop Pro PNG File): 6,29MB => 6,08MB Judging from pngout's output, the Paint .NET PNG files seem to contain alpha transparency even though it should not. This is probably responsible for quite a bit of the wasted space. Can this be switched off? I looked through the .NET documentation but wasn't really successful in finding something. Those .NET image encoder options aren't documented too well IMHO... I don't really expect Paint .NET's PNG output files to be as small as pngout's. But at the moment they are 50% bigger than the competition (PSP11) and 59% bigger than what's theoretically possible (PSP11+pngcrush)... Is there any hope that this gap in filesize can be closed/reduced in future versions? Or is this a limitation of .NET ?
×
×
  • Create New...