RidgeRun/gstd

GStreamer Daemon for GStreamer 1.0

Opened this issue · 3 comments

Hi all,

I have started a wiki to capture the goals and proposed design for a rewrite of GStreamer Daemon that uses the GStreamer 1.0 API. You can find the wiki at https://github.com/RidgeRun/gstd/wiki/GStreamer-Daemon-for-GStreamer-1.0

The overall goal is to take what we learned from gstd-0.10 and get gstd-1.0 hosted at http://gstreamer.freedesktop.org/modules with gstd-1.0 included in future standard gst distributions.

Please add to the wiki page as you see fit. Since github wiki is so lame, you can add issues, concerns, suggestions, whatever at the bottom of the page if you don't feel comfortable changing the text directly.

Hi Todd,

I have following comments / suggestions for GStd 1.0:

  1. gstd for Android. Possible IPC on Android: D-Bus (not part of Android SDK; relying on it should be avoided), sockets (too low-level...) and "native" Android IPC - Binder. Supporting the last one is preferable. Architecturally: implement core part as a C library (libgstd?), to be interfaced via JNI with Android GstService written in Java?
  2. Allow more fine-grained access to internal GStreamer elements and interfaces (e.g. GstBus) of the pipeline. At least one use case - porting existing GStreamer applications to be distributed (i.e. move GStreamer library from application to gstd - to allow the app and the gstd to be run on different machines; more about this topic is available here: https://fosdem.org/2014/schedule/event/virtiaas23/ )

This is a bit off-topic, but if anyone would like to use gstd with gstreamer-1.x, https://github.com/dunkpa/gstd does the job. The changes aren't suitable for merging back as they stand because they break gstreamer-0.10 compatibility.

We have re-designed Gstd to have more fine-grained access control and to support different IPC mechanisms. Please checkout our Gstd for GStreamer 1.0.

Additionally, we are working on some documentation in our project wiki page.