Summary: | Genre tag in m4a files showing up as "unknown" | ||
---|---|---|---|
Product: | [Frameworks and Libraries] taglib | Reporter: | Dave <dave> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | mitchell, mutlu_inek |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | taglib-extras file listing |
Description
Dave
2009-06-29 04:59:37 UTC
I should have added that I'm using Archlinux as my distribution. Amarok is pulled from the kdemod repository. You need to install taglib-extras for m4a support Created attachment 34906 [details]
taglib-extras file listing
I have taglib-extras version 0.1.3 installed. I've attached the file listing for this package in the in case this is useful.
Would it be worth my time to acquire taglib-extras from svn?
Could somebody familiar with taglib have a look at this, please? Same problem here. I have a few m4a albums. I have edited their tags with EasyTag which shows them correctly. All these albums are categorized by Amarok as belonging to the "unknown" genre. If I open the "Edit Track Details" dialog in Amarok, the genre tag is shown as empty. I am also on Archlinux. Both taglib 1.5 and taglib-extras 0.1.3 are installed. Amarok is from git. 0.1.3 is old, can you please try with taglib-extras 0.1.6 and see if it's still valid? My system was just updated with taglib-extras 0.1.6. I recompiled Amarok and renamed a few .m4a files to force a rescan of them. Unfortunately, no change in behavior. Please make some of the files available to me for testing. Jeff, you should have received an email just about now. OK...Amarok doesn't show a genre tag, because TagLib doesn't give a genre when scanning the file. A hexdump of the file suggests that there is no string genre identifier and that easytag is possible doing a lookup of a number against a mapping, which may or may not actually be valid. I've forwarded the files to the appropriate person (TagLib maintainer) and will follow up with him. When TagLib supports it, it will either be pulled into a new release of taglib-extras or will simply be in TagLib proper in 1.6 (which will be released relatively soon). This is now fixed in upstream TagLib and in the just-released taglib-extras 0.1.7. Wow! Thanks to you and the taglib developer for this fix! You rock! |