Android custom catalog match

Question

Hello, we've encountered issues on Android using Custom Catalogs.

On Android the only possible way to create a custom catalog is using .addFromCatalog() from a .shazamcatalog file, there is no method like iOS SDK provides .addReferenceSignature() to add a signature.
Generating from iOS a .shazamcatalog file and loading in Android returns wrong values for query signature duration:

Android

catalog.minimumQuerySignatureDurationInMs: 3000
catalog.maximumQuerySignatureDurationInMs: 2147483647

iOS

minQuerySignDuration:  1.0 seconds
maxQuerySignDuration:  12.0 seconds

No match resulting for Android but iOS works as expected.

Is it possible to match against a custom catalog on Android?

Any help will be much appreciated.

525

Posted by

andzk

Reply

Add a Comment

Answer 1

Hi @andzk, thank you for opening the Feedback.

So what's happening is the Android SDK disregards a signature (or clusters of signatures) that have no associated metadata. I suggest when you populate a custom catalog to also provide metadata for any signature ( see https://developer.apple.com/documentation/shazamkit/shcustomcatalog/3747140-addreferencesignature).

I have tried with a custom catalog following such recommendation and I was able to get matches. We will be working with the team to consolidate a common behaviour with the iOS counterpart in the future.

Best Regards

Posted by

FrancescoPz

Hi @FrancescoPz, adding metadata to signatures, fixes the problem, Android can get matches too. Thank you.

—
andzk

Add a Comment

Answer 2

iOS works as expected.

Good news (no surprise).

Android questions are not for this forum. You should ask on Android forum.

Posted by

Claude31

Hey Claude,

Apple develops the ShazamKit SDK for Android too. If there is a better place to post my question, can you point me to it?

—
andzk

Add a Comment

Answer 3

Hi @andzk please find some notes here:

On Android the only possible way to create a custom catalog is using .addFromCatalog() from a .shazamcatalog file

That is correct. Adding custom signatures to a catalog is currently not supported by the Android SDK.

Android returns wrong values for query signature duration:

The two boundaries (minimumQuerySignatureDurationInMs and maximumQuerySignatureDurationInMs) should be respected as they might change in the future and they don't necessarily need to adhere to the iOS counterpart.

No match resulting for Android

Please open a Feedback request with a sample project containig a custom catalog, the audio and the steps to reproduce your issue.

Best Regards

Posted by

FrancescoPz

Hi @FrancescoPz,

I opened a feedback request here, FB9773953 (ShazamKit SDK no matches found for Android (iOS works))

Thank you

—
andzk

Add a Comment

Answer 4

Hi @andzk, thank you for opening the Feedback.

So what's happening is the Android SDK disregards a signature (or clusters of signatures) that have no associated metadata. I suggest when you populate a custom catalog to also provide metadata for any signature ( see https://developer.apple.com/documentation/shazamkit/shcustomcatalog/3747140-addreferencesignature).

I have tried with a custom catalog following such recommendation and I was able to get matches. We will be working with the team to consolidate a common behaviour with the iOS counterpart in the future.

Best Regards

Posted by

FrancescoPz

Hi @FrancescoPz, adding metadata to signatures, fixes the problem, Android can get matches too. Thank you.

—
andzk

Add a Comment

Android custom catalog match

Accepted Reply

Replies