Universal Accelerator - cls-mtx.dll

[BLACKFIRE69]

Originally Posted by Masquerade

@BLACKFIRE69

Following your instruction, it works:

cls-mtx.dll that i gave is original (v2.0.0.4), i didn't change anything.

so i think you need to double check your "Script.iss".


or you forgot to replace the old "cls-mtx.dll" with the new version (v2.0.0.4).

[BLACKFIRE69]

• cls-mtx.dll also supports "mcm".

arc.ini:

[External compressor:mcm]
header = 0
packcmd   = Resources\Mcm\{compressor} -x6 $$arcdatafile$$.tmp $$arcpackedfile$$.tmp
unpackcmd = Resources\Mcm\{compressor} d $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

Pack.bat

arc.exe a -ep1 -r -ed -s; -w.\temp -m=srep+mtx:c128m:t100p:mcm "..\Packed\Data0.bf"   "..\Pack0\*"

[BLACKFIRE69]

any suggestions for the next update of "cls-mtx"?

[Cesar82]

Originally Posted by BLACKFIRE69

any suggestions for the next update of "cls-mtx"?

If you are not going to increase the size of your library a lot, even if it does not serve to increase performance, it could include support for all the most used methods that would dispense with the use of other CLS.


Does your cls-mtx.dll library allow me to extract using executables in folders?
I want to include a mode with decompressors in folders in the CIU and I think that the other CLS don't work the way I need.

Creating folder structures as:

Compressors\PRECOMP\<precomp files>
Compressors\MPZAPI\<mpz files>
Compressors\RAZOR\<rz files>

In the Arc.ini file informing the folder containing the executables, like this:

[External compressor:precomp]
header    = 0
unpackcmd = "PRECOMP\{compressor}" -r -o$$arcdatafile$$.tmp $$arcpackedfile$$.tmp

[External compressor:mpz]
header    = 0
unpackcmd = "MPZAPI\{compressor}" d <stdin> <stdout>

[External compressor:rz]
header    = 0
unpackcmd = "RAZOR\{compressor}" e -y $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

Using in the Inno Setup script like this:

[Files]
Source: cls-mtx.dll; Flags: dontcopy;
Source: CLS.ini; Flags: dontcopy;
Source: Arc.ini; Flags: dontcopy;
Source: UnARC.dll; Flags: dontcopy;
Source: ISDone.dll; Flags: dontcopy;
Source: "Compressors\*"; Flags: dontcopy createallsubdirs recursesubdirs;

[code ]
function InitializeSetup(): Boolean;
begin
   ExtractTemporaryFile('cls-mtx.dll');
   ExtractTemporaryFile('CLS.ini');
   ExtractTemporaryFile('Arc.ini');
   ExtractTemporaryFile('UnARC.dll');
   ExtractTemporaryFile('ISDone.dll');

   ExtractTemporaryFiles('{tmp}\Compressors\*');
end;

[BLACKFIRE69]

Originally Posted by Cesar82

If you are not going to increase the size of your library a lot, even if it does not serve to increase performance, it could include support for all the most used methods that would dispense with the use of other CLS.


Does your cls-mtx.dll library allow me to extract using executables in folders?
I want to include a mode with decompressors in folders in the CIU and I think that the other CLS don't work the way I need.

Creating folder structures as:

Compressors\PRECOMP\<precomp files>
Compressors\MPZAPI\<mpz files>
Compressors\RAZOR\<rz files>

In the Arc.ini file informing the folder containing the executables, like this:

[External compressor:precomp]
header    = 0
unpackcmd = "PRECOMP\{compressor}" -r -o$$arcdatafile$$.tmp $$arcpackedfile$$.tmp

[External compressor:mpz]
header    = 0
unpackcmd = "MPZAPI\{compressor}" d <stdin> <stdout>

[External compressor:rz]
header    = 0
unpackcmd = "RAZOR\{compressor}" e -y $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

Using in the Inno Setup script like this:

[Files]
Source: cls-mtx.dll; Flags: dontcopy;
Source: CLS.ini; Flags: dontcopy;
Source: Arc.ini; Flags: dontcopy;
Source: UnARC.dll; Flags: dontcopy;
Source: ISDone.dll; Flags: dontcopy;
Source: "Compressors\*"; Flags: dontcopy createallsubdirs recursesubdirs;

[code ]
function InitializeSetup(): Boolean;
begin
   ExtractTemporaryFile('cls-mtx.dll');
   ExtractTemporaryFile('CLS.ini');
   ExtractTemporaryFile('Arc.ini');
   ExtractTemporaryFile('UnARC.dll');
   ExtractTemporaryFile('ISDone.dll');

   ExtractTemporaryFiles('{tmp}\Compressors\*');
end;

Cesar,
"cls-mtx.dll" supports this feature, since v2.0.0.3.

and unpackcmd should be like, ( without inverted commas (") ) (i'll fix this issue in the next update.)

[External compressor:bcm]
header    = 0 
unpackcmd = Res\Bcm\{compressor} -d $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

not

unpackcmd = "Res\Bcm\{compressor}" -d $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

here is the full example,

cls-mtx Example - Cesar.rar

[Cesar82]

Originally Posted by BLACKFIRE69

Cesar,
"cls-mtx.dll" supports this feature, since v2.0.0.3.

and unpackcmd should be like, ( without inverted commas (") ) (i'll fix this issue in the next update.)

not

unpackcmd = "Res\Bcm\{compressor}" -d $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

Without double quotes (") in the path names, if the path has spaces then I think it will detect the path to the space and the rest will be interpreted as another parameter causing errors.

[External compressor:bcm]
header    = 0 
unpackcmd = Res\Bcm Compressor\{compressor} -d $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

I will look forward to future updates.
Thank you.

[BLACKFIRE69]

Update

What's new:

• Bringing back "{compressor}".
  - Added support for "{compressor}" as before.

* cls-mtx supports two methods.

1: The simple way

[External compressor:precomp, mtxprecomp, mtx_precomp]
header    = 0
packcmd   = "Res\Precomp\precomp.exe" -cn -intense0 -o$$arcpackedfile$$.tmp $$arcdatafile$$.tmp
unpackcmd = "Res\Precomp\precomp.exe" -r -o$$arcdatafile$$.tmp $$arcpackedfile$$.tmp

2: Alternative method

[External compressor:precomp, mtxprecomp, mtx_precomp]
header    = 0
packcmd   = "Res\Precomp\{compressor}" -cn -intense0 -o$$arcpackedfile$$.tmp $$arcdatafile$$.tmp
unpackcmd = "Res\Precomp\{compressor}" -r -o$$arcdatafile$$.tmp $$arcpackedfile$$.tmp


and the exe name must be "precomp.exe" (similar to the first one in section names.)

[dixen]

Test

Left 4 dead 2 2.2.0.1

*.WAV (srep+mtxrz)

Tested 47,599 files, 4,218,328,066 => 9,937,777,119 bytes. Ratio 42.45%
Testing time: cpu 8.50 sec/real 82.11 sec = 10%. Speed 121.03 mB/s
All OK

[BLACKFIRE69]

cls-mtx October Update v2.0.0.7

What's new:

• Fixed a minor issue..
  - Fixed an issue that related to the working directory.

[kj911]

Any members tested the accelerator, using DLZ compressor in multi-core PC's?? (x86 or x64 and more CPU cores 2/4 to 8-16)

[Masquerade]

Originally Posted by kj911

Any members tested the accelerator, using DLZ compressor in multi-core PC's?? (x86 or x64 and more CPU cores 2/4 to 8-16)

Don't use DLZ. LOLZ is superior + has built in mulithreading.

[kj911]

I know lolz is better. For testing, you should do this to see if it can be better with MTX, the speed of (de)compression. Lolz, however, you can't pack on old X86 machines. (The unpacking only, we leave it now.) While with DLZ yes. DLZ is more faster compared (data dependent case) to FreeArc internal lzma codec. Up to 2x speed.* (Without cu2 or cu3 and cm40/43 switches.) The compression rate is often better (1-2% to few percentage), even for smooth data. (DDS files has in up to 5-15%) This cm10 or cm00 no effecting or minimally in decompression speed. For the most extreme settings, the unpacking is slow, true. Compared to OGGRE, even 2* is still more faster.

This range from DDS files compression:

1. LOLZ (its probably best, without MSC!)
2. DLZ (no MSC)
3. MSC + FA's lzma or use "FA's lzma" compression replacement use this lzma part from DLZ
4. FA's lzma or any lzma1/2 compressor

*Note: This DDS/DXT datafiles decompression speed comparable the FA's internal LZMA compression. (uses lzma's only switches.) Minimally slower. This "DATA"-typed compressed data (This DLZ printed type to out from CMD window) comparable or barely faster than FA's lzma algo. More tests req. from old PC from comparison. (Using and find ~0.5-1GB test data.)**

**More DDS samples, any games resources, text, sounds/videos, exe/dll binaries or any more.

Extra questions: Original DLZ Package has been release originally in UPX'ed files??

[darkwolves]

another one? lol