Implementation Opensubtitles hash

http://ds6.ovh.org/lib.main.c.zip

Only copy main.c to bitcollider0.0.6/lib/main.c and compile. A don’t generate diff but mark differences (ctrl+f) and search “turbos”.

Please add to database this tag:

tag.video.oshash

tag.video.subtitleforthisfile

Do you do it?

Can you add this to official release of bitcollider?

Nice day.

Thanks! I will have a chance to look over this code and the necessary server-side support later in the week.

For my reference, what's the best/official description of how the 'oshash' is calculated and what legal values look like?

What sort of information would be in a 'tag.video.subtitleforthisfile' tag?

(Is it an URL? Is it found inside the target file itself, in some cases, or always added by a user at some outside reference site?)

- Gordon @ Bitzi

Oshas is 64bit number, write hexadecimal – 16 chars.

OShas values is from 000000000000000 to fffffffffffffff. (only chars 0-9,a-f).

Calculation get 8192 64bit numbers from beginning of file,

8192 numbers from end of file, get filesize. And add all. This is sum.

See description on http://trac.opensubtitles.org/projects/opensubtitles/wiki/HashSourceCodes

tag.video.subtitleforthisfile is url. Site only display subtitles for this movie version.

Like his:

http://www.opensubtitles.org/search/sublanguageid-all/moviebytesize-146987008/moviehash-3445bb088d420e8b

It only have filesize and oshash. You don’t must save it in database. You may generate it from oshash.

Sometimes You may ignore filesize:

http://www.opensubtitles.org/search/sublanguageid-all/moviehash-3445bb088d420e8b

good work! Also it should be mentioned, that 16bit should be padded with 0, because you can have sometimes 15bit crc.

Forward to see some nice implementations :)