Bug 198238 - Genre tag in m4a files showing up as "unknown"
Summary: Genre tag in m4a files showing up as "unknown"
Status: RESOLVED FIXED
Alias: None
Product: taglib
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-29 04:59 UTC by Dave
Modified: 2009-09-10 00:15 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
taglib-extras file listing (1.75 KB, text/plain)
2009-06-29 13:58 UTC, Dave
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dave 2009-06-29 04:59:37 UTC
Version:           2.1 (using KDE 4.2.4)
OS:                Linux
Installed from:    Unlisted Binary Package

I'm in the process of converting all of my flac file into Apple Lossless (m4a) files so that they will be playable on my ipod (using ffmpeg).  What I'm noticing is that when I set the "Genre" tag in the resultant m4a with anything other than Amarok the track is reported as having a genre of "Unknown" by Amarok.

The file is created like so:
$ ffmpeg -i song.flac -acodec alac song.m4a

I then specify the genre tag like so:
$ m4tags -g "Soundtrack" song.m4a

I verify the tag:
$ mp4info song.m4a
mp4info version 1.6
song.m4a:
Track   Type    Info
1       audio   alac, 343.841 secs, 660 kbps, 44100 Hz
 Tool: Lavf52.31.0
 Genre: Soundtrack

But when I drag song.m4a to the Amarok playlist the genre is now "Unknown".  I see this behavior when I specify the genre under kid3 as well.

All of the other tags that I've tried specifing with mp4tags seem to be working.  Those include:  Title, Artist, Composer, Album, Track, and Year.

When I change the genre from within Amarok it sticks, and I can see the change in kid3 and mp4info.
Comment 1 Dave 2009-06-29 05:01:12 UTC
I should have added that I'm using Archlinux as my distribution.  Amarok is pulled from the kdemod repository.
Comment 2 Myriam Schweingruber 2009-06-29 08:38:43 UTC
You need to install taglib-extras for m4a support
Comment 3 Dave 2009-06-29 13:58:36 UTC
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?
Comment 4 Myriam Schweingruber 2009-06-29 14:24:29 UTC
Could somebody familiar with taglib have a look at this, please?
Comment 5 mutlu inek 2009-09-03 02:58:41 UTC
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.
Comment 6 Mikko C. 2009-09-03 07:51:58 UTC
0.1.3 is old, can you please try with taglib-extras 0.1.6 and see if it's still valid?
Comment 7 mutlu inek 2009-09-09 07:20:17 UTC
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.
Comment 8 Jeff Mitchell 2009-09-09 13:49:21 UTC
Please make some of the files available to me for testing.
Comment 9 mutlu inek 2009-09-09 17:38:55 UTC
Jeff, you should have received an email just about now.
Comment 10 Jeff Mitchell 2009-09-09 20:39:20 UTC
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).
Comment 11 Jeff Mitchell 2009-09-09 22:47:50 UTC
This is now fixed in upstream TagLib and in the just-released taglib-extras 0.1.7.
Comment 12 mutlu inek 2009-09-10 00:15:18 UTC
Wow! Thanks to you and the taglib developer for this fix! You rock!