FileForums - MTX - The Universal Accelerator

FileForums (https://fileforums.com/index.php)

- Conversion Tutorials (https://fileforums.com/forumdisplay.php?f=55)

- - MTX - The Universal Accelerator (https://fileforums.com/showthread.php?t=103853)

Quote:

Originally Posted by BLACKFIRE69 (Post 488277)

first configured file (MTX.ini) then checks the default keys (--mainpath , ...).

means,

If MTX.ini is not configured, it uses the default keys.

Just out of curiosity, if I use it like this:

DiskSpan_x64.ini:

Code:

[External compressor:mpz,MPZ,mpzapi,MPZAPI]

header    = 0

packcmd   = "MEDIA\MPZ\mpzapi.exe" c <stdin> <stdout>

unpackcmd = "MEDIA\MPZ\mpzapi.exe" d <stdin> <stdout>



[External compressor:mpz_mtx,MPZ_MTX,mpzapi_mtx,MPZAPI_MTX]

header    = 0

default   = -c:64m -t:100p --mainpath=".\..\..\..\" --config="%MainPath%\DiskSpan_x64.ini" --tmppath="%MainPath%\..\TEMP"

packcmd   = "OTHERS\MTX\Win64\MTX.exe" a:mpz {options} - - <stdin> <stdout>

unpackcmd = "OTHERS\MTX\Win64\MTX.exe" x:mpz {options} - - <stdin> <stdout>

And add MTX.ini file next to MTX.exe with the config:

MTX.ini

Code:

[MTX]

MainPath=.\..\..\..\

Config=%MainPath%\DiskSpan_x64.ini

TmpPath=%MainPath%\..\TEMP

Question is as follows:
Will the "-c:64m -t:100p" settings be applied to MTX.exe, or will they be ignored?

Thanks!

Quote:

Originally Posted by Cesar82 (Post 488278)

Just out of curiosity, if I use it like this:

DiskSpan_x64.ini:

Code:

[External compressor:mpz,MPZ,mpzapi,MPZAPI]

header    = 0

packcmd   = "MEDIA\MPZ\mpzapi.exe" c <stdin> <stdout>

unpackcmd = "MEDIA\MPZ\mpzapi.exe" d <stdin> <stdout>



[External compressor:mpz_mtx,MPZ_MTX,mpzapi_mtx,MPZAPI_MTX]

header    = 0

default   = -c:64m -t:100p --mainpath=".\..\..\..\" --config="%MainPath%\DiskSpan_x64.ini" --tmppath="%MainPath%\..\TEMP"

packcmd   = "OTHERS\MTX\Win64\MTX.exe" a:mpz {options} - - <stdin> <stdout>

unpackcmd = "OTHERS\MTX\Win64\MTX.exe" x:mpz {options} - - <stdin> <stdout>

And add MTX.ini file next to MTX.exe with the config:

MTX.ini

Code:

[MTX]

MainPath=.\..\..\..\

Config=%MainPath%\DiskSpan_x64.ini

TmpPath=%MainPath%\..\TEMP

Question is as follows:
Will the "-c:64m -t:100p" settings be applied to MTX.exe, or will they be ignored?

Thanks!

those settings are not ignored ( -c:64m -t:100p ).

ok cesar,

we use MTX.ini to define only "MainPath", "ConfigFile" and "TempPath".

let us consider,
if MTX.exe doesn't find any MTX.ini near MTX.exe, it will look for MTX.exe options ( --mainpath, --config and --tmppath). if those options are also not found, it uses its default values.

in your case, there is MTX.ini next to MTX.exe. therefore, the "--mainpath", "--config" and "--tmppath" options will be ignored.

but the only place to set values for "-t:" and "-c:" is the command line. so nothing can ignore those values.

finally, MTX.exe will ignore some options as the code below because you have used MTX.ini. (Marked in red).

Code:

[External compressor:mpz_mtx,MPZ_MTX,mpzapi_mtx,MPZAPI_MTX]

header    = 0

default   = -c:64m -t:100p --mainpath=".\..\..\..\" --config="%MainPath%\DiskSpan_x64.ini" --tmppath="%MainPath%\..\TEMP"

packcmd   = "OTHERS\MTX\Win64\MTX.exe" a:mpz {options} - - <stdin> <stdout>

unpackcmd = "OTHERS\MTX\Win64\MTX.exe" x:mpz {options} - - <stdin> <stdout>

Extra: (not related to the question)

during decompression, MTX.exe doesn't retrieve values for "ChunkSize" from users. therefore it is better to use as follows. :)

Code:

[External compressor:mpz_mtx,MPZ_MTX,mpzapi_mtx,MPZAPI_MTX]

header    = 0

default   = -t:100p

packcmd   = "OTHERS\MTX\Win64\MTX.exe" a:mpz -c:64m {options} - - <stdin> <stdout>

unpackcmd = "OTHERS\MTX\Win64\MTX.exe" x:mpz {options} - - <stdin> <stdout>

Help BlackFire69

first thing thanks to you for this tool and other cls
i need IS example to unpack compressed data by mtx and thanks

Quote:

Originally Posted by Snapppr6 (Post 488332)

first thing thanks to you for this tool and other cls
i need IS example to unpack compressed data by mtx and thanks

here is the basic inno example for MTX v5.0.0.0.

note that the two arc.ini files in the "Compressor" folder and the "IS_Example" folder are different. ;)

MTX v5.0.0.0 Inno Example.rar

MTX v5.1.0.0 New Update Test.

MTX v5.1.0.0 New Update Test

it's time for a new update. :D you guys, can you do some testing for me?

TESTS:
MTX + oo2reck

MTX + oo2recm

MTX + oo2recs

Arc.ini

Code:

; //================== FreeArc =================\\

[External compressor:oo2reck,oo2recm,oo2recs]

header    = 0

packcmd   = {compressor} e <stdin> <stdout>

unpackcmd = {compressor} d <stdin> <stdout>





; //==================== MTX ====================\\

[External compressor:MTX_oo2reck, oo2reckMTX, oo2reckX]

header = 0

default   = -t:100% --logs

packcmd   = MTX.exe a:oo2reck -c:64m {options} - - <stdin> <stdout>

unpackcmd = MTX.exe x:oo2reck {options} - - <stdin> <stdout>



[External compressor:MTX_oo2recm, oo2recmMTX, oo2recmX]

header = 0

default   = -t:100% --logs

packcmd   = MTX.exe a:oo2recm -c:64m {options} - - <stdin> <stdout>

unpackcmd = MTX.exe x:oo2recm {options} - - <stdin> <stdout>



[External compressor:MTX_oo2recs, oo2recsMTX, oo2recsX]

header = 0

default   = -t:100% --logs

packcmd   = MTX.exe a:oo2recs -c:64m {options} - - <stdin> <stdout>

unpackcmd = MTX.exe x:oo2recs {options} - - <stdin> <stdout>

i'll attach the MTX v5.1.0.0 test files.

thanks @dixen for the idea.

_

Code:

MTX

Compressed 1 file, 119,898,862 => 168,186,700 bytes. Ratio 140.27%

Compression time: cpu 0.13 sec/real 8.59 sec = 1%. Speed 13.96 mB/s

All OK



Extracted 1 file, 168,186,700 => 119,898,862 bytes. Ratio 140.27%

Extraction time: cpu 0.19 sec/real 3.90 sec = 5%. Speed 30.74 mB/s

All OK





No MTX

Compressed 1 file, 119,898,862 => 168,186,552 bytes. Ratio 140.27%

Compression time: cpu 0.14 sec/real 10.16 sec = 1%. Speed 11.80 mB/s

All OK



Extracted 1 file, 168,186,552 => 119,898,862 bytes. Ratio 140.27%

Extraction time: cpu 0.17 sec/real 3.84 sec = 4%. Speed 31.26 mB/s

All OK

Thanks to BLACKFIRE69 for update but...tests..Not particularly impressive

patchpack002\dlc.rpf

MTX+OO2RECK (pack)

Quote:

Compressed 1 file, 1,060,477,032 => 1,820,126,829 bytes. Ratio 171.63%
Compression time: cpu 1.28 sec/real 186.69 sec = 1%. Speed 5.68 mB/s
All OK

MTX+OO2RECK (Unpack)

Quote:

Extracted 1 file, 1,820,126,829 => 1,060,477,032 bytes. Ratio 171.63%
Extraction time: cpu 2.11 sec/real 132.35 sec = 2%. Speed 8.01 mB/s
All OK

Razor's oo2reck (Pack)

Quote:

Compressed 1 file, 1,060,477,032 => 1,820,656,947 bytes. Ratio 171.68%
Compression time: cpu 1.19 sec/real 216.05 sec = 1%. Speed 4.91 mB/s
All OK

Razor's oo2reck (unpack)

Quote:

Extracted 1 file, 1,820,656,947 => 1,060,477,032 bytes. Ratio 171.68%
Extraction time: cpu 1.77 sec/real 125.85 sec = 1%. Speed 8.43 mB/s
All OK

I'll test this on DOOM Eternal & Horizon Zero Dawn..

Guys, try with more chunk sizes.

-c:128mb
-c:256mb
-c:512mb

Same file, chunk size 256

Unpack

Quote:

Extracted 1 file, 1,820,527,500 => 1,060,477,032 bytes. Ratio 171.67%
Extraction time: cpu 2.06 sec/real 117.64 sec = 2%. Speed 9.01 mB/s
All OK

chunk size 512

Quote:

Extracted 1 file, 1,820,527,500 => 1,060,477,032 bytes. Ratio 171.67%
Extraction time: cpu 2.09 sec/real 123.59 sec = 2%. Speed 8.58 mB/s
All OK

Quote:

Originally Posted by dixen (Post 488630)

Same file, chunk size 256

Unpack

chunk size 512

It seems to be MTX is 0.58 mb/s faster than the original version right ? ( for chunk = 256mb )

Quote:

Originally Posted by BLACKFIRE69 (Post 488631)

It seems to be MTX is 0.58 mb/s faster than the original version right ? ( for chunk = 256mb )

Yeah it looks like the idea failed

MTX + Lolz may work well in high chunk sizes.

Isn't the oodle precompressor multi threaded already? :confused:

I made the tool in such a way that there no streams being cut off when chunking takes place because the program knows what it is doing and how it should make cuts in the chunks, if for example there is a stream that can be cut off at a certain position, the program self adjusts the position and your chunking method makes no such considerations and gets in the way of how the program should work in the first place which makes it prone to crashes or a drop in ratio. :o

Multi threading a multi threaded program does not make it faster especially if the main program uses all of the cpu, furthermore your MTX does not prepare chunks in advance which could be the reason it doesn't work very well.

Compare the speeds of MTX vs Freearc's 4x4

I'll also leave this here
Attachment 28232

I can't believe this community has been reduced to this, I don't know if I should find this funny or be sad that there are no new inventions will be made. :(

I would totally understand if the community gets excited every time EA Sports releases FIFA every year :D

no more developments. it doesn't seem to be useful.

@mods, plz delete this thread.

I wonder what makes you cease the development of your project, I just pointed out that using MTX on already multi threaded programs may have such an issue of being slower than when run natively. I wouldn't have said anything if you had figured out a smarter way of making the precompressor making sure it stays at 100% because there are times when it doesn't fully utilize the cpu furthermore there is also overutilization because the precompressor would be using all of the cpu while MTX is also making several instances of the program and now you have the problem of system being unresponsive. Your project has its uses just not handling multi threaded programs, you'd need to come up with a better solution for this.