erm yea.. how good is it suppose to be?
i can only get compression to do this much
from 367kb to 348kb.......
Awesoken at
I am always impressed when someone finds it easier to post a question on a forum than read the first few lines of the help text. The only reason I'm not locking this thread is because I had a typo in my description. It wasn't printing out the percent sign after the "5-10".
Anonymous at
To hi-jack this thread (and turn it into something more useful!)
You updated PNGOUT again on 6th December. Could you please let me know what has changed? Would it be possible to maintain a simple text changelog?
Cheers,
Andrew
PS- Sorry if I sound pushy, but I'm currently converting close to 8,000 images over for an open-source project, so I like to keep on top of any improvements/ bugs/ etc. Ta.
Awesoken at
I knew this would happen. Here's what changed:
In the C source code, this:
...by 5-10%...
got replaced with this:
...by 5-10%%...
Would it be possible to maintain a simple text changelog?
Yes, it would be possible. At this time, I'm pondering whether the pain of maintaining a public changelog is greater than answering these questions every time I change a percent sign. As you can see, most changes are very minor.
Anonymous at
Ok, thanks for the info and your time. I understand it must be frustrating answering these kind of questions- but to look on the bright side, it does show what a large user base you have for your software.
Best wishes,
Andrew
PS- To assist in the 'pain' of changelog maintenance, here is a first line for you :wink:
2005.12.06 - Fixed per cent sign in help so that it reads "5-10%".
2005.11.23 - Fixed exit codes: 0 for good, and 1 (instead of -1) for error.
counting_pine at
Thanks for all the work you put into PNGOUT. It's a great program, and it's nice that you continue to maintain and update it, even with just small changes : )
Anonymous at
Hi Ken.
Happy New Year, and thanks for the Christmas PNGOUT update (2005.12.26). Would you be able to let us know what changed?
Cheers.
Awesoken at
I finally added support for progressive JPG to my image loading library (KPLIB.C). That's the only change to PNGOUT. The good news is this also means Voxlap, Evaldraw, JFBuild/JfDuke/JFSW, etc.. will be receiving support on their next release.
Anonymous at
Thanks
Cheers for the update!
2005.12.26 - Added support for loading progressive JPEG images.
2005.12.06 - Fixed per cent sign in help so that it reads "5-10%".
2005.11.23 - Fixed exit codes: 0 for good, and 1 (instead of -1) for error.
Anonymous at
my bad
forgive me my noobness, but as far as i could judge from different sources, PNG was supposed to be a better compression algorithm than *.jpg
I compressed a file, it grew about 600% in size...
Is PNG only recommended for compressing lossless files?
Why bother supporting the recompression of JPEG's and GIF's then?
Saucjedi at
Re: my bad
Anonymous said
forgive me my noobness, but as far as i could judge from different sources, PNG was supposed to be a better compression algorithm than *.jpg
It is in the lossless arena... I believe JPEG never implemented their lossless compression algorithms... do not take my word for it, though
Anonymous said
Is PNG only recommended for compressing lossless files?
Compression in PNG is always lossless
Anonymous said
Why bother supporting the recompression of JPEG's and GIF's then?
Because your target application/system does not support JPEG/GIF directly and you don't have the original uncompressed image that the JPG depicts, for example
counting_pine at
Anonymous said
Why bother supporting the recompression of JPEG's and GIF's then?
I hope this isn't some sort of anti-feature request : )
Firstly, GIFs are very different from JPEGs. PNG can usually beat GIF on compression. So GIF -> PNG recompression is a good idea.
Probably the most likely reason for converting JPEG to PNG is simply because PNG might be the preferred format to use, e.g. working with a program that can't import JPEGs.
Also, very occasionally, PNG can sometimes beat JPEG on compression. So in those situations, it is a good feature.
If that doesn't convince you, then how about the old "might as well" argument? Ken has code for reading JPEG files, so why not add it to PNGOUT?
FreeDOSfan at
PNG performance :D
"erm yea.. how good is it suppose to be?
i can only get compression to do this much
from 367kb to 348kb......."
It depends of input file and how good or poor the original compressor was.
The size can reduce by factor up to cca 1.5 (rarely), or it can fail
competely, either on a file already optimized by PNGOUT, or, rarely,
on "ordinary" PNG files.
"I compressed a file, it grew about 600% in size...
Is PNG only recommended for compressing lossless files?
Why bother supporting the recompression of JPEG's and GIF's then?"
GIF: lostless
PNG: lostless
JPG: lossy
GIF-> PNG good save (1.2 ... 1.5)
PNG -> PNG less save (1.1 ... 1.4)
JPG -> PNG no save, file size will grow !!!