-
Notifications
You must be signed in to change notification settings - Fork 0
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
Expand api metadata #96
Conversation
+ also get ISRC and genre + show in front-end + fix duration formatting in front-end + only show important metadata in waveform + i18n fixes
Can you fix merge conflicts? |
What do you mean by "received only one metadata"? If you mean "only one set of metadata per song", you might be using an invalid AcoustID key (see what i mentioned in the README.md). The Shazam service will still only return one song, so only one set of metadata, AcoustID will return a lot of songs letting you choose between options. This also means that for songs that AcoustID couldn't identify, only one set of metadata is made available (as seen when splitting the hiphop test file using the "normal" preset - the third song can't be identified by AcoustID and thus calls shazam) If you mean only one song was identified at all, that's indeed an issue - I can't reproduce it though, for me all four songs are identified and three of them have several sets of metadata. I mostly tested using the old_pop testfile, which returns a lot of metadata options for each song. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have only added some styles to table to make it not look wierd in small screen.
My bad, have tried with other key and now I recieved more set of metadata for each segment |
issues/TODOs that should be added as a consequence of this: