KDE 4 Multimedia: The Answer
rbultje at ronald.bitfreak.net
Mon Feb 23 16:29:24 GMT 2004
On Mon, 23 Feb 2004, Gioele Barabucci wrote:
> We will surely need to patch part of the code of the solution we choose.
> You know, using an infrastucture intesively you discover bugs, limitations
> and so on.
(and even better: you might actually fix them, too ;) ).
> - written in C, GLib based... I fear this combination.
There's Qt/C++ bindings by Tim Jansen (who should be familiar to you).
They're somewhere in KDE CVS.
> Look at this example stated "how to write a simple typefinder"
I want to make a short remark here: typefinders is not something you'll
write for yourself. The reason is that a typefinder is a type of plugin to
put parts of pipelines together. This can be used for playback purposes,
for example. However, GStreamer already includes a fairly powerful
typefinder (spider) by default. so creating your own is - in general - not
So why's the docs there? Just as a "FYI". :). There's lots of things in
there that you won't need, but they're good to know if you want to get
into GStreamer development. If you want to know some cool things, read the
first three chapters of the plugin writer's guide (4/5 are unfinished).
> - network trasparency?
We're not. We do have network elements, though. Using a sound server as
audio output, you'll be able to do all network-transparent things that
you'd want to do, though.
> - where are the benchmarks? how fat is it?
(Can't speak here...)
And before I forget: it'd be great if you'd use GStreamer plus the Qt/C++
bindings in KDE4!
More information about the kde-multimedia