-
PackJPG v2.x
[-s?] set global number of segments (max: 64)
[-c?] set global number of categories (max: 255)
[-s?,?] set number of segments for component
[-c?,?] set number of categories for component
[-split] split jpeg (to header & image data)
[-coll?] write collections (0=std,1=dhf,2=squ,3=unc)
[-fcol?] write filtered collections (see above)
[-zdst] write zero distribution lists
[-test] test algorithms, alert if error
[-info] write debug info to .nfo file
[-dist] write distribution data to file
[-pgm] convert and write to pgm files
But can't work yet...
-
you have to run -dev command with these to use it and its for advanced users & developers but the packjpg author has already tuned the program to maximum compression ratio and speed refer to
http://www.encode.su/forums/index.ph...um=1&topic=538
and here is some explanation from packjpg author
> is there a hidden options in packjpg..?
There are hidden developers options in packJPG. You can use the command line parameter "-dev" to make them accesible.
A short explanation:
> [-s?] set global number of segments (max: 64)
> [-c?] set global number of categories (max: 255)
> [-s?,?] set number of segments for component
> [-c?,?] set number of categories for component
These parameters are used to finetune compression. packJPG actually tries to find optimal settings on its own. There might be better compression in some cases if it is done by hand using the parameters above.
> [-split] split jpeg (to header & image data)
> [-coll?] write collections (0=std,1=dhf,2=squ,3=unc)
> [-fcol?] write filtered collections (see above)
> [-zdst] write zero distribution lists
> [-dist] write distribution data to file
All of these output some kind of debug info. This should be of little to no use for anyone else than me .
> [-test] test algorithms, alert if error
If this parameter is used, all input and output algorithms are tested. If this test passes, it is sure that the original JPEG file is identical to that restored from the PJG file.
Be careful with those parameters, though. While for packJPGs standard functions everything has been done to assure reliability, crashes might occur when using the developers functions in a wrong way. Also, files in the same directory might be overwritten without warning.
