Support and General Use > Audio Playback, Database and Playlists
Tagnavi_custom.config: searching by comment field
roolku:
--- Quote from: Llorean on August 10, 2007, 08:09:15 AM ---And what if someone wants to use parenthesis in their comment?
--- End quote ---
Then they should? Why would that be a problem?
--- Quote ---I'd rather it simply use the first comment, and people insure they know what's in their comments, rather than assuming parenthesis mean "skip this comment"
--- End quote ---
So far I haven't seen a single tagging program that can show more than one comment not to mention one that allows to specify the order in which they are saved to the binary? Could you point one out to me please?
Llorean:
Well, you said the first tag has (iTunNORM), and described that as an extra label. Did you mean something other than it having parenthesis in it as being the 'extra label' because I can't see how I could use (blah) in the beginning of a tag safely if you had it ignoring those tags.
And by "insure they know what's in their comments" they could perhaps only have one comment. I don't see how ignoring tags based on a non-standard methodology is a good idea. If there's no such thing as a tagging program that lets you order your comments (and I'd assume that there has to be at least one that lets you edit multiple comments if multiple comments is indeed valid, and I can only assume then that this one would write the comments in the order they're written) then wouldn't a proper solution be something like a plugin that lets you reorder your comments rather than arbitrarily ignoring a comment based on its contents?
roolku:
--- Quote from: Llorean on August 10, 2007, 10:03:51 AM ---Well, you said the first tag has (iTunNORM), and described that as an extra label. Did you mean something other than it having parenthesis in it as being the 'extra label' because I can't see how I could use (blah) in the beginning of a tag safely if you had it ignoring those tags.
--- End quote ---
No, the iTuneNORM text string is in the label field (also called shorttext) of the ID3 comment tag, which describes what the comment is about.
This shorttext is hardly ever used and again I don't know of any tagging programs that even expose it to the user for editing, however itunes uses it. It stores the normalisation information in a comment tag which is labeled iTuneNORM. Considering this is a problem for all users who use iTunes normalisation, comments and the database I think this is the solution that will cause the least confusion. I can't see any point in ever displaying the technical information from iTunesNORM in Rockbox.
--- Quote ---And by "insure they know what's in their comments" they could perhaps only have one comment.
--- End quote ---
Well the two programs I use for tagging will only expose one comment tag for editing and leave any existing other ones untouched.
--- Quote ---I don't see how ignoring tags based on a non-standard methodology is a good idea.
--- End quote ---
I don't think it is any more non-standard than ignoring the second tag like you suggested? I would even call it de-facto standard (as winamp's behaviour is often referred to like that).
--- Quote ---If there's no such thing as a tagging program that lets you order your comments (and I'd assume that there has to be at least one that lets you edit multiple comments if multiple comments is indeed valid, and I can only assume then that this one would write the comments in the order they're written) then wouldn't a proper solution be something like a plugin that lets you reorder your comments rather than arbitrarily ignoring a comment based on its contents?
--- End quote ---
No, I prefer a KISS approach that is current practice in other programs to anything that makes it harder for the user. Also it is not ignoring it based on the contents, but on the fact that it is labelled. If you can show me any evidence that the labelling mechanism is commonly used for user-added comments (rather than for tagging technical information), I will reconsider.
Llorean:
Well, part of the problem is the misunderstanding. You didn't clearly label "iTuneNORM" as being in another part of the tag. You referred to it as another label, but wrote it as part of the actual tag contents.
If it's not part of the tag contents, then I see no problem using it as a factor for ignoring tags.
But "Winamp does it" is not an excuse for why Rockbox should do something. Winamp is far from the only program out there. In this case, I assume the shorttext is meant for identifying the content-type of Comments, so ignoring ones that aren't simply "comments" as it were makes sense. But you still have to pick one if there are multiple that don't have shorttext, don't you?
The whole problem stems from it being unclear that (iTuneNORM) wasn't in the actual comment in your first post, which is why I made all those points about parenthesis.
polygonal:
--- Quote from: roolku on August 10, 2007, 09:57:04 AM ---So far I haven't seen a single tagging program that can show more than one comment not to mention one that allows to specify the order in which they are saved to the binary? Could you point one out to me please?
--- End quote ---
Mp3Tag shows the multiple comments under names like COMMENT ITUNESNORM, etc.; foobar2000 also shows multiple comments - if I remember correctly, by combining them. I don't think either of them allow you to specify the order, though, and I don't think fb2k writes multiple comments at all. My humble opinion is that ignoring the labeled comments in the ID3 screen are the way to go, since I personally don't know of any program that write labeled comments rather than unlabeled, and it should provide compatibility for the unfortunate victims of itunes' unasked-for comments.
Also maybe not parsing the labeled comments as well (or an option to do it)? Because I ran into problems with truncated tag info in long tags, and my problem is solved in most cases (I still have some unusually long tag that's my own fault) by removing the extra comments left by itunes.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version