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 stopped working #430

Open
LouWeed opened this issue Nov 28, 2024 · 7 comments
Open

Audio features stopped working #430

LouWeed opened this issue Nov 28, 2024 · 7 comments

Comments

@LouWeed
Copy link

LouWeed commented Nov 28, 2024

Audio features does not work at all since yesterday (Nov 27th).
Maybe has something to do with this:

https://developer.spotify.com/blog/2024-11-27-changes-to-the-web-api

@Marekkon5
Copy link
Owner

yeah, unfortunate

@AndreaCan
Copy link

I confirm that it doesn't work anymore.
@Marekkon5 Is One tagger still maintained or is it dead?

@Marekkon5
Copy link
Owner

1T is still working, partially maintained (due to lack of time), however audio features are pretty much dead since esentially it was a Spotify wrapper, and Spotify decided to stop providing this data.

@AndreaCan
Copy link

audio features are pretty much dead since esentially it was a Spotify wrapper, and Spotify decided to stop providing this data.

This is a big disappointment, I really liked this feature as well as all your One tagger, it is a great application.
Do you think to make a new version of One tagger including the use of the new Spotify API?
There are websites (https://musicstax.com) that are working regularly even with the new API.
Thanks.

@Marekkon5
Copy link
Owner

The websites having that data are according to Spotify legacy apps, so they will continue to work. However they do not provide API, and I don't think they will like us scraping it. However feel free to link a website which provides such data as API and we can implement it.

@Vadogre
Copy link

Vadogre commented Dec 17, 2024

Its sucks it doesn’t work anymore, that was the thing made the tagged to be so useful. Is there any way to fix it or use other api? Thanks!

@j-editor80
Copy link

Hello everyone!

Believe me, those values like 'energy,' 'danceability,' etc., are very, very subjective. I recently created a similar Python script to retrieve these three values, and trust me, they are quite relative. After all, they're determined by an algorithm, not a human, and so far, there are artistic and sensory interpretations that (luckily) only we possess.

That's why it might not be so necessary. We always feel inclined to gather more information about tracks, thinking it will make us more efficient in cataloging them, but at least these particular values are extremely subjective. So, cheer up! It's an excellent program. Perhaps it would be good to remove that function.

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

5 participants