The "compression is used" notice is correct because this release was PRE'd on 2019-05-21 so before the senseless compression requirement for NSP releases was dropped (see the second last nested spoiler in
this comment for context):
Code:
$ 7z l -slt Assassins_Creed_III_Remastered_Russian_Audio_Pack/sxs-asscrr_ru_dlc.rar | grep '^Method'
Method = m1:22
$ srr -e Assassins_Creed_III_Remastered_Russian_Audio_Pack.srr | grep '^+METHOD' | tail -n +2
+METHOD: Fastest compression
+METHOD: Fastest compression
+METHOD: Fastest compression
+METHOD: Fastest compression
+METHOD: Fastest compression
+METHOD: Fastest compression
But the srrDB project would be much less useful if pyReScene did not support creating SRRs from compressed releases, which can be enabled with the
-c argument. Rescening often works, provided you have the correct RAR executable and sometimes the right
--mt-set value like in
this case. Though what you will really come to dread is the "custom RAR packer detected" warning at the bottom of the table, that you will see on some releases by RELOADED and their subgroups (
example).
For rescening to succeed the SRR file must contain the RAR metadata, which you can quickly check by looking for the "RAR-files" and "archived files" rows on the srrDB page. Compare
The.Legend.of.Zelda.Breath.of.the.Wild.PROPER.NSW-BigBlueBox to
The_Legend_of_Zelda_Breath_of_the_Wild_Update_v1.6.0_NSW-SUXXORS. The latter can be rescened, as its SRR includes the required data, while the former cannot, since only the NFO and SFV were stored.
Because pyReScene still does not support RAR5 archives, like you said, and auto-leechers seem to lazily use the default SRR upload script, srrDB would not have have any entries for RAR5 releases if manual backfillers did not use a rather simple albeit flawed workaround:
1. Move/rename the SFV (to prevent pyReScene from parsing the RAR parts and exiting with the RAR5 error message)
2. Run
pyrescene RELEASE (to create an SRR containing only the NFO)
3. Move/rename the SFV back
4. Run
srr -s SFV RELEASE.srr (to also store the SFV in the SRR)
This will create a technically valid file, as SRR is a general container format (see the
), but will not enable recreating the original scene archive. At least it makes the included files (NFO, SFV, proof JPG, trainers, etc.) more easily accessible.
On a related note: If you are unsure whether an archive is in the RAR5 format or not, a simple sign for split parts is often that they use the
.partXX.rar naming scheme instead of the old
.rXX one, though it was first introduced with RAR4. To be certain open the archive in a hex editor and look at the seventh byte. A RAR5 file will have a value of
0x01 (see the
):
Code:
$ xxd -s 6 -l 1 -ps The.Legend.of.Zelda.Breath.of.the.Wild.PROPER.NSW-BigBlueBox/bbb-h-aaaaap.part01.rar
01
$ xxd -s 6 -l 1 -ps The_Legend_of_Zelda_Breath_of_the_Wild_Update_v1.6.0_NSW-SUXXORS/sxs-tlozbotw_v786432.rar
00
