Worked great the first few times I've used it, but now whenever I try and identify a song on YouTube (and other sites) using this, I get this error:

"Recognition failed: authorization failed: no api_token passed and the limit was reached. Get an api_token from dashboard.audd.io and make sure you're passing the token in the `api_token` parameter."

What should I do because I don't want to pay for the API thing?

I've tested this extension and for some times now and while it's being really great and responsive, something doesn't really work correctly on the Firefox extension only.

I have tested the AudD extension on both Firefox and Chrome, and it appears that the Firefox extension has an issue at the end of song identification.

In Chrome, when initiating a song search, there is an audible cut (similar to a pop) when the extension begins listening, and another when it either identifies the song or fails to do so, which is expected behavior.

However, in Firefox, the initial cut is heard when starting a song search, but not when it ends; the issue arises when any subsequent song is played in the same tab, producing the cut/pop at the beginning of each song, as if the extension continues to listen even when inactive.

The only solution seems to be refreshing the tab after using AudD to prevent the cut/pop from occurring when a new sound plays from the same tab.

Changed my original 1-star review to 4 stars after reading Developer response. I was originally under the impression that this requires Sign Up and is only a Free Trial of an extension. I thought this for a few reasons:

1) Before using, I read other reviews stating the same thing.

2) When I first tried to use it without an API token, it did not find any songs I tried. I then opened Settings and saw a field for an API token and the words "API token, paste it below" and thought that it must not work without an API token. I signed up for the API token (not knowing the API is a separate product) and after creating an account the dashboard shows that the user is on a 2-week Free Trial. I thought this applied to the extension, not the API.

3) There is a link on the main extension page to a Privacy Policy which differed from the one I read on the API dashboard, which further contributed to my impression that it is a paid extension, as I was unaware they are two separate products.

Now that I have read the Developer response, when I go to Settings, I can clearly see that it reads "If you're subscribed to the AudD® Music recognition API and have an API token, paste it below." I didn't notice this at first and thought the API token was required.

I have tried it and you can indeed use the extension to find songs without any API token. I gave the extension four stars instead of five only because the AHA extension is still better at actual song recognition. Thanks for the response developer! My apologies for assuming the worst in my original review.

Music recognition works pretty well, but I think the widget could use some UI improvements. Like managing individual songs from the history (not just clear the entire list) and also a way to just view the list even if current tab is still playing music. Also synchronizing listening history across different devices would be great.

Good but Some Time it dont found music

Работает :))

Works, but doesn't recognize audio playing on soundcloud and mixcloud (these are the main reason I use an identifier). Any chance of an update including these sites?

Really good addon, recognizes musics really well, but unfortunatly doesn't work on discord website