Quote:
Originally Posted by Crimzan
Would you mind explaining in a bit more detail how to use the XTool Verbose mode? I created a standard zip and also a 7zip file (LZMA2) and created a batch file based on what you showed in the link you provided (also changed the algorithm from mzlib to lzma2 (hoping that it works that way), but no matter what file I yeet onto xtool, all I get is this:
Code:
[0] Performing scan from block 0000000000000000 to 0000000000502C9D (5254302)
Streams: 0/0
Time: 00:00:00 (00:00:00)
Memory: 128 MB (128 MB)
I didn't expect it to not find any lzma2 streams in an lzma2 file, or other files I tried out with the adjusted algorithm parameter. I expected, similar to the "Drop and Scan 4 ZLib" Application from Razor to have different values here, that recognize how many parts of a file actually correspond to the compression algorithm. Am I misunderstanding the function and expecting a result that this tool is not supposed to give? If it isn't too much to ask, could you maybe show me a working result on a file? |
You cannot use -mlzma2 directly. As far as I know, zip/7z files contain always reflate streams (correct me if I'm wrong).
So for zip/7z files you have to use -mreflate if they are compressed.
Example for what it should look like:
Code:
...
...
[0] Processed reflate stream at 00000000022750C2 (304787 >> 349571 >> 304787) using l9:w15 successfully
[0] Processed reflate stream at 00000000022BF7D2 (33359 >> 43715 >> 33359) using l9:w15 successfully
[0] Processed reflate stream at 00000000022C7B42 (9895 >> 20251 >> 9895) using l9:w15 successfully
[0] Processed reflate stream at 00000000022CA262 (219985 >> 349563 >> 219985) using l9:w15 successfully
[0] Processed reflate stream at 00000000022FFEC2 (155628 >> 278096 >> 155628) using l9:w15 successfully
[0] Processed reflate stream at 0000000002325F32 (141976 >> 174791 >> 141976) using l9:w15 successfully
[0] Processed reflate stream at 0000000002348A42 (1270475 >> 1398167 >> 1270475) using l9:w15 successfully
[0] Processed reflate stream at 000000000247ED92 (491179 >> 699087 >> 491179) using l9:w15 successfully
[0] Processed reflate stream at 00000000024F6CC2 (2433413 >> 2796295 >> 2433413) using l9:w15 successfully
[0] Processed reflate stream at 0000000002748EC2 (965084 >> 1398165 >> 965084) using l9:w15 successfully
Streams: 167/167
Time: 00:00:04 (00:00:03)
Memory: 175 MB (175 MB)
Here are some possible options:
Code:
zlib / reflate / preflate
kraken / mermaid / selkie / leviathan (part of oodle compression family, requires "oo2core_#_win64.dll" library near xtool.exe)
flac (wave audio)
packjpg / brunsli / jojpeg (for JPG images, requires corresponding libraries near xtool.exe)
png (PNG image precompression, requires -d1 option and preflate option -> -mpng:d1:preflate)
lz4 / lz4f / lz4hc (requires liblz4.dll library near xtool.exe)
zstd (requires libzstd.dll library near xtool.exe)
Quote:
Originally Posted by Crimzan
So, let's keep things simple for now and let's say I found a file is actually compressed with LZMA2 / 7zip -- I would use xtool to decompress it (precomp?), receive a larger file, and then use a more efficient combination to get a better compression ratio, right?
|
Yes.
Quote:
Originally Posted by Crimzan
What does the 4x4: stand for? are these parameters in xtool or where does it come from?  |
4x4 is part of freearc. It utilizes all cores (max 16) for compression. This gives a good speed boost, but cpu usage is 100% most of the time.