View source for NCDI/Checksum

The checksum is handled by taking each track offset and summing them together, resulting in a "large number", which is then brought into the range of 0-4095 by applying mod4096.

;Q:Why 4096?
;A:Cos FFF in hex is a nice size for the checksum to be

;Q:Why not 255 (FF) or 65536 (FFFF) then?
;A:255 and 65536 were both tested with a conversion script which generated NCDI's from the FreeDB database. 65536 gave no appreciable improvement for guaranteed uniqueness, and 255 was ''(awaiting actual data for this ;)''