Re: [Rhythmbox-devel] while we are talking id3tag writing



Jonathan Matthew wrote:
On Feb 10, 2008 7:48 AM, Matthew McGowan
<matthew joseph mcgowan gmail com> wrote:
Bug 424629 – handle multiple id3 tag sets better
http://bugzilla.gnome.org/show_bug.cgi?id=424629

This bug is a total pain!

Enough of a pain for you to consider helping fix it?

Short term could rb be designed to display the most recent id3 tag which
is most likely to be the preferred tag, or otherwise mimic the behavior
of banshee or ex falso which seem to display what i expect when it comes
to id3 tags.

Picking the right tag set to use is the right way to fix this, yes.

In the longer term, imho, rb should be good enough to try and remedy the
problem rather than just use the most recent id3tag. Similar to how
'missing files' or 'import errors' pops up there could be a category in
the sidepane for 'fix tags' or 'duplicate tags' or something, under
which are listed all the files that have multiple id3 instances, and
lets you review the versions, and provides a set of functions to choose
the preferred tag instance and optionally lets you strip out the other
unwanted tags.

I think this is a bad idea. No one cares that their files have
multiple tag sets, and no one wants to do anything manually to fix
them.
_______________________________________________
rhythmbox-devel mailing list
rhythmbox-devel gnome org
http://mail.gnome.org/mailman/listinfo/rhythmbox-devel

Enough of a pain for you to consider helping fix it?


Well i am mmcg069 at ec ... in the comments in the mentioned bug, but i don't really have anything to add at this point since i do not know how to find more information than is currently in the thread. In fact i posted a bug to bugzilla that was subsequently tagged as a duplicate, see http://bugzilla.gnome.org/show_bug.cgi?id=508655. I would be more than willing to provide example files et cetera or anything else developers need, but i need instruction about how to go about helping.

It seems to me that the bug is dormant and is currently listed as 'unconfirmed'. As mentioned its my major irritation with regard to rb atm. So posting to the list can be seen as me trying to raise awareness of this issue (perhaps this is my contribution to fixing the problem? :P).

Interestingly, there is mention of the issue at http://live.gnome.org/Rhythmbox/MetadataPlans. There they note:

   *    Read multiply-tagged files (e.g. with both id3 and ape tags)
     correctly
         o Don't want to just treat them as multiple values, as they'll
           either be the same, or one will be right and the other wrong
         o Could drop one set of tags (prefer id3 to ape or something -
           might be difficult to handle all cases properly)
         o Or return them as separate data sets (harder, probably not
           worth it)
   * Write tags for multiply-tagged files correctly
         o Strip out ape tags?
         o Or update all tag sets?
         o Do something with unnecessary containers (mp3-in-wav)?

So i am not quite sure as to why the bug continues to be tagged as unconfirmed when there is some level of recognition of this issue.

Picking the right tag set to use is the right way to fix this, yes.

No one cares that their files have
multiple tag sets, and no one wants to do anything manually to fix
them.


Yea, i agree.


Regards,
Matthew


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]