Version: (using KDE KDE 3.3.0) Installed from: SuSE RPMs OS: Linux Okay, maybe I'm old, but I like - no, love tracker music. I've collected quite a bit and plan to continue doing so. As amaroK is my audio player of choice, I appreciate that (because of aRts) I can easily add mods to my playlists - especially since kmod is no longer part of KDE (and wouldn't mix with other formats, anyway). However, the handling of mod files in amaroK is thoroughly unpleasant. With that in mind, these are the changes that, if anyone is interested or charitable enough to implement it, would resolve this: One, count mod (and s3m/xm/it) files in whatever part of the database you put the number of times a file is played. Two, include them in the collection database (though I probably have this one and the first reversed). Perhaps, since their info works differently than mp3/ogg tags, they could default to "Mod" as artist, album, genre, track and whatnot. Three, if it's not a big headache, it'd be really nice to be able to read the text most mod writers put in their mods. Perhaps it could be shown in a window brought forth with "View Meta Information..." as all that currently does with mods is more or less squat. I appreciate you reading this far (unless you skipped :P) and hope you can help me (and other tracker fans) out. I love amaroK and this last thing would make it absolutely perfect in my book.
I love tracker music too :) To answer your question: To get modules into the collection there would have to be mod support in TagLib, because amaroK uses this library for reading meta information. So I'm reassigning this report to TagLib.
Ah! Thank you. I didn't think about this. It'd be nice if it were KDE-wide.
Once this is implemented it will apply to (at least) JuK and amaroK. I'm not sure if Noatun uses TagLib, if so it would apply to Noatun as well.
It appears as this request has sat for a while. I would like to bring it up again as the Modular formats are still popular. There is meta data stored within most mod files (mod, s3m, mtm, xm, it, etc...). At the very least, meta data that should be read is: song title, sample text and message text (if available, not all module formats contain it). Note, most mods do not have an author field in the meta data, it's usually contained in the sample text. That said, it might be worth allowing users to add it as necessary (manually of course). Other meta data typically found in mod files: number of tracks, number of patterns, length in patterns, length in time, tempo (beats per minute). Note...many opensource programs support the reading of this metadata: Audacious, xmms, Schism Tracker (as well as most other trackers). This stuff is important to me because, like the original submitor, use AmaroK which can't support adding these songs to its collection library unless TagLib supports this data.
Well, just for full disclosure, I don't have any real interest in doing this myself, though I'd consider patches for such. Also, for the record, applications can add additional formats to TagLib; Amarok already does this with a few formats.
Amarok developer has expressed the same lack of interest in supporting the modular formats. That's where I turned to TagLib. In my opinion, from a development point of view, it would make sense to have the support in TagLib so that other applications (not just media players) can take advantage. I'm not a developer though. I'll see if I can scare up some interest to try to submit a patch for you.
*** This bug has been confirmed by popular vote. ***
I really would like to have this feature in TagLib. I wrote a Python based proof of concept tag reader (not TagLib based) for *.xm, *.s3m and *.it files (because these are the types of which I have files). These files have a title tag and the long names of the samples are usually abused as a multiline comment. So these two things can be mapped to the usual title and comment tags. Is there a howto/tutorial for writing (+compiling and installing) a basic TagLib plugin? I'm not sure if I would support reading of other attributes then the two (not sure if I understood the scarce and confusing info I found about them) and at least for a start it would be read-only.
Created attachment 60849 [details] s3m, it, xm proof of concept tag reader
I added tag reading/writing support for mod, it, s3m and xm files to taglib: https://github.com/panzi/taglib I'm hopeful this will get merged into taglib and thus later versions of amarok will support tags for these file formats. Whats supported: Reading: title, comment (from sample/instruments/pattern names), trackerName (faked for mod, it and s3m). Writing: title, trackerName (only for xm) Currently writing of "comments" is not supported. I might add that in future when I have time.
This should be closed now, right?
Yes, it's now in TagLib 1.8.