#16
|
||||
|
||||
Quote:
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> MTX.ini Code:
[MTX] MainPath=.\..\..\..\ Config=%MainPath%\DiskSpan_x64.ini TmpPath=%MainPath%\..\TEMP Will the "-c:64m -t:100p" settings be applied to MTX.exe, or will they be ignored? Thanks! |
Sponsored Links |
#17
|
||||
|
||||
Quote:
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> Last edited by BLACKFIRE69; 12-10-2020 at 00:36. |
The Following User Says Thank You to BLACKFIRE69 For This Useful Post: | ||
Cesar82 (12-10-2020) |
#18
|
|||
|
|||
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 |
#19
|
||||
|
||||
Quote:
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 |
The Following User Says Thank You to BLACKFIRE69 For This Useful Post: | ||
Snapppr6 (17-10-2020) |
#20
|
||||
|
||||
MTX v5.1.0.0 New Update Test.
MTX v5.1.0.0 New Update Test
it's time for a new update. you guys, can you do some testing for me? TESTS:
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. _ Last edited by BLACKFIRE69; 27-10-2020 at 05:36. |
The Following User Says Thank You to BLACKFIRE69 For This Useful Post: | ||
dixen (26-10-2020) |
#21
|
||||
|
||||
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
__________________
Haters gonna hate
|
The Following User Says Thank You to KaktoR For This Useful Post: | ||
BLACKFIRE69 (26-10-2020) |
#22
|
||||
|
||||
Thanks to BLACKFIRE69 for update but...tests..Not particularly impressive
patchpack002\dlc.rpf MTX+OO2RECK (pack) Quote:
Quote:
Quote:
Quote:
Last edited by dixen; 26-10-2020 at 11:13. |
The Following User Says Thank You to dixen For This Useful Post: | ||
BLACKFIRE69 (26-10-2020) |
#23
|
||||
|
||||
Guys, try with more chunk sizes.
-c:128mb -c:256mb -c:512mb |
#24
|
|||
|
|||
Same file, chunk size 256
Unpack Quote:
Quote:
|
#25
|
||||
|
||||
It seems to be MTX is 0.58 mb/s faster than the original version right ? ( for chunk = 256mb ) |
#26
|
|||
|
|||
Yeah it looks like the idea failed
|
#27
|
||||
|
||||
MTX + Lolz may work well in high chunk sizes.
|
#28
|
||||
|
||||
Isn't the oodle precompressor multi threaded already?
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. 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 197.PNG 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 Last edited by Razor12911; 27-10-2020 at 04:06. |
#29
|
||||
|
||||
no more developments. it doesn't seem to be useful.
@mods, plz delete this thread. |
#30
|
||||
|
||||
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.
Last edited by Razor12911; 27-10-2020 at 06:04. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
XLolz - Lolz Accelerator | BLACKFIRE69 | Conversion Tutorials | 17 | 28-09-2022 15:24 |
Universal Accelerator - cls-mtx.dll | BLACKFIRE69 | Conversion Tutorials | 60 | 12-07-2022 15:44 |
New Universal Extractor By DLG | felice2011 | Conversion Tutorials | 5 | 30-12-2018 05:16 |
Universal CLS Generator | 78372 | Conversion Tutorials | 57 | 30-01-2018 05:04 |
CheatEngine Universal Game Cracker All Games 2014 | sillywalks | PC Games | 1 | 01-12-2014 13:24 |