Skip to content

3.1
Compare
Choose a tag to compare
@zemoto zemoto released this 11 Oct 23:38
· 15 commits to main since this release
3.1
7ed7a15

Streamlined Custom API Key Workflow

This is the second month in a row the bundled API key has hit the monthly quota, so in order to make life easier for everybody, I've decided to slightly streamline the process of setting a custom API Key.

UI Changes

  • A new "API Key" section has been added to the UI
    • When there is no custom key, ghost text is displayed indicating that the default key bundled with the app is being used.
    • A provided key is used right away for the next detection, no need to restart.
    • If an invalid key is provided, the app will display an error indicating as much when trying to identity audio.
    • To go back to using the default key, simply empty out the contents of the text box.
    • If you already have a custom API key set, the value is still loaded from ShazamApiKey.json so all you have to do is move your old settings files next to the new exe and it will all continue to work.
    • A hyperlink is provided in-app that goes to https://github.com/zemoto/WhatAmIHearing?tab=readme-ov-file#rate-limiting which has instructions on how to get your own API key.
  • The "API quota reached" error is now shown in-UI rather than with a default message box. When this error is hit, the API Key section is expanded and the text box given focus.

Screenshots:



Update Reminder

To update and keep your settings, copy the config.json, history.json, and ShazamApiKey.json files from your old version folder to the new one.

Assets 3
Loading