Release note of version 1.3.2.1
This commit is contained in:
113
README.md
113
README.md
@@ -1,72 +1,63 @@
|
||||
# MultiPar
|
||||
|
||||
v1.3.2.0 is public
|
||||
v1.3.2.1 is public
|
||||
|
||||
This is a beta version to test new encoder & decoder.
|
||||
I implemented a way of Cache Blocking for CPU's L3 cache optimization.
|
||||
It will calculate multiple blocks at once on multi-Core CPU.
|
||||
Old method calculated each block independently,
|
||||
and could not avail the advantage of shared memory.
|
||||
New method may use shared L3 cache more often, and will be fast on recent PCs.
|
||||
This includes some bug fix and a sample of new feature.
|
||||
I found a problem in my old code, and fixed them.
|
||||
Because they are 32-bit version PAR2 client and PAR1 client, nobody saw them for long time.
|
||||
Thanks [Safihre for finding the bug](https://github.com/Yutaka-Sawada/MultiPar/issues/55).
|
||||
|
||||
Thanks [prdp19 and Slava46](https://github.com/Yutaka-Sawada/MultiPar/issues/47) for many tests.
|
||||
Thanks [Anime Tosho](https://github.com/Yutaka-Sawada/MultiPar/issues/21) for some idea and advice.
|
||||
Also, other users aided my development.
|
||||
Without their help, I could not perform this speed improvement.
|
||||
I changed some behavior of handling invalid filenames on Windows OS.
|
||||
In previous version, those bad filenames were sanitized automatically.
|
||||
But, it might be strange and confused users of other OSes.
|
||||
Thanks [Danilo for reporting the issue](https://github.com/Yutaka-Sawada/MultiPar/issues/58).
|
||||
Now, this version warns such incompatible filenames only.
|
||||
Because it's difficult to rename some bad fileanames on Windows Explorer,
|
||||
I made a simple tool to rename invalid filenames, too.
|
||||
The [tool "Rename7" is available on my GitHub page](https://github.com/Yutaka-Sawada/Rename7).
|
||||
|
||||
While new version seems to be faster on most cases,
|
||||
it may happen to be slow for a few blocks.
|
||||
Though I don't know the speed on old PCs, it may not become slow.
|
||||
If you see a failure or strange result, please report the incident with ease.
|
||||
I will try to solve as possible as I can.
|
||||
|
||||
I adjusted CPU usage slider for CPUs with many Cores.
|
||||
Now, each position will set different number of threads always.
|
||||
Left most : 1/4 of CPU cores
|
||||
One from left : 2/4 of CPU cores
|
||||
Middle : 3/4 of CPU cores
|
||||
One from right : 4/4 of CPU cores, or use one less threads on CPU with 6 or more Cores.
|
||||
Right most : May use one more threads on CPU with 5 or less Cores.
|
||||
|
||||
I improved calculating hash of multiple source files.
|
||||
From my testing result, I changed default number of threads for NVMe SSD.
|
||||
When you use a raid-system or external drive, it cannot detect the drive type.
|
||||
If it fails to detect, it uses HDD mode by default.
|
||||
At MultiPar options, it's possible to change the setting manually.
|
||||
You may select one of them; HDD, SSD, or Fast SSD.
|
||||
Caution, you should not select SSD, if your using drive is HDD.
|
||||
Some [users requested a queue repair feature](https://github.com/Yutaka-Sawada/MultiPar/issues/57) ago.
|
||||
I didn't make such utility, because there were some tools for the usage.
|
||||
But, it seems to be old, or it's not updated so much.
|
||||
So, I implemented a feature to repair multiple PAR2 recovery sets in queue.
|
||||
Currently, it's a simple tool and will be changed more.
|
||||
If a user is interested in the feature,
|
||||
please read "Command_Queue.txt" in "help" folder.
|
||||
Because it's sample, there may be a problem or fault.
|
||||
I will improve later, when users tested the behavior.
|
||||
|
||||
|
||||
[ Changes from 1.3.1.9 to 1.3.2.0 ]
|
||||
[ Changes from 1.3.2.0 to 1.3.2.1 ]
|
||||
|
||||
GUI update
|
||||
- New
|
||||
- For a folder with PAR2 files, MultiPar may invoke ParQueue.
|
||||
|
||||
- Change
|
||||
- Fast SSD is selectable as file access mode.
|
||||
- Max number of log files was increased from 100 to 1000.
|
||||
- CPU usage slider was adjusted on CPU with 6 or more Cores.
|
||||
- Shadow of text over progress-bar becomes more smooth.
|
||||
- In command-line, it uses "/" for each option instead of "-".
|
||||
|
||||
All clients update
|
||||
- Change
|
||||
- It will warn incompatible filenames on Windows OS.
|
||||
|
||||
PAR1 client update
|
||||
- Bug fix
|
||||
- Failure in setting a file pointer was fixed.
|
||||
|
||||
PAR2 client update
|
||||
- Change
|
||||
- Standard buffer size becomes double to decrease iteration.
|
||||
- Single byte error in a single slice file may be corrected.
|
||||
- Number of using threads was changed on CPU with 6 or more Cores.
|
||||
- Enabling GPU won't use additional threads on multi-core CPU.
|
||||
- Progress percent may move while writing blocks.
|
||||
|
||||
- Improvement
|
||||
- L3 cache optimization was implemented for multi-core CPU.
|
||||
- Bug fix
|
||||
- Possible stack overflow at searching missing files was fixed.
|
||||
|
||||
|
||||
[ Hash value ]
|
||||
|
||||
MultiPar1320.zip
|
||||
MD5: 56524875BC77FD7A4E51A9E2C3F834CB
|
||||
SHA1: 245F3432DBCCAD335AEB2A70371EE57EFEF52CE7
|
||||
MultiPar1321.zip
|
||||
MD5: FC155A166F5C31F7FA2373F06A866427
|
||||
SHA1: 2E4DF4FF1DDEC301A51A9FA33C4F66B41D1F24C2
|
||||
|
||||
MultiPar1320_setup.exe
|
||||
MD5: 5D0A51F48CDE8FCB0B87CC949BE84DD1
|
||||
SHA1: B727D5193697E8C0A2335DB8233874CBDAFDEE40
|
||||
MultiPar1321_setup.exe
|
||||
MD5: B4D94783D4CB3A72EEBF51A893C1ED39
|
||||
SHA1: B22AE13319FD3856BD4E9D7CC042119FDF6A4E34
|
||||
To install under "Program Files" or "Program Files (x86)" directory,
|
||||
you must start the installer with administrative privileges by selecting
|
||||
"Run as administrator" on right-click menu.
|
||||
@@ -77,17 +68,17 @@ you must start the installer with administrative privileges by selecting
|
||||
[GitHub](https://github.com/Yutaka-Sawada/MultiPar/releases) or
|
||||
[OneDrive](https://1drv.ms/u/s!AtGhNMUyvbWOaSo1n_R8awJ_hg0?e=4V0gXu).
|
||||
|
||||
MultiPar_par2j_1320.7z
|
||||
MD5: 5DBF880047D05BC2E8FE349DC6EC610C
|
||||
SHA1: 1D50EFE97A7812B6AF0090B83AAEE61BCBABD1ED
|
||||
MultiPar_par2j_1321.7z
|
||||
MD5: 4853C852E6DAEB8BCC034595C46CFE87
|
||||
SHA1: 24027B8E91DD32EF3A16931091BBD84D88EDBDBF
|
||||
|
||||
MultiPar_par1j_1318.7z
|
||||
MD5: F66285403BA0AD856BA6A8CCD922EBF5
|
||||
SHA1: 4CF5D819B16E60F1BBD82415D5F68CB46D3F53C3
|
||||
MultiPar_par1j_1321.7z
|
||||
MD5: 2BE9BCCA25672BD7FC6773B6D5C3A831
|
||||
SHA1: 2F3759136922627ADFC6197D0CA3911508104694
|
||||
|
||||
MultiPar_sfv_md5_1318.7z
|
||||
MD5: 4E6433808625C088E2773C961BBEBBD2
|
||||
SHA1: 68B54D178BA58637F63CC3E0CC656C96D4472A33
|
||||
MultiPar_sfv_md5_1321.7z
|
||||
MD5: 5CD627C2D768290EF574230259A19487
|
||||
SHA1: E768B38783DF56289549BBAA3D65DBDAE679213B
|
||||
|
||||
MultiPar_ShlExt_1320.7z
|
||||
MD5: C413655ABF85BCFF3D4B349BAAADC24B
|
||||
|
||||
Reference in New Issue
Block a user