[gst-devel] GSOC Ideas

[Stefan Kost]

Donny Viszneki schrieb:
> On Fri, Mar 6, 2009 at 4:04 AM, Donny Viszneki <donny.viszneki at gmail.com> wrote:
>> On Fri, Mar 6, 2009 at 3:25 AM, Edward Hervey <bilboed at gmail.com> wrote:
>>> You can then split up your pipeline into sub-pipelines accross several
>>> machines, have the clocks synchronized and the data flow happening
>>> through tcp+gdp.
>> But the point is to control the entire graph from a single process
>> using the regular GStreamer, and have GStreamer split up the work
>> based on work load!
> 
> And the networking-related elements would be transparent to the
> programmer unless they specifically asked to see them.
> 
> 
hi,

This is all not so easy, I've been thinking about this from tiem to time and
wonder if its worth the effort. Its certainly cool, but I just can't find enough
use-cases :)

In my thinking what you would need is:
- a proxy element that could proxy any existing element
  (could probably use gstreamer dataprotocol library).
- a gst_element_proxy_factory_make(type,name,host) to create remote elements
- a daemon that can create pipelines+elements on remote machines
- when adding the proxy to the pipeline, it would create the remote pipe as
needed and plug the real element there.
- smart ideas to avoid data going back and-forth

Also some non-essential
- discovery of daemons
- load-balancing (autoselect host)

Wanna try?

Stefan