Matching fails with ValueError: The first argument of bincount must be non-negative about audfprint HOT 2 CLOSED

The problem was in the way _approx_match_counts uses np.bincount to quickly count the most popular combinations of IDs and time offsets (to identify the reference files with the best match). It combines them into a single int by shifting the IDs up by enough bits to make them clear of all the time offsets. In this case, the input file was very long (7 hours), to to be clear of all the time offsets, timebits was 21. Then allids included numbers up to 2973 (i.e., 11 bits wide). Shifting these values up by 21 bits caused bit 32 to be set; because the values had been taken out of the big hash table, they were 32 bit ints, so when the top bit was set, they flipped to become negative.

Converting allids and alltimes to default (64 bit) ints seems to fix the problem.

from audfprint.

closed via a076c60

from audfprint.