Closed VocAddict closed 4 years ago
I thought it was my coding but the same code with the same parameters yielded two different results for azapi and I'm starting to wonder if the way the requests are phrased to the API is to blame for this because at this point, I'm not even sure any more.
Submitted a bug report for azapi so hopefully we get some news on that soon. For now I'll work on implementing the other APIs.
Implemented tswift which is the API for MetroLyrics fetching. Holding off from a PR until I deal with the other two.
Added the following:
Also decoupled dependency checks from the scripts - b376cd0d6bc3de738fd2af6c4d9980227d33cf64
I would add Piapro in a few days once I analyse how the site is written.
azapi 3.0.0 - https://github.com/adlez27/phonetic-songs/commit/50fc38b5ebcd0ac175b8abf4e54d79d9fc2b5f43
This fixes the issues that we had with it in terms of consistency, I'm still analysing piapro's site. This issue will be closed when that is done.
Piparo - 987f992e35f8f7bd578e06f03537b0a1e09d9387
Currently, it uses the API for AZLyrics but I've been thinking of adding on more (VocaDB is a must since you most likely aren't going to find Vocaloid songs on normal lyric sites) to give a the user a bit of a choice. I mentioned it in #5 but I may as well make an issue here to keep track of it further down the road. Of course, we'll have a recommended one based on our internal testing and maybe even eventually completely phase out the others if not needed.
APIs:
There also the collection of billboard songs aren't difficult to do, we may just have to decide just how far back we want to go in terms of collection. After that, it's just to automate fetcher to read the artist name and song title and retrieve the lyrics.