i am getting this error with some releases.
is there a way to force pyReScene to use a specific rar executable to rebuild the release when pyReScene is unable to detect the good version?
we can check the files with sfv afterwards, right?
If pyReScene is unable to detect the good version, forcing a rar executable won't magically spit out all the good rars.
If you think there could be intermediate good RAR volumes generated, play around with the code.
All the settings are stored in srr file, right?
The only problem is that pyReScen is unable to detect the good rar.
If there was an option to force pyReScene to use the desired RAR executable for reconstruction, that could solve the issue.
If there was such an option, we could repeat the process with various RAR executable manually, till we get the correct RAR volumes.
Is it possible?
I don't know how to edit the codes, if it is possible, please tell me how to edit the codes.
Not all, but most can be derived from the SRR. Something like the number of threads used, is not. This means it might not even be possible to recreate the original RAR files on your hardware.
No, the problem is pyReScene can't find the right settings to use a good rar.exe file. And even if they are right, it might use them the wrong way.
I'll repeat myself:
forcing a rar executable won't magically spit out all the good rars.