[gstreamer-bugs] [Bug 339918] GstTagSetter merge-mode description unclear, and implementations inconsistent

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=339918
 GStreamer | gstreamer (core) | Ver: HEAD CVS





------- Comment #11 from Tim-Philipp Müller  2006-05-19 09:39 UTC -------
Alex - just so I understand this correctly - are we talking

 (a) breakage in practice here (ie. happening with rhythmbox
     as it is usually compiled/shipped by default), or

 (b) breakage in corner cases (ie. someone compiled rhythmbox
     himself with the still experimental --enable-foobar option), or

 (c) mostly principle?



Does the code in rhythmbox explicitly set the merge mode of id3mux to something
(REPLACE) that is documented - and was already documented back then - as doing
the exact opposite of what rhythmbox wants to do, with the documentation of
gst_tag_setter_set_merge_mode() explicitly describing KEEP mode to be what
rhythmbox wants to do?


Is there a released version of rhythmbox yet that uses id3v2mux? (viewcvs
didn't seem to feature anything id3v2mux-related)

Would it help to keep the old broken semantics for "id3mux" and only change it
for id3v2mux?


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.