MTX - The Universal Accelerator
 

.

If anyone wants an example of "Inno setup" for MTX.exe, just let me know. ;)

MTX console version works perfectly. Also I was tested MCM works perfectly.

Masks
 

MTX.exe supports MASKS (Arc.Groups)

Can you explain about masks?

Masks allow you to use more than one method for different files in an archive

Different methods are specified with groups, which you can write yourself into the file "arc.groups" next to your arc.exe for compression.

Write your group as example:

Then we can use this in our compression method:

So here, all of the files defined in the $nameofgroup list will be compressed using rzx, where all other files will be compressed with srep+lolz.

Ok thanks for your information friend

MTX.exe Feature update
 

MTX.exe Feature update v.3.0.0.0

What's New:

• Some improvements.
  
  
• A new key (MainPath) has been added to MTX.ini.
  -- this allows you to set the root directory manually.
  -- MTX.exe can be executed within a sub-folder.
  
  
• There is no need to rename "mtx.ini" (as before).
  -- before: MTX64.exe ---> MTX64.ini --> [MTX64]
  -- now : MTX64.exe ---> MTX.ini --> [MTX]
  
  
• Added an example for XLolz.
• Added an example for MASKS.

Additional Options For both Compression and the Decompression:




_

Oh, thank you!
Can I have an example or small guide to adapt Inno/ASIS to this please? I'm probably doing something wrong with my frankenstein script lol

Edit/question: Is Xlolz working multithreading via MTX? It doesn't seem for me.
Edit2: It works with fixed thread count and not % like default (?)

You can't use "XLolz" via "MTX" (because both are accelerators). but it supports "MTX + Lolz".

ok, I'll give you some examples for both INNO Setup and Lolz with MTX.

Oh, yea, my bad: I mean the one inside the default "arc.ini" with MTX, for reference this one:
___

So.. Something works but not well

Using unpack.bat
Using my modified InnoSetup scripts with MTX gives "UnArc.dll -11 error: archive damaged" at ~80% but it actually extracts something

ok, just wait for the example.

New Update
 

• MTX.ini

• Percentage

• Supports Custom Input/Output

• New Options

• MTX.ini Configuration

Will show some errors in nanozip decompression with MTX.exe. therefore it is better to use cls-nzx.dll instead of MTX.exe. ;)


guys, I don't have enough space to upload it here. so use this link....


MTX v5.0.0.0 + Full Examples.rar




_

@BLACKFIRE69, very good the new key default options in example 5.
It will be very useful for the need to use MRX.ini.
Thanks for the great job.

If you have both configurations, which one will be used?
I mean if you have MTX.ini configured in one way and use the key default with --mainpath, etc. in another way, which one will be used?

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:
And add MTX.ini file next to MTX.exe with the config:

MTX.ini
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).



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. :)

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

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

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

thanks @dixen for the idea.

_

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

patchpack002\dlc.rpf

MTX+OO2RECK (pack)

MTX+OO2RECK (Unpack)

Razor's oo2reck (Pack)

Razor's oo2reck (unpack)

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

chunk size 512

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.

What people thinks development is? Remaking old projects with more bugs and making non sense project is not development. If you can make something new that's development, even if you remake and make something better than before that's development. Posting same thing over and over again by changing a bit of information is spamming, not development.

Sorry for bothering mr.BLACKFIRE, This may be a useful thread but we can't find the download section here. so please reupload it.
Thank you.

Hi,

I tried to use the settings in the snapshot, which should be using precomp048.exe

but when I test a packing, method called is

MTXprecomp048
-> calls method precomp048
-> calls precomp048.exe

however it is reporting error with precomp038.exe in the same directory.

It is MTX 5.0.0.0

https://i.ibb.co/qxF1j5m/2021-02-07-031238.png

Precomp v0.38 requires "packjpg_dll.dll" and "packjpg_dll1.dll" next to the precomp038.exe.

Thanks, that could explain part of it.
But why it would invoke precomp038.exe?
Is MTX parsing every external compressor defined in arc.ini as well as try to load them once to build some kind of lookup table into memory for later use?

I gave the default example and some random files a go:

precomp048+srep+lolz64 works
precomp048+srep+LolzMTX ERROR: general (de)compression error in LolzMTX

precomp048+srep+rz64 works
precomp048+srep+RazorMTX ERROR: general (de)compression error in RazorMTX

precomp048+srep+bcm32 ERROR: general (de)compression error in bcm32
precomp048+srep+BcmMTX works

It is a bit strange that, if not using MTX it works, using MTX will make it not working.
If not using MTX doesn't work, using MTX will make it work?
Is it because of the input output in the settings?

Another test for
PrecompMTX+srep+ any normal or MTX final compressor

none works.

The console / log doesn't say why at all.
It seems as soon as MTX invokes precomp, it exits/crashes.
The temp folder for precomp has been created, only the 0 folder has 512KB file, all others are 0

MTX New Update v5.0.0.1
 

What's new: MTX v5.0.0.1

• Some improvements.
• Minor bugs fixed.
• Exception handling.
• MTX.ini is no longer supported by default.
• {compressor} keyword is no longer supported.
• A few more changes:
  1. %exePath% ==> $exePath$
  2. %basePath% ==> $basePath$

Example contains:

• Bcm
• Bsc
• Lolz
• Mcm
• Mpz
• Nanozip
• Precomp
• Razor
• Uharc
• Zcm
• Zstd

^^
Thanks for the MTX update.
But in freearc alpha build struggled with Antivirus:(.
If we turnoff all Ok:rolleyes:

Maybe because of UPX. He has compressed all exe files with UPX?

it's common to see false positives due to upx. I didn't include any trojans with them. :p