You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 18, 2022. It is now read-only.
An issue was reported on forum where par-repair fails with message:
repair completed but the data files still appear to be damaged
It seems the issue is caused by posters using development version of ParPar, a version which wasn't released for public usage actually.
Par2 file format specification describes a field of par2-file containing identification information about application which created par2-files. The specification also says:
If a client is unable to process a recovery set, the contents of the creator packet must be shown to the user. The goal of this is that any client incompatibilities can be found and resolved quickly.
If NZBGet would print par2 creator that would certainly helped to identify the cause of the issue sooner.
The text was updated successfully, but these errors were encountered:
An issue was reported on forum where par-repair fails with message:
It seems the issue is caused by posters using development version of ParPar, a version which wasn't released for public usage actually.
Par2 file format specification describes a field of par2-file containing identification information about application which created par2-files. The specification also says:
If NZBGet would print par2 creator that would certainly helped to identify the cause of the issue sooner.
The text was updated successfully, but these errors were encountered: