2018-11-19, 02:18
(2018-11-18, 22:52)gibxxi Wrote: Because Mike, people submit them. Don't ask me why, but they do. Much like the idiots who answer the item Q & A section on Amazon, just to tell the OP they don't know the answer to the proposed question.
People submit the lyrics embedded in your own music files? I don't understand how that is possible...
(2018-11-18, 22:52)gibxxi Wrote: The thing is, If those lyrics are available on a lyrics provision service / site, they will get downloaded. There's no way of stopping it, other than uninstalling CU-LRC Lyrics. For me, I'd rather not have to trawl through my music collection fixing this, as it's not going to fix it. Next time I play said track(s), with either CU-LRC Lyrics enabled, or use MiniLyrics (If MediaMonkey ever gets MP3 v2.4 tag writing support) I'll be back to square one.
Actually there are a few things you can do. First disable embedded lyrics:
Then you can disable "regular" lyrics:
Lastly, when the lyrics appear you can delete them:
(2018-11-18, 22:52)gibxxi Wrote: If your not interested in looking into it, just say so. I'd rather you said that, than come up with some convoluted excuse why it's somehow my fault. The issue I'm mainly reporting here is that special characters present in the lyrics file *might* be the cause of the above screenshot, and if that's the case, it will affect other lyrics files on tracks that aren't instrumentals equally as much. I focused on instrumentals, because I've seen more instances of special characters being present in instrumental tracks (acting like a title) that do have lyrics than those (ordinary) tracks which don't. This was when I was still using MediaMonkey + MiniLyrics. But since it doesn't seem to respect (for me) it's own setting not to modify tags (and thus revert them to v2.3 ID3 tags), I don't use it any longer.
Where exactly did I come up with some convoluted excuse why it's somehow your fault? You said you have a problem, one that, only you seem to be having. I gave suggestions and my opinion. Let me throw one more suggestion your way and say that this is likely an issue with the CU-LRC add-on cause it appears to be spitting out what looks like malformed code or something.
Also IMHO you're "kinda" being a dick right here.
