[gst-devel] NMM
Marco Lohse
mlohse at cs.uni-sb.de
Mon Nov 3 05:56:02 CET 2003
Hi,
sorry, but again:
I realized that you recently discussed NMM ( www.networkmultimedia.org )
on your mailing-list.
As I am one of the developers of NMM, I would like to correct some
details that were written on the list and that are technically wrong.
Please, understand me right, I do not want to start a discussion about
which architecture is better in the one or other way. I just want people
to read the facts about NMM. As you all are developers, I am sure you
will respect this.
Mathrick wrote:
> W liście z pon, 27-10-2003, godz. 14:20, Benjamin Otte pisze:
>
>>On Mon, 27 Oct 2003, Karl Schmitz wrote:
>>
>>
>>>Hi
>>>
>>>I read about the Network-Integrated Multimedia Middleware (NMM) and the Multimedia-Box in the german journal c't (issue 22), see www.networkmultimedia.org
>>>
>>
> [snip]
>
>>>Now I was wondering what you gstreamer guys think about NMM ? Why should I develop for gstreamer and not NMM ?
>>>
>>
[..]
>
> Looks like it is, and I didn't find any mentions of typefinding /
> autoplugging on their site, however there are examples of explicitly
> requesting plugins by filenames - not very promising.
>
>
The point here is: you can request plug-ins by node name (e.g.
"MPEGAudioDecodeNode"). But you do not have to.
You can request a plugin by specifying the name of the plugin, the type
of the plugin (e.g. "converter), a (subset) of the supported
input/output formats, or the supported interfaces. The nice thing: you
only need to specify what you need (e.g. only the interface "ITV" and
type "source" for some plugin for receiving TV), the registry will
provide a list of all "matching" plug-ins you can chose from.
And - of course, since NMM is networked - you can simply add a hostname
where you want this plug-in to run. Everything else is handled by NMM.
Marco.
More information about the gstreamer-devel
mailing list