Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Audio Features 403 - Except for this, it would be a perfect program! (Keep up the great work!) #434

Open
j-editor80 opened this issue Dec 28, 2024 · 4 comments

Comments

@j-editor80
Copy link

Dear team,

One Tagger seems like an excellent program to me. Very well-designed and developed with great taste. However, I would like to report this issue that, if resolved, would make it a perfect program!

I'm trying to use "audio features." To do so, I registered the application on Spotify, obtained my ID and secret key, and set up the Redirect URIs (http://127.0.0.1:36914/spotify). However, it is impossible to get past the 403 error.

It seems as if Spotify rejects the possibility of connecting to the API to fetch the data. Have you received similar reports from other users experiencing the same issue as me?

I hope there's a solution, as this is a fantastic program. Keep up the great work!

Thank you and best regards.

onetagger 403

@Marekkon5
Copy link
Owner

Sadly Spotify removed the API.
See here for details #430

@j-editor80
Copy link
Author

Sadly Spotify removed the API. See here for details #430

Hello Marekkon5! Do you have anything to do with the development of the software? It's excellent! Recently, I created a Python script to consume this type of data (danceability, energy, etc.), and believe me, the results are very subjective. To the point where today, they seem unnecessary to me due to their inaccuracy. After all, that information is provided by an algorithm and not a human, and we're talking about sensations. The best thing is, in any case, to catalog it yourself. Assign your own "dance" rating. That's the best, it never fails. Regards

@Marekkon5
Copy link
Owner

The data is indeed generated by an algorithm, however Spotify does it, not us, so we can't realistically improve it unless we make our own version

@j-editor80
Copy link
Author

The data is indeed generated by an algorithm, however Spotify does it, not us, so we can't realistically improve it unless we make our own version

It's exactly what I'm trying to say. Being created by an algorithm, they are unreal. I recommend not considering that information. It's irrelevant for cataloging, unlike the year of release, genre, etc. Perhaps it would be good to remove it from the new version, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants