[gstreamer-bugs] [Bug 435120] cairosvgoverlay

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=435120
  GStreamer | gst-plugins-bad | git

--- Comment #20 from olivier.aubert at liris.cnrs.fr 2010-10-04 12:52:59 UTC ---
Hello

With no answer to previous comments, I would like to know the status of this
proposed element... To sum up the arguments, here is the current situation: the
rsvgoverlay element overlays SVG graphics over a video stream. The problem lies
in the specification of the SVG data.  There are 3 ways to do this:
1. the gstreamer-way, feeding the SVG data through a data-sink pad.
2. the less gstreamer-way but more convenient/concise in common cases:
specifying the location of the SVG file through a property.
3. the other less gstreamer-way, but more convenient also: specifying the
actual SVG data through a property.

Now, the first 2 methods cause no apparent problem, and the issue lies at point
3. If we compare the API to the textoverlay element one, there is similarity:
we can feed it data either through the text_sink pad or through a "text"
property. There is only 1 non-gstreamer way, since the common case it addresses
is the specification of some static text.
Now, back to the SVG overlay element, the nature of the SVG data is hybrid: on
the one hand, it is a graphical format, generally available in the form of
files (hence the filename property) ; on the other hand, it is text-based, and
can be specified on the command-line too, which can help rapid prototyping.
The dual nature of SVG data is IMO the justification of the presence of these 3
ways to specify data.

Until now, the only argument against this proposal has been "The API is too
complicated", which, without further explanations, does not really help me to
figure out the real issue.

I would really appreciate to have this solved before the next -bad release.
What would be the best way to find a solution?

-- 
Configure bugmail: https://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.