Is the Track ID Search Still Around?

[cesser000]

Hey everyone - I'm sure this has been discussed before, but if so I am oblivious of it    - 2 or 3 years ago there was a search device set up where people on here were submitting their music libraries to a custom database and then you could upload a track of your own to check against the database for track IDs.

I used this a bunch back then and got several IDs, but it's been a while now, I lost the link to the search, and I'm guessing this is no longer active?

[ChunYinZi]

From what I understand.

The program has been available since the earliest days and has been updated over time.

But after upgrading to version 2.5.0, which is the latest version, there's a bug that produces a lot of invalid results so that you don't know which message is the right one.

The old version is not working anymore and will force you to update it.

The developer of the program hasn't been around for a long time.

But he open-sourced his program, so if someone could program it, they could make a new program, and it's not that complicated.

[cesser000]

Thanks for that info.  Is there a link to the current version somewhere?

[lbjames]

hxxps://github.com/mitin001/audfprint-gui

[stackjackson]

Moved to General Discussion

[MrDee2534]

But after upgrading to version 2.5.0, which is the latest version, there's a bug that produces a lot of invalid results so that you don't know which message is the right one.

try opening "%USERPROFILE%\AppData\Local\Programs\audfprint-gui\resources\app.asar" with HxD (Freeware Hex Editor and Disk Editor)
and search getAudfprintScript(['match', '-N', 2, '-d', dbFilename, ...precomputePaths, '-R']);

from:
getAudfprintScript(['match', '-N', 2, '-d', dbFilename, ...precomputePaths, '-R']);

to:
getAudfprintScript(['match', '-N', 5, '-d', dbFilename, ...precomputePaths, '-R']);

or goto bytes offset 9931195 (9789BB) and change from 2 to 5 (5 is default for audfprint.py)

to fix a lot of invalid results.