Chromaprint API default config is different than the one used in Chromaprint::Fingerprinter

[Anatoliy Atanasov]

In Chromaprint API the recommended value for the algorithm used during the creation of a context is CHROMAPRINT_ALGORITHM_DEFAULT which corresponds to CHROMAPRINT_ALGORITHM_TEST2

In the C++ code Chromaprint::Fingerprinter constructor's default value for this algorithm, if nothing is specified, is CHROMAPRINT_ALGORITHM_TEST1

This difference leads to different fingerprints between the API and the C++ classes to compare results.

The workaround for this is to explicitly use the same value of the config parameter for the both instances.

[Lukáš Lalinský (luks)]

The C++ code is not meant to be public (it could be, but it would have to be rewritten so that we can easily maintain binary compatibility). I kept it on CHROMAPRINT_ALGORITHM_TEST1 for now, so that some tests that I've written before still work.