Release note of version 1.3.2.7
This commit is contained in:
90
README.md
90
README.md
@@ -1,78 +1,44 @@
|
|||||||
# MultiPar
|
# MultiPar
|
||||||
|
|
||||||
### v1.3.2.6 is public
|
### v1.3.2.7 is public
|
||||||
|
|
||||||
I added a new feature and changed some default behavior in this version.
|
This is a minor update version for Python script users.
|
||||||
I explain the difference below.
|
There is no difference in basic feature.
|
||||||
Be careful to use them.
|
If you don't use Python script, no need to update.
|
||||||
If you see a strange, odd, or wrong behavior, please report with ease.
|
When there is no problem in this version,
|
||||||
I will fix as possible as I can.
|
next version will be the last of v1.3.2 tree.
|
||||||
|
|
||||||
I saw [a question](https://github.com/Yutaka-Sawada/MultiPar/discussions/64) about number of recovery files.
|
There are some Python script files in `tool` folder of MultiPar.
|
||||||
Max number of recovery blocks was limited to the max source file size.
|
Users may edit them for thier usage.
|
||||||
At old time, this limit was made to be similar to QuickPar.
|
As I'm learning Python language still, I may modify these samples later.
|
||||||
I changed the default setting from this version.
|
When a user request a new feature in MutliPar,
|
||||||
In old versions, recovery file size was limited by default.
|
I may implement it as an independent tool.
|
||||||
If you wanted to disable the limit, you needed to set larger limit size at `Limit Size to` option.
|
Users would edit them for thier usage.
|
||||||
In new version, recovery file size isn't limited by default.
|
|
||||||
If you want to limit, you need to set the limit size at `Limit Size to` option.
|
|
||||||
I added an option `RecoveryFileLimit` on `MultiPar.ini`.
|
|
||||||
If you want to limit recovery file size by the max source file size as same as old versions,
|
|
||||||
add a new line `RecoveryFileLimit=1` in the .INI file.
|
|
||||||
|
|
||||||
While reviewing my old source code, I found an obsolate point.
|
|
||||||
I omitted one step in verification for speed ago.
|
|
||||||
Because recent CPUs are much faster than before,
|
|
||||||
I enabled searching duplicated blocks at simple verification.
|
|
||||||
When you select `Simple verification` at `Verification level`,
|
|
||||||
it may become slightly slow.
|
|
||||||
Most users won't see any difference.
|
|
||||||
|
|
||||||
I implemented [a new feature](https://github.com/Yutaka-Sawada/MultiPar/issues/74).
|
|
||||||
It tries to repair damaged files by over writing recovered blocks directly.
|
|
||||||
It doesn't make temporary files.
|
|
||||||
To enable the feature, select `Aligned verification` at `Verification level` option.
|
|
||||||
You must understand good and bad points of this mode.
|
|
||||||
Becasue it's testing period still, I may change the behavior in future.
|
|
||||||
|
|
||||||
Pros:
|
|
||||||
- Fast verification.
|
|
||||||
- Fast recovery.
|
|
||||||
- Less disk space.
|
|
||||||
|
|
||||||
Cons:
|
|
||||||
- Backup of damaged files is disabled.
|
|
||||||
- Less finding available source blocks.
|
|
||||||
- Cannot treat splited source files.
|
|
||||||
- Cannot treat additional source files.
|
|
||||||
- Cannot treat external source files.
|
|
||||||
- Risk of more data loss at failed recovery.
|
|
||||||
|
|
||||||
|
|
||||||
[ Changes from 1.3.2.5 to 1.3.2.6 ]
|
[ Changes from 1.3.2.6 to 1.3.2.7 ]
|
||||||
|
|
||||||
Installer update
|
Installer update
|
||||||
- Inno Setup was updated from v6.2.0 to v6.2.1.
|
- Inno Setup was updated from v6.2.1 to v6.2.2.
|
||||||
|
|
||||||
GUI update
|
GUI update
|
||||||
- Change
|
- New
|
||||||
- It won't limit size of Recovery Files by default.
|
- It's possible to start Python script as batch processing.
|
||||||
- Aligned verification is available for test.
|
|
||||||
|
|
||||||
All clients update
|
PAR2 client update
|
||||||
- Change
|
- New
|
||||||
- Original filename item was removed from version information.
|
- It's possible to save verification result on JSON file.
|
||||||
|
|
||||||
|
|
||||||
[ Hash value ]
|
[ Hash value ]
|
||||||
|
|
||||||
MultiPar1326.zip
|
MultiPar1327.zip
|
||||||
MD5: 9CD095ABF31A2A9978A2FF79EDC47C6D
|
MD5: 72909EA45889CEC681E5F458E43F6666
|
||||||
SHA1: 7FDDB03B68CFAE404F54A67559BE0DA29CEE5374
|
SHA1: 278EB9128FEB8839792A6340DC29381E7966F655
|
||||||
|
|
||||||
MultiPar1326_setup.exe
|
MultiPar1327_setup.exe
|
||||||
MD5: 36AB1A803538D4CC60EF2D9E30ABEC7B
|
MD5: 85DFD7C9DF386F52420BD9FDE1A5A4DA
|
||||||
SHA1: 3E7A2ED2D2ED01F80964D865F7616EE4E3CA2D5E
|
SHA1: E127588A243D8E80516D5DB60C9F92A213200E16
|
||||||
To install under "Program Files" or "Program Files (x86)" directory,
|
To install under "Program Files" or "Program Files (x86)" directory,
|
||||||
you must start the installer with administrative privileges by selecting
|
you must start the installer with administrative privileges by selecting
|
||||||
"Run as administrator" on right-click menu.
|
"Run as administrator" on right-click menu.
|
||||||
@@ -83,9 +49,9 @@ you must start the installer with administrative privileges by selecting
|
|||||||
[GitHub](https://github.com/Yutaka-Sawada/MultiPar/releases) or
|
[GitHub](https://github.com/Yutaka-Sawada/MultiPar/releases) or
|
||||||
[OneDrive](https://1drv.ms/u/s!AtGhNMUyvbWOaSo1n_R8awJ_hg0?e=4V0gXu).
|
[OneDrive](https://1drv.ms/u/s!AtGhNMUyvbWOaSo1n_R8awJ_hg0?e=4V0gXu).
|
||||||
|
|
||||||
MultiPar_par2j_1326.7z
|
MultiPar_par2j_1327.7z
|
||||||
MD5: 2BC1FF60C2470119D0C2F1956260BF70
|
MD5: 84B07B477714E64272828F2C1A246899
|
||||||
SHA1: 4554C5C01B9F8C4B14D23BE010A8866AF447B5BC
|
SHA1: 76B8DD02C24D39C473C119478D589BE7E1737E8A
|
||||||
|
|
||||||
MultiPar_par1j_1326.7z
|
MultiPar_par1j_1326.7z
|
||||||
MD5: 72C640381C56373CA56A73157A5AA026
|
MD5: 72C640381C56373CA56A73157A5AA026
|
||||||
|
|||||||
Reference in New Issue
Block a user