[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 #8 from Alex Lancaster  2006-05-19 07:06 UTC -------
(In reply to comment #7)
> As far as anyone knows Rhythmbox is the only app depending on the broken
> behaviour. So the breakage is if a) you are running gst-plugins-ugly with the
> change, and b) you are running Rhythmbox without a version check, with
> tag-editing enabled, then tag changes to MP3s aren't written back into files.

My understanding was the plugin interface was supposed to be stable within a
given stable series of gstreamer (e.g. 0.8 and 0.10) and that new features
could be added with the series, but that changes would never be incompatible so
that any plugin version could be interchanged with any other plugin version.

The existing rhythmbox in CVS (and 0.9.4 and 0.9.4.1) checks for a minimum
version of id3mux, not for a specific version of id3mux.  

CVS rhythmbox should be updated to use the new interface for gst-plugins-ugly >
0.10.3 and use the old interface for 0.10.2 <= gst-plugins-ugly <= 0.10.3. 
That way rhythmbox CVS and >= 0.9.5 will always Do the Right Thing regardless
of the installed gst-plugins-ugly.  

Then the only potential problems will be with 0.9.4 and 0.9.4.1.  <= 0.9.3
isn't a problem because tag writing wasn't ever enabled with gstreamer 0.10.


-- 
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.