How to use is almost same as QuickPar. But there are some different behavior, because the development environment and how to implement are different. Moreover I added some useful features which QuickPar lacks; such like supporting directory tree or preview before creation. If you have a new idea, you may request by mail.
 
While QuickPar's default settings are optimized for UseNet, they are different from those of MultiPar.
If you want to set similar setting as QuickPar, you need to change the following items from default setting;
On [GUI options] page, in [Restrict block size to multiples of the unit] section,
 
select "For yEnc: 3,000 lines".
On [GUI options] page, in [Block allocating method] section,
 
check "Limit Block count up to: 3,000" and set "Block size: 384,000".
On [Client behavior] page, in [Creation options] section,
 
check "Don't search subfolders".
On [Client behavior] page, in [Verification and Repair options] section,
 
select "For 15 days" at "Re-use verification result".
  There are some different behavior between MultiPar and QuickPar. Because MultiPar tries to select efficient block size to create PAR2 files, initial block count may differ, even when the setting is same. If you want "Recovery File Size: Variable (power of 2 sizing scheme)" in QuickPar, select "Sizing scheme: Variable size" in MultiPar. When you create additional recovery files against existing recovery set by "Extra", QuickPar creates extra files without modifying original files, but MultiPar re-creates all files by over-writing original files.
  The biggest difference between MultiPar and QuickPar is the support of multi-languages. While QuickPar saves non-ASCII filename by a system specific character encoding, MultiPar saves by UTF-8. Then, QuickPar cannot read non-ASCII filename correctly which was saved by MultiPar. In PAR2 clients, MultiPar and par2_tbb can support Unicode filename.
 
Because Peter Clements allowed me to use similer GUI with QuickPar,
I made MultiPar to treat Japanese filename.
I made English GUI for foreign users, who got failure in QuickPar.
When you have trouble using other PAR clients, MultiPar will help.
If you want to translate MultiPar's text or message, send mail to me.
MultiPar is used in many countries like;
America, Belgium, China, Denmark, England, France, Germany, India, Italy, Japan, Netherlands, Poland, Portugal, Russia, Spain, Ukraina, and so on.