https://bugs.kde.org/show_bug.cgi?id=506771
--- Comment #2 from [email protected] --- Thank you very much for the quick response. I must confess that I am a little disappointed by the difficulty of the task. In any case, adding a user action that calls an external tool like rmyrics3 or other might be a good idea. Perhaps you could implement it in the near future? Even if this is not the case, I reiterate my gratitude for your time and your response. Best regards. El 9/7/25 a las 18:27, Urs Fleisch escribió: > https://bugs.kde.org/show_bug.cgi?id=506771 > > --- Comment #1 from Urs Fleisch<[email protected]> --- > Thanks for the suggestion. Kid3 itself does not parse or render tags, it uses > 3rd party libraries to do that. For MP3 files, there are two options: id3lib > (using the Id3libMetadata plugin) and TagLib (using the TaglibMetadata > plugin). > id3lib has support for parsing Lyrics3v2. I have not used it because it offers > little control. As I can see from the source code, it would convert the > Lyrics3v2 data to COMM, USLT and SYLT ID3v2 frames. But it does not have a > function to remove such tags. Besides this, id3lib is no longer maintained > since many years, so it is disabled by default, and TagLib is used, because it > has more features, supports also ID3v2.4.0 (and many other formats) and is > still actively maintained. However, it does not support Lyrics3v2. Therefore, > it is not possible to nicely integrate Lyrics3v2 support into Kid3's UI using > the existing metadata plugins with the requested features, namely removing > such > tags. > > What would be possible is to add a user action which calls an external tool > such as the mentioned rmlyrics3 (https://github.com/Moonbase59/rmlyrics3). > Another idea would be using the QML API, it has script.readFile() and > script.writeFile(). However, there is probably no way to strip the Lyrics3v2 > data (bytes between LYRICSBEGIN and the ID3v1 tag) using QML. At least I could > not see a way to access the returned QByteArray as a JavaScript ArrayBuffer. > -- You are receiving this mail because: You are watching all bug changes.
