Support and General Use > Audio Playback, Database and Playlists
Tagnavi_custom.config: searching by comment field
SoulSkorpion:
Sorry to bump this, but:
I notice that in the latest build, the comment field (among others) is now showing up in the ID3 info as "" and is still not being picked up by tagnavi. This probably is due to the tags being written by iTunes as I have AAC files that exhibit the same behaviour. Should I file a flyspray entry for this? Is this a bug, or a feature request on the basis of "Rockbox doesn't support iTunes tags yet"?
polygonal:
--- Quote from: SoulSkorpion on August 27, 2007, 06:53:25 AM ---Sorry to bump this, but:
I notice that in the latest build, the comment field (among others) is now showing up in the ID3 info as "<no info>" and is still not being picked up by tagnavi. This probably is due to the tags being written by iTunes as I have AAC files that exhibit the same behaviour. Should I file a flyspray entry for this? Is this a bug, or a feature request on the basis of "Rockbox doesn't support iTunes tags yet"?
--- End quote ---
As far as I know, there is no "ituns tags" except a non-standard compliant "Compilation" tag. Rockbox should be ID3v2 compliant, and itunes is actually known to be not. So I don't think there is any bug here since itunes is the trouble maker by being not standard compliant. But it may very well be a codepage problem if you experience weird character problems only for ID3v1. Try changing codepage and see if that solves the problem. As for the empty comment field, are you sure that you actually tagged the file? ID3v1 has limited space for comments, and they might be truncated without you knowing it.
SoulSkorpion:
--- Quote from: polygonal on August 27, 2007, 08:27:57 PM ---
--- Quote from: SoulSkorpion on August 27, 2007, 06:53:25 AM ---Sorry to bump this, but:
I notice that in the latest build, the comment field (among others) is now showing up in the ID3 info as "" and is still not being picked up by tagnavi. This probably is due to the tags being written by iTunes as I have AAC files that exhibit the same behaviour. Should I file a flyspray entry for this? Is this a bug, or a feature request on the basis of "Rockbox doesn't support iTunes tags yet"?
--- End quote ---
As far as I know, there is no "ituns tags" except a non-standard compliant "Compilation" tag. Rockbox should be ID3v2 compliant, and itunes is actually known to be not. So I don't think there is any bug here since itunes is the trouble maker by being not standard compliant. But it may very well be a codepage problem if you experience weird character problems only for ID3v1. Try changing codepage and see if that solves the problem. As for the empty comment field, are you sure that you actually tagged the file? ID3v1 has limited space for comments, and they might be truncated without you knowing it.
--- End quote ---
I'm not getting weird characters in these fields any more, I'm now getting "" (sorry, that didn't show up in my above post because the forum didn't like it for some reason. I've edited my post using a workaround to force it to display correctly).
I'm not using the ID3v1 fields for these files, I'm trying to use the ID3v2 ones. And yes, they are tagged. I haven't actually been consistent about whether these files have ID3v1 tags as well or not; I didn't think it mattered because I've set Rockbox to prioritise ID3v2.
Look, I accept that iTunes is the nonstandard thing here. This is still a pain, since its tagging interface is very good. Also, Winamp has no problem with iTunes tags, can can search by the contents of the comment field. iTunes might be nonstandard, but it's evidently nonstandard in a consistent way if Winamp knows how to handle it. I also understand if it's deemed a bad idea to build nonstandard functionality into Rockbox itself. Could this maybe be implemented as a plugin instead?
Well, if anyone can suggest some kind of automatic tag-cleaner-upperer, I'd be happy to use it to un-iTunes my tags...
roolku:
--- Quote from: SoulSkorpion on August 27, 2007, 06:53:25 AM ---Sorry to bump this, but:
I notice that in the latest build, the comment field (among others) is now showing up in the ID3 info as "" and is still not being picked up by tagnavi. This probably is due to the tags being written by iTunes as I have AAC files that exhibit the same behaviour. Should I file a flyspray entry for this? Is this a bug, or a feature request on the basis of "Rockbox doesn't support iTunes tags yet"?
--- End quote ---
Could you upload a short example mp3 file somewhere and post the link? Please let me know what info you expect from the comment field.
SoulSkorpion:
[edit]This forum keeps chewing up my angle brackets. It shows up fine in the preview, but not in my posts. Hang on while I edit my post with the workaround to force thme to be visible...[/edit]
File uploaded here.
This is how the file shows up on my Rockbox when I view the ID3 info:
[Title]
Egypt
[Artist]
Microprose
[Album]
Civilization
[Album Artist]
[Work]
[Discnum]
[Tracknum]
3
[Comment]
[Genre]
[Year]
[Length]
0:43
[Playlist]
3/3
[Bitrate]
128 kbps (VBR)
[Frequency]
44100 Hz
[Track Gain]
[Album Gain]
[Path]
/MUSIC/misc (games)/Civilization - Egypt - Microprose.mp3
This is how the comment field appears in Windows, when I right-click on it and go to "Properties":
--- Code: --- 0000014B 0000014B 0000044D 00000452 000076E4 000076E4 00005961 00004FDE 00000F8F 00000F8F
--- End code ---
This is how the comment field appears in iTunes, when I highlight it and go to "show info":
(this is how I'm expecting it to look in Rockbox).
Winamp tells me that apparently this file has both ID3v1 and ID3v2 tags. I've uploaded a screenshot of all the details it displays, here.
I didn't realise this file had ID3v1 tags as well; I'll go back and remove them later. Either way, neither comment field is showing up in Rockbox's ID3 tag viewer, and this file is being returned by by tagnavi search that searches for files that do not have in the comment field.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version