Sab using par2-classic

[aceor44]

Hi,

Long time user, first time poster. Great application, and thanks to everyone that puts time into this project.

As I said, I am a long time user of SAB, and it's always been solid. Recently, my main hard drive crashed, and I had to replace the drive (with a WD BLACK) and then reinstall everything. SAB is working fine, except when it has to repair something. The repair process is very slow now (wasn't previous to the crash). So I had a look at Task Manager, and I can see it's running 'par2-classic.exe *32'. I know that's not right, so i head into the Post Processing section of Config-Switches. 'Enable MultiCore Par2' is checked. Then, I looked at the Special Configs, and par2_multicore is checked. So now I am stumped as to why SAB is using par2-classic instead of par2. (And this all assumes my initial assessment is the reason why it's slow to repair!)

Help?

System:
WHS2011
AMD Triple core 720
6 GB ram
tons of HD, but SAB runs on a dedicated WD Black drive that is not in any sort of pool.

[shypike]

It would be useful if you told us which version of SABnzbd you are using.

Also, a minority of downloads require par2-classic, because par2-tbb crashes
or is incompatible with the par2 files.

[shypike]

Never mind the version.
You're right, the current version does seem to have this problem.

[aceor44]

SABnzbd Version: 0.7.3

It's 3 d/ls in a row that are using classic to repair files.

BTW, which version of par does the verify stage use?

[shypike]

BTW, which version of par does the verify stage use?

All the same.

[aceor44]

Never mind the version.
You're right, the current version does seem to have this problem.

Sounds like you've recreated the problem. Excuse my ignorance of the process, but what happens next? Does a fix get scheduled for the next release?

[shypike]

Does a fix get scheduled for the next release?

The problem has been solved in source code and will be in the next release.