file - Postscript to png conversion loss
2013-08
Chetan Bhargava
When converting Postscript files to PNG, is there any loss of fidelity in the converted files? The postscript files are scanned at 1200DPI.
If there is such loss, how can it be kept minimum?
I'm using gimp to convert these files.
arober11
Postscript is a programming language, bassed on Forth, so theoretically postscript files(programs) offer infinite fidelity, well as good as the rendering engine / interpreter that's passing the file can offer. There are numerous fractal / mandelbrot Postscript demos, that can demonstrate this.
As to whether there is noticeable difference between a 1200dpi bitmap generated from a postscript file, via one Postscript interpreter, that's possibly scaled later by another engine to fit some physical medium, and a natively rendered Postscript file on that device, it all depends on what the intended purpose / media is, and especially on how you will be manipulating the image (rotating / scaling).
Travis
At work, on certain projects I have to manage a lot of images. Most of the time PNG files work the best for what I'm doing.
With such a huge amount of images, I've tried using PNG compression with PNG Gauntlet but sometimes the file doesn't really change and sometimes PNG Gauntlet reports it would've made the filesize bigger!
Am I just maxing out the compression or is there something more I can do?
Joseph
PNG compression is a lossless compression. However, a caveat to this is that there will be times when compressing an image will not always yield the results you want (% compression ratio won't be that great). In contrast to lossful compression (like JPG compression), where you will almost always get a filesize reduction (% compression ratio might be higher), but you actually lose image quality.
raspi
Have you tried PNG Crush?
Brad Gilbert
PNG compression works better for images that have large areas of flat color, like cartoons that are colored with simple color fill, as apposed to a painting which has many colors which look similar, but really aren't.
liori
You should check if you PNG files do really need all the features PNG offers. If it doesn't have man colors, maybe you should switch from 24-bit color to a colortable? If you don't use alpha channel, turn it off. This can make them much smaller.
Cristián Romo
I recommend PNGOUT - it works very well. I have never had it make a file larger, and have only had it keep the same file size on rare occasions.
via Coding Horror
Shadok
Your best bet would be to use Optipng, there are links to GUIs projects for it on their homepage if you need one. The way it works is very efficient size-wise, by trying every combination of compression parameters you have a guarantee to find the better one.
The drawback is that it will consume more cpu than other techniques because it compresses the same image multiple times to find the smallest one, without any assumption.
The cool factor here is that you can adjust the optimization level to spare CPU time at your convenience (-o level), in that case assumptions will be made but generally you will not gain anything at testing every possibility.
porneL
You can try all of the PNG compressors at once, e.g. ImageOptim for OS X does that, and that's best you can get with lossless PNG alone.
However, there are lossy operations you can do to make PNG smaller (easier to compress).
If you have 24 bit PNG with alpha channel, convert it to paletted PNG with 8-bit alpha channel. pngquant does that (sadly both Photoshop and GIMP pretend such combination cannot exist).
Lynda
I know this is an old post but I came across it looking for a PNG Optimizer of some sort.
I found this: PngOptimizer it has a nice interface and I ran 61 files at once, it took about 30 seconds. The 61 files were originally 360kb and it compressed them to 300kb.
Some files it changed the files only 2 or 3 percent of the original others it reduced by 89%!
One Note: I never saw it make a larger file. It would say File 100% og original but never larger =>
It does vary though. Try it and test it for yourself =>