We very much appreciate the PGF speed and the reasonable improvement of compression over JPEG.
What makes us to go with PGF rather than JEPG2000 is its speed for near-to-real-time applications. However, it seems PGF now adds more and more functions to compete with JPEG2000. I am afraid it may lose its initial focus on speed and compression. I am wondering whether PGF can offer a compiling option for us to ignore all other fancy functions such as progressiveness, regional retrieval, etc and focus on the optimization only for speed and compression.
Thanks!
John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
PGF was designed with progressiveness in mind right from the beginning, that is what the P stands for. For disabling ROI support there is the compiler option NPGFROI. Whichever version you use, images do not get encoded with ROI per default (ROI slightly decreases the compression ratio as we need to store some additional values).
We try hard not to sacrifice speed in exchange for other features. The latest release (available via SVN, packages will come soon) contains some minor speed improvements. Rest assured that speed is our main concern.
Regards
Raphael
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We very much appreciate the PGF speed and the reasonable improvement of compression over JPEG.
What makes us to go with PGF rather than JEPG2000 is its speed for near-to-real-time applications. However, it seems PGF now adds more and more functions to compete with JPEG2000. I am afraid it may lose its initial focus on speed and compression. I am wondering whether PGF can offer a compiling option for us to ignore all other fancy functions such as progressiveness, regional retrieval, etc and focus on the optimization only for speed and compression.
Thanks!
John
Hi John
PGF was designed with progressiveness in mind right from the beginning, that is what the P stands for. For disabling ROI support there is the compiler option NPGFROI. Whichever version you use, images do not get encoded with ROI per default (ROI slightly decreases the compression ratio as we need to store some additional values).
We try hard not to sacrifice speed in exchange for other features. The latest release (available via SVN, packages will come soon) contains some minor speed improvements. Rest assured that speed is our main concern.
Regards
Raphael