AFT and MusicBrainz track identifiers

Amarok Blog

Friday, August 7. 2009

Posted by Jeff Mitchell in jefferai

Comments (2)
Trackbacks (0)

AFT and MusicBrainz track identifiers

A heads-up: Amarok File Tracking can now use MusicBrainz track identifiers for its embedded IDs. This means people that have used Picard to tag their files but not amarok_afttagger can still get some embedded AFT goodness! It also enables an interesting "mode" because it essentially enables song tracking vs. actual file tracking (which you may or may not want, depending on your particular needs).

Full details are here.

Trackbacks

Trackback specific URI for this entry

No Trackbacks

Comments

Display comments as (Linear | Threaded)

That wiki page mentions that some people may consider "song tracking" to be a feature, but I would go farther. It would be nice to see a music player that explicitly recognizes songs for which multiple formats exist in the library. For example, if your library contains the same song encoded as both MP3 and OGG Vorbis, Amarok should play the better quality one (higher bitrate?) when you play that song, but when you transfer that song to a portable music player, it should use the MP3 version for players that don't support OGG, and vice versa, without any transcoding.

#1 Ryan on 2009-08-08 13:10 (Reply)

Your request makes an assumption that everyone would always actually want that behavior. (It also assumes that we can know ahead of time what portable music players support what formats, which is not something that can be reliably determined from many/most non-iPod players.)

While it is easily possible that we could do the first part, there would have to be an unobtrusive and discoverable way to toggle the necessary options.

#1.1 jefferai on 2009-08-08 15:41 (Reply)

Add Comment

Name
Email
Homepage
In reply to
Comment	Enclosing asterisks marks text as bold (word), underscore are made via _word_. Standard emoticons like :-) and ;-) are converted to images. To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly. Enter the string from the spam-prevention image above:
	Remember Information? Subscribe to this entry