1. Gfy
  2. pyReScene
  3. Issues
Issue #32 new

Need verification of sfv file before creating SRR.

fongod
created an issue

This is my second release that I can't rebuild because the sfv file was not proper when creating the SRR.

The first one "Fair_Strike-Razor1911.srr" is missing the file rzr-fs1.050 and rzr-fs1.051 from the cd1/rzr-fs1.sfv making it impossible to recreate and the second one "Knights_Of_Honor-MONEY.srr" has the files "mo-koha.050 to mo-koha.052' repeated in the CD1/mo-koha.sfv creating a weird error where the program is looking to rebuild a bin who is 30 MB bigger than it is supposed to be, because the program repeated the files inside the SRR.

My suggestion would be to compare the real files available to the files listed in the sfv before creating the SRR and create an error message if they are not identical.

NOTE: In the second case, the program was always using 447838374b instead of the random number of bytes trying to recreate the bin, and I was able to rebuild the release after editing the SRR (removing the double entries).

Comments (18)

  1. Gfy repo owner

    Can you upload the good .srr file of that second release then? I don't see it in our collision queue yet. We detect these issues if someone else uploads a good file. http://www.srrdb.com/release/details/Knights_Of_Honor-MONEY

    The SFV is there to verify the RARs and we create the SRR based on the SFVs. If a RAR volume from the .sfv doesn't exist, the creation will fail. The other way around does not. It is better to have that incomplete SRR than none. Then it should still be possible to reconstruct all in original form if you have the missing CRCs. (you need to do some programming then) But a complete working SRR is even better of course. Adding a check for the SFVs based on the file names should be possible.

    I see a small problem for some original releases that we wouldn't be able to create an SRR for then: the releases that the rarfixes fix and some rarfixes themselves if there were two files missing.

  2. fongod reporter

    If i knew where to get the missing CRC, I would have probably be able to rebuild the SRR. I wish I knew a place where to get those.

    The reason for the check is to let the user know that something is wrong with the sfv before he creates the SRR. Then it's up to the user to correct the sfv or to abort if he doesn't know how to modify it. The rarfixes must be added before creating the SRR, since before those fixes you can't extract the release (nothing to recreate with) and the sfv must also be corrected.

    I try to keep in mind that you and we have to rely on the user ability to verify the release before he creates and upload the SRR.

    Thank you for the fixed SRRs.

    NOTE: I found a quantity of SRR created from repacks (not the original files) and I have no idea how to report them, wish there was a report button on the site.

  3. Gfy repo owner

    "I would have probably be able to rebuild the SRR" So you can really code? This is a hard thing to do: you have to fix the headers based on the other volumes.

    "I wish I knew a place where to get those" make friends :) Just asking what you are looking for in the chat can do wonders too.

    A report button wouldn't be bad either. You can create an issue for it on the srrdb tracker if you want.

    Repacked games are often very old and and it is very hard to find the original packaging again. We keep those SRRs because everyone has the same files. Although I add ___repacked at the end of the srr name and upload it again. This way it is clear for the user it is a repack and we can detect them too if they are reuploaded.

  4. fongod reporter

    Coding is a big word, I can do some but not this kind. I learned to use the programs to recreate the files an then I use my best friend (WinHex).

    Create an issue about not being able to report SRR made from repacks, DONE.

    I don't like to ask for this kind of information as it can take a very long time to get an answer, when you get one. I prefer to look for it on a site with an immediate result.

    "There is an email address at the bottom of srrdb.com". Tried that, still waiting for a response one week later.

    The __repacked is a good idea. As you mentioned most of them are for very old releases and only the repacks are available. What I don't like to see is the same SRR re-uploaded without the "repacked" as if it was from the original files. The main problem is that most user don't realize that they downloaded repacks. They can't open the rar and look for the dates of the files (modified in 2006) for a release created in 1999.

    Thanks for the forum address, it might be useful.

  5. Gfy repo owner

    "still waiting for a response" hence at the bottom of my list. The owner can be busy with other stuff too and then forget it after a while.

    We have a list with dupe SRR files that need to be cleaned, but it's very long. Once that's done, we'll notice it sooner. However, there are releases that will always stay in that list because they had multiple pres or pred under different names.

    Another problem is that releases pre 2000 can be originally in .ace too for example.

    If you see issues, tell us. The only way we can do something about them is if we know about them.

  6. fongod reporter

    Looking at your sample, It will all depend on your guidelines.

    Alias.S01E20.Almost.The.Solution.DVDRip.XviD-VF must be removed (wrong label and missing dirfix)

    Alias.S01E20.The.Solution.DVDRip.XviD-VF.srr (good, but not original release name, dirfix corrected name, will appear in a list at the proper place for this release)

    Alias.S01E22.Almost.Thirty.Years.DVDRip.XviD-VF.srr (good original release name but dirfix must be applied as the content does not correspond to the label)

    Will need guidelines to know which one you want to keep in situations like these.

  7. Gfy repo owner

    That was an example where we will keep them all since they all have been pred. In most other cases we'll keep the original name and add the dirfix if we can find it.

    You also have to pay attention with these kind of releases. If you look in the wrong db, you could remove the wrong release, so we just keep all pred.

    corrupt-net.org: 2003-08-21 Alias.S01E20.DirFix.NfoFix.For.SE22.Read.NFO.XviD-VF 2004-05-06 Alias.S01E20.Almost.The.Solution.DVDRip.XviD-VF 2006-08-26 13:15:23 Alias.S01E22.Almost.Thirty.Years.DVDRip.XviD-VF 2006-08-26 13:42:54 Alias.S01E20.The.Solution.DVDRip.XviD-VF

    predb.me: 2003-08-22 Alias.S01E22.Almost.Thirty.Years.DVDRip.XviD-VF 2003-08-22 Alias.S01E20.DirFix.NfoFix.For.SE22.Read.NFO.XviD-VF 2004-05-03 Alias.S01E20.The.Solution.DVDRip.XviD-VF 2004-05-07 Alias.S01E20.Almost.The.Solution.DVDRip.XviD-VF

    layer13.it.cx: 2003-08-22 Alias.S01E22.Almost.Thirty.Years.DVDRip.XviD-VF 2003-08-22 Alias.S01E20.DirFix.NfoFix.For.SE22.Read.NFO.XviD-VF 2004-05-04 Alias.S01E20.The.Solution.DVDRip.XviD-VF 2004-05-07 Alias.S01E20.Almost.The.Solution.DVDRip.XviD-VF

    orlydb: 2003-08-21 Alias.S01E22.Almost.Thirty.Years.DVDRip.XviD-VF 2003-08-21 Alias.S01E20.DirFix.NfoFix.For.SE22.Read.NFO.XviD-VF 2004-05-03 Alias.S01E20.The.Solution.DVDRip.XviD-VF 2004-05-06 Alias.S01E20.Almost.The.Solution.DVDRip.XviD-VF

    other1: 2003-08-21 Alias.S01E20.DirFix.NfoFix.For.SE22.Read.NFO.XviD-VF 2004-05-06 Alias.S01E20.Almost.The.Solution.DVDRip.XviD-VF 353.423MB 25F 2006-08-26 13:42:54 GMT Alias.S01E20.The.Solution.DVDRip.XviD-VF 363.523MB 26F 2006-08-26 13:15:23 GMT Alias.S01E22.Almost.Thirty.Years.DVDRip.XviD-VF 353MB 25F [NUKED] mislabeled.should.be.S01E20.The.Solution

    other2: 2003-08-22 22:43:59 Alias.S01E20.DirFix.NfoFix.For.SE22.Read.NFO.XviD-VF 1.00MB 1F 2005-09-27 04:46:10 Alias.S01E20.Almost.The.Solution.DVDRip.XviD-VF 353.42MB 25F 2006-08-26 16:44:11 Alias.S01E20.The.Solution.DVDRip.XviD-VF 363.52MB 26F 2006-08-26 16:16:41 Alias.S01E22.Almost.Thirty.Years.DVDRip.XviD-VF 353.42MB 25F

    other3: 2003-08-21 Alias.S01E22.Almost.Thirty.Years.DVDRip.XviD-VF 353MB 25F 2003-08-21 Alias.S01E20.DirFix.NfoFix.For.SE22.Read.NFO.XviD-VF 1MB 1F 2004-05-03 Alias.S01E20.The.Solution.DVDRip.XviD-VF 353.423MB 25F 2004-05-06 Alias.S01E20.Almost.The.Solution.DVDRip.XviD-VF 353MB 25F

    other4: 2003-08-22 Alias.S01E22.Almost.Thirty.Years.DVDRip.XviD-VF 353MB 25F 2003-08-22 Alias.S01E20.DirFix.NfoFix.For.SE22.Read.NFO.XviD-VF 2004-05-04 Alias.S01E20.The.Solution.DVDRip.XviD-VF 353MB 25F 2004-05-07 Alias.S01E20.Almost.The.Solution.DVDRip.XviD-VF

    Many others are like these examples: Alice.im.Wunderland.1951.XVID-DVDRIP-GERMAN-GME2000 Walt.Disneys.Alice.im.Wunderland.1951.XVID-DVDRIP-GERMAN-GME2000 A.Nightmare.on.Elm.Street.2010.BluRay.1080p.VC1.5.1.WMV-INSECTS Nightmare.on.Elm.Street.2010.BluRay.1080p.VC1.5.1.WMV-INSECTS

    That last one is cut because it was created from Usenet for example. Then we keep the names of the removed ones in a list on the wiki.

  8. fongod reporter

    "so we just keep all pred" even if evidently somebody altered the name and re-pred a old release using the same files with a different title (Alias.S01E20.Almost.The.Solution.DVDRip.XviD-VF) especially when the new title is wrong as E20 was "The Solution" and E22 was "Almost Thirty Years"?

  9. Gfy repo owner

    Yes, looking at the SRR uploader, it's like that in archives. I just checked two torrent sites and they both have all 4 releases in their pack. Hence there is no such thing as "evidently". They will keep getting uploaded over and over again. How would you know they are all exactly the same release? Adding a note to the SRR page would be more useful. (but that feature doesn't exist yet)

  10. Log in to comment