Improve match results (iOS/ Android)

Question

andzk OP

Created Nov ’21

Replies 1

Boosts 0

Views 1k

Participants 2

The resulted matches from a custom catalog on both iOS/ Android are a bit delayed (1-3+ seconds)

How to test? (iOS)

Prepare AVAudioPlayer with recorded audio.
Load custom catalog & listen to recorded audio from an external source.
When a match is found, play recorded audio from the AVAudioPlayer at: predictedCurrentMatchOffset

Result: 1-3+ seconds delayed matches

Question

How to improve or filter the resulting matches to be close if not exact to the external audio source?

Experimental

Filtering results by frequencySkew close to 0, does not minimize delayed matches.

[{
    "sh_audioStartDate" = "2021-11-24 12:34:42 +0000";
    "sh_frequencySkew" = "2.222024e-05";
    "sh_matchOffset" = "388.3738065670163";
    "sh_score" = "4302.546";
    "sh_speedSkew" = "0.0009712927";
    "sh_title" = ItemTitle;
}]

Printing the matchedMediaItems, there is a “sh_score”, maybe we can experiment with? But it’s not a public property

Best regards.

Answered by Technology Evangelist in 696489022

Hi @andzk. Thanks for the question. Can you open a Feedback Request with the info above and attach a sample project with a sample catalog for us to test against, please?

Custom Catalogs are matched locally on device so the expectation is for that delay to be a fraction of what you're getting.

Thanks.

Boost

Answer 1

Technology Evangelist OP

Apple

Nov ’21

Accepted Answer

Hi @andzk. Thanks for the question. Can you open a Feedback Request with the info above and attach a sample project with a sample catalog for us to test against, please?

Custom Catalogs are matched locally on device so the expectation is for that delay to be a fraction of what you're getting.

Thanks.

0