Making -c mandatory?

Making -c mandatory?

hurda 11 Aug 2014 14:30

I noticed that somebody uploaded a srs for the following release: http://www.srrdb.com/release/details/Die.Reise.ins.Labyrinth.1986.German.DL.1080p.BluRay.x264.iNTERNAL-VideoStar

Problem is, you cannot recreate the sample from the full release:

W:\1080p\Die.Reise.ins.Labyrinth.1986.German.DL.1080p.BluRay.x264.iNTERNAL-Video
Star\Sample>C:\python33\python.exe c:\pyrescene\bin\srs videostar-labyrinth.1080
p-sample.mkv -c ..\videostar-labyrinth.1080p.mkv
File Details:   Size           CRC
                -------------  --------
                   79.955.204  C8ADDA4D

Track Details:  Track  Length
                -----  -------------
                    1     71.556.071
                    2      4.070.400
                    3      4.070.400
                    4         37.516
                    5         44.910
                    6         48.770
                    7         56.241
                    9         45.581

Parse Details:  Metadata     Attachments   Track Data     Total
                -----------  ------------  -------------  -------------
                     25.315             0     79.929.889     79.955.204

Checking that sample exists in the specified full file...
/
Unable to locate track signature for track 1. Aborting.
/
W:\1080p\Die.Reise.ins.Labyrinth.1986.German.DL.1080p.BluRay.x264.iNTERNAL-Video
Star\Sample>C:\python33\python.exe c:\pyrescene\bin\srs videostar-labyrinth.1080
p-sample.srs ..\videostar-labyrinth.1080p.mkv
SRS Load Complete...          Elapsed Time: 0.00s
Track Location Complete...    Elapsed Time: 86.57s

Unable to locate track signature for track 1. Aborting.

(The second command is made with the srs downloaded from srrdb.)

So I wondered what's the point of creating a srs at all without checking if the sample can actually be recreated from that file?

EDIT:
The problem with this particular release is, I guess, that the sample contains subtitle-streams, but the full release doesn't.

Last edited on 11 Aug 2014 14:44 by hurda Show more

Re: Making -c mandatory?

Gfy 12 Aug 2014 20:12

No. Never going to happen.

For me the ReScene project is in the first place about archiving history. It being useful in several other ways is just a nice side effect that also gives an incentive to contribute.

The example SRR you point to is created with pyReScene Usenet 1.5. This means that the uploader doesn't have the release at all. He just created it on the fly from Usenet and downloaded the sample to create a .srs file. Making it mandatory causes an awful lot of valid uploads to be missed. I doubt anyone thinks that will be better.

We noticed the leaked preview is able to rebuild some more files. It's not because it fails now that it'll always fail. The tools have their limitations too. Similar with SRRs for compressed RARs.

Creating an SRS with -c can consume a lot more time. Worst case: the whole main movie file is read again. Auto uploaders have busy systems and might not want to lose resources on this.

A .srs file is better than a .txt file. It provides more info.

A sample from a nuked release added to the PROPER release can't be reconstructed either without having the original file.

Thousands of SRS files have been added by people not having the actual release.

What you and others can do: create SRR files with pyReScene Auto using the -s parameter. After being uploaded, the best sample will be used. I've added the --best parameter that includes the option, but if verification fails, an SRS file will always be created if possible.

It could be a feature for srrDB to be warned that reconstruction will fail.