-
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
New lyric source pack for ESLyric #115
Comments
Thanks!! I'll take a look when I have time. |
Hi ohyeah, That is all for now, cheers. -Tom |
updated. now you can download from the online fetcher. |
Thanks ohyeah, don't forget the lyric parser js files from the post above. |
Hi, I think the original parsers are barely ok. |
Hi ohyeah, here is a new ESLyric source pack 2: Contains 4 new lyric sources:
and here is the new minilyrics_v0.4 ( suppress error log when server is down ): Did test those a bit and all seems OK. -Tom |
@TT-ReBORN ok, added to online downloader. |
Thanks for the new scripts, but Metallum hasn't worked at all over here. Placed at the top of the searcher list, and using LSP3-foo_multisource as a reference, every song found at Metallum by LSP3 is not found there by the metallum.js searcher. Some examples of the unfound songs and their lyrics as linked at Metal Archives: Darkwell - Suspiria Reaper - 1943 Misery Loves Co. - 2 Seconds Kaunis Kuolematon - Hurskas Danzig - Until You Call on the Dark Had high hopes for this one and I hope it can be fixed. |
I can find all lyrics for all the songs you have listed via the metallum searcher script. If the artist, album and title are the same as on the website, it will find them. |
here is the last one ( deezer ) as a bonus. Tested it, but you need to add your own API key and cookie to make it work. deezer has synced and unsynced lyrics, so I have added the description "Mixed". -Tom |
I should have mentioned that the Metallum search failures were all done using ESLyric on radio streams, not files, which almost never include an ALBUM name in their metadata. I was able to modify the metallum.js in the new package myself by removing album name from the search expression and from the "if.." statement 2 lines below it. The "const album =.." line can also be removed if desired. Now I am getting plenty of hits from radio streams on Metal Archives! A zip containing my modified metallum.js is attached for anyone interested Just as a FYI I found that if the search done on the website returns hits from different releases from the band (EPs, etc) that contained the same song, some of the releases may not show the lyrics while others do. In these cases, the search produces results from the first album in the list only and does not "travel" the others, even if the first listed has no lyrics and the second listed does. I imagine accounting for this in a searcher script would be too complicated to worry about. Somehow, foo_multisource is able to do this. The other 3 new scripts work fne with radio streams as-is. THANK YOU TT-ReBORN! Off to give deezer a try now :) |
Yes, I have included the album meta data to improve search results accuracy. Did not account for radio streams though as I never use them with lyrics. ohyeah could implement a new callback that checks if current playback is streaming. Then we could add conditional statement to use or not use album meta in the search. just found out about Example: Also Can you please fix this first? After that, I will then send you lololyrics.js v0.2. -Tom |
I checked also, the |
@ESLyric, I have posted a video in the previous post that you can see. |
Yes, the 'Edit' field's initial values still are preprocessed by design(Most sources are suitable). When request manully, metadbs were override by the 'Edit' fileds. |
OK but can you disable/ignore this for It should only use the preprocess for meta.artist, meta.album, meta.title but not when using raw meta. -Tom |
The preprocess fileds are used as the initial values only when manual searchin, you can edit them. For example, if you changed the Title edit field to 'xxxx', the |
Yes I have understood this from the beginning, but why do you use the field preprocessing for So I ask again, can you only exclude/disable ESLyric Field processing for Thanks for understanding. -Tom |
When manully search, the So actually the initial value cause the 'issue'. As I said, Use the preprocess value as the initial values would be more conventient in most cases when search manully. If you cannot fetch the result, you should try different keywords any ways. |
Hi there people. Great to see more lyrics sources. Also some |
happens when MiniLyrics server is down. |
OK I get it now, this was so confusing ohyeah. Sorry :( , but you could have told me from the beginning to just check console.log when changing the title in the "Lyric Search" input field, took me long to figure it out... Anyways thanks for the help. I have uploaded the new improved lololyrics.js here #115 (comment) Thanks -Tom |
Error log gone. |
One more question. |
@TT-ReBORN Please issue a PR instead, thanks. |
An idea to filter out garbage lyrics would be to make an ESLyric blacklist filter feature where user can input these strings |
Hi ohyeah,
I have wrote some new ESLyric sources and refactored and fixed your original lyric sources scripts.
I will add them to my Georgia-ReBORN theme and hope you will also add them officially to your ESLyric source repo.
Here is the new ESLyric source pack:
eslyric_source_pack.zip
Installation:
Go to foobar's
Preferences
>Tools
>ESLyric
>Lyric Option
>Lyric Sources
At the top right corner click on
Get More...
>Get online script
> Download everythingGo to your
foobar2000\profile\eslyric-data\scripts\searcher
and replace all files from the eslyric_source_pack.zipAdded new sources:
Refactored:
All original script files have been refactored and cleaned:
Changed:
Added better name descriptions for the users that shows if the source has synced or unsynced lyrics
Fixed:
AZLyrics - fixed search query and its results when artist names start with "A" and "The".
In the old script the search results were not found.
I have tested all lyric sources and they should work properly but there is a note for you in the bandcamp.js:
To explain:
bandcamp search query only works if the artist name is the same as url subdomain.
But there are artist that do not have their exact bandname in the bandcamp subdomain.
Many bandcamp music files have their URL to their bandcamp site in either the
%comment%
,%label%
or%publisher%
.So if you could implement
meta.comment
,meta.label
,meta.publisher
we could use the embedded url to have better search results.It will search for the url in these tags via
getUrlFromTag(tag)
func and use this url instead. I think this would work, but it needs to be tested...You can also close this issue here #76, thanks!
Hope your doing fine.
-Tom
The text was updated successfully, but these errors were encountered: