Beoordelingen voor AudD® Muziekherkenning
AudD® Muziekherkenning door AudD, LLC
152 beoordelingen
- Waardering: 1 van 5door AziSlays, 3 maanden geledentried it twice. somehow it not only fails to find any music but also mute everything on the browser until I removed the application.
- Waardering: 5 van 5door jackyzy823, 3 maanden geleden
- Waardering: 3 van 5door Samg381, 3 maanden geledenI have two complaints with this plugin. The first issue is with respect to the pricing and API configuration- the setup of which is somewhat convoluted for most users, and there is no free tier, similar to Shazam, and it is unclear what benefit the API key brings, or when it is active / actively assisting recognition, or disabled or invalid. My second issue relates to the muting issue, where your browser tab stops producing audio when the recognition button is pressed. This probably has something to do with the way this app handles audio pipelines in the browser, but it is annoying nonetheless. Other than that, this plugin works mostly well, and I appreciate the developers for maintaining it.
- Waardering: 2 van 5door 𝘽. 𝙁𝙧𝙚𝙣𝙠𝙮, 3 maanden geledenWorks really well, Recently there is a bug where it mutes the tab's audio when searching and has to reload to get back audio.
- Waardering: 1 van 5door Nodus, 3 maanden geleden
- Waardering: 1 van 5door Firefox-gebruiker 17822790, 3 maanden geleden
- Waardering: 1 van 5door Firefox-gebruiker 13331269, 3 maanden geledenEven after the last update there is still problem in many sites. Now add-on doens't give result or mutes site and a refresh of the site is required/ For example: www.kusc.org, strummerradio.com, jazz.org
- Waardering: 3 van 5door NicCrimson, 3 maanden geledenWorks really well, Recently there is a bug where it mutes the tab's audio when searching and has to reload to get back audio. Also can't use because of 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." - Waardering: 1 van 5door IndiePat, 3 maanden geleden"Requires" very suspicious optional permissions it will prompt you for such as accessing data for all websites. It works perfectly fine without the permission so I worry it is selling information.
Antwoord van ontwikkelaar
3 maanden geleden geplaatstYou can find the extension's source code at https://github.com/AudDMusic/firefox-extension.
On many streaming websites, the audio source is in an iframe/embedded content, which the extension can't access to record audio without that permission.
The only information the extension sends us is information about the current tab when the add-on is opened and the corresponding recorded audio.
We do not sell any user information. - Waardering: 5 van 5door GODIE, 3 maanden geleden
- Waardering: 2 van 5door Mijehake, 3 maanden geledenMutes audio in the browser in which you are trying to record for recognition, have to reload page for this..
Antwoord van ontwikkelaar
3 maanden geleden geplaatstYou don't need to have an API token to use the extension. Apologies if the interface is not clear on that. The field to provide an API token is only for people who otherwise have an API account and, e.g., want to use the extension for work purposes. If you don't have one, you can leave the field empty and use the extension completely for free. - Waardering: 2 van 5door umadkek, 3 maanden geleden
- Waardering: 3 van 5door AndyArtistics, 3 maanden geledenThis worked completely fine, and technically still does, but now whenever I use it completely cuts the audio so i can't hear anything until i disable and reload a tab
- Waardering: 1 van 5door Dimibyte, 4 maanden geledenНе работает. На твиче нужен токен, но они дискриминируют живущих в РФ
Antwoord van ontwikkelaar
4 maanden geleden geplaatstWe don’t provide our services in Russia due to the sanctions imposed on Russia and the Russian government’s war crimes. - Waardering: 1 van 5door Firefox-gebruiker 18767572, 4 maanden geledengood extension but stops working randomly after getting 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" - Waardering: 1 van 5door DanologyUK, 4 maanden geleden
- Waardering: 5 van 5door Firefox-gebruiker 18727640, 4 maanden geledenI have used it only on YouTube and it managed to find all the songs so far, even those that were overlapped with someone's voice or other sound effects. Will change my review if enshittification happens.
- Waardering: 4 van 5door william, 5 maanden geledenWorked 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?
edit 2/23/2025: it somehow started working again I guess? the audio mutes when I activate the extension but it actually recognized some of the song I played. Antwoord van ontwikkelaar
4 maanden geleden geplaatstThere should not be any adware. Our add-on is fully open-source, not minified/obfuscated, and you can look at the source code to check for anything shady. We'd be extremely surprised if the extension is related to any ads.- Waardering: 2 van 5door Mikaïl, 5 maanden geledenDidn't work 20% of the time.
Didn't give me the right song 50% of the time.
And gave me songs that didn't exist 30% of the time.
Two stars because it at least worked once. - Waardering: 5 van 5door mooney, 5 maanden geleden
- Waardering: 4 van 5door PWN3D_, 5 maanden geledenI'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. - Waardering: 5 van 5door Dream, 6 maanden geleden