works fine here. Never had a need to change from the default search parameters. You do have local search first in the Search Order box, right?EDIT: And is Only Query the next source if no valid lyric found checked?

Edit2:

QUOTE

I tried a lot of combinations of artist and title search parameters, even something like "Depeche Mode" / "Enjoy the silence" for which I know, that there is a text-file in my lyrics directory named "Depeche Mode - Enjoy the silence.txt". -> Nothing!

What are you saying here? Have you changed search parameters away from titleformat syntax?

- upon searching for lyrics, be able to detect what I think of as "fake": lyrics that contain little or no real lyrics and contain "we haven't lyrics of this song", or "unfortunately, we", or the name of the database without any lyrics ("lyricsfly" is the biggest offender with this approach), and prevent the downloading of such fake lyrics.

Some fake lyrics are tricky in that they'll contain a few verses of real lyrics, and then stop and end with text like above. I'm sure there are other strings that people have encountered that indicate the same, but the ones above are the ones I've found.

Perhaps others can chime in with other similar indicators of fake lyrics.

Separate question: does title formatting work in the Lyric Saving tab, for the "use this tag..." entries? I'm trying to use what I used before with Lyrics2, what I'm trying doesn't work, and I can't figure out if it's me or if title formatting doesn't work in these spots.

I tried the default search parameters as well as some combinations with AND without titleformat fields (even tried $meta(...)).

I tried both query options and every of the sync-preferences, which should have no effect at all having local search as the only source.

I configured the local file search by using the Properties button:

Sub-directory search: enabled

Search depth:3

Lyrics path is simply G:\Lyrics for me.

Of course, I checked the presence of the specific lyric files in G:\Lyrics

But: Local file search is still not working for me.

EDIT:OK, this is definitely a BUG.After changing the custom SAVE path under "Lyric Saving" to "G:\Lyrics" the local search works, so it seems that the local file search doesn't interpret the custom SEARCH path but the SAVE path.

After the great improvement of usability i have started to become acquainted with lyrics_show component.

I have a question regarding the search parameters in lyrics search tab - not really a question but more the desire to get confirmation what i learned after some quick testing: The search parameters are not only related to online search but also to local file search?

I thought so because i changed the saved name of text file and nevertheless the lyrics was shown: so an intelligent type of search is proceeded. Would be an useful information to call the groupbox f.e. "Search parameters (online and local file search)". So i wouldn't have tested that behaviour.

The tag search doesn't know whether the lyrics are synced or not, it just searches the fields you've asked it to (entered in properties of Tag Search) and adds what it finds to a list. The list is then sorted according to your preferences, so it will display what you want (synced or unsynced). Saving is completely independent of loading lyrics (it doesn't care where you've saved it).

Edit: Doesn't the DSP page have them listed as available sources as well? (I'm not at my own computer so I can't check ).

Had a quick look: yes, they are called "available dsps" but the list left to it is called "active dsps".

(still don't understand yourr explanation. )

QUOTE

Edit: Hopefully explained a little better .

Ok, let me give you an example of what i don't understand:Let's say "only query next source if no valid lyrics are found" is enabled", the only active source is "tag search" and in properties of tag search in "read lyrics from the tags" in exactly this order is written: "Unsynced Lyrics; Lyrics". How can the synced lyrics be found when i've setted "only synced" in "search for this type of lyric"?

It will only query the next source if no valid lyric is found. So, it will search/load all lyrics from a particular source (e.g. Tag search) and then check if a valid lyric has been found. If one had been found, it will display this, otherwise it will continue searching.

sounds like the next preference then becomes important. All tag lyrics searched and then the one displayed is based on Search for this type of lyric.Name of this preference could be better, though I do not have a suggestion.

What you said is clear! But if i have setted "only synced" and in tag search both field Unsynced Lyrics and Lyrics are present how the component knows which of that both field contains synced lyrics? (I would test it on my own what happens in that case but i have no synced lyrics). Or better described: It finds as first source the unsnced lyrics but the option is "only snced" - how does the component know not to display them? By the content (the time expression)?

In the meantime i found a probably minor issue:I downloaded for a whole album (BDP - Sex and violence) the lyrics as textfiles. For some lyrics the "copy lyrics" command is available and for some not (command is greyed out). I can't see a difference between the files.

Maybe another minor issue: in "about current lyrics" for a local file the attribute "bad" was displayed so i thought that attribute was overtaken from the attribute in online search. Hence i apllied the lyrics search and loaded lyrics with a better atrribute and then saved the lyrics. After applying "about current lyrics" on local file the same attribute "bad" remained although i expecetd "medium".

Another issue in same area: what is "next" supposed to do if a lyric is displayed from an online search? display of next online db? In my case the fallback text will be shown with source: unknown in "about current lyrics" and on further next the same online db is shown again! (the other online db also have lyrics)If "next" is suposed to do nothing then the "next" should be greyed out and be unavailable. Or is it a bug because the next online db search isn't shown?

You did so much for usability and what i've described is the legacy of the old versions. But all these "unclear" points in its summary still make the component unfriendly because the new user is not able to recognize on first sight what is expected to happen. As i requested a few days ago it should be displayed in the ui-element itself what sourse is used and which sources are still available for next search so that no confusion happens.

Playing stream online, it'll get wrong result. For example, 977 music the hitz channel urls is "http://icecast3.977music.com/hitz", the lyrics name will be "977 Music Channel - .977 The Hitz Channel - 977MUSIC.COM - The #1 Hit Music Internet.lrc".

son, there is a social pattern to everything in the world. HydrogenAudio has many.

One is that it is preferred that threads do not get polluted with +1 posts. Another is a desire for posters to not quote previous posts needlessly. [obviously you missed the entire point of what I said]Another is to not quote more text than you add.