Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foobar2k, Tags and Android Phones (Read 4513 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foobar2k, Tags and Android Phones

Tagging m4a files with foobar (or mp3tag) is breaking compatibility with my Android OS phone, a myTouch 3g. I'm looking for a solution or workaround.

I use iTunes to rip my CDs but use foobar for most else. The files are all aac-encoded within an mp4 container with the .m4a extension. If I use foobar to edit a tag, either changing a field myself or applying replaygain, the phone will no longer read the tags. Every track shows as unknown artist, unknown album and the file name for the title.

To see what else might make or break the files I tried two other things. I installed MediaMonkey and used it to apply replaygain to a freshly ripped track. The phone recognized the tag. I used mp3tag to edit a field in a freshly ripped track and that also broke the phone's ability to read the tag, so mp3tag is doing the same thing.

I'm not really sure what causes the problem, but I'd love to figure it out and see if I can get my tracks working properly on the phone.




edit: more info - once the tags are changed by foobar or mp3tag, editing them in iTunes or MediaMonkey doesn't fix it.

edit2: stripping the tags completely with mp3tag and then retagging in MediaMonkey seems to work. But that'd be a time consuming project to strip and retag my whole collection.

foobar2k, Tags and Android Phones

Reply #1 –
Same here. In my expercience, some .m4a and mp3 id3v2 tags are not properly read by the android media player. This is clearly a problem with the android parser, and probably has nothing to do with the fb2k tagger. Nevertheless, it'd be useful to find a workaround. I've tried setting id3v2 writer compatibility mode to see if the mp3 tags would be properly parsed, but the problem still occurs. I'm kind of clueless regarding .m4a tags. Any suggestions? Is this a known issue?

foobar2k, Tags and Android Phones

Reply #2 –
Yup, the player is not able to read any tags in my collection.

Winamp for Android suffers from the same flag (it might use the same libs for all I know).

I found this report:
http://code.google.com/p/android/issues/detail?id=6808
Note comment 2.

Similar issue in mp3tag:
http://forums.mp3tag.de/index.php?showtopic=11403