You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
|
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: K. <kp...@gm...> - 2011-03-24 19:32:48
|
On Tue, 22 Mar 2011, Todd Fischer wrote: > Hi Lavruschenko, > The two main steps are to convert the gstd factory and pipeline files into header files, like: > dbus-binding-tool --mode=glib-client com.ridgerun.gstreamer.gstd.FactoryInterface.xml --output=gstd-factory-interface.h > dbus-binding-tool --mode=glib-client com.ridgerun.gstreamer.gstd.PipelineInterface.xml --output=gstd-pipeline-interface.h > and then connect to dbus to be able to send messages. Once that is done, you can use the functions in the generated header files to exchange messages. Thanks for answer i will try do that way, i hope dbus tutorial drive me right direction to write this extra code. -- WBR Oleksandr Lavruschenko |
|
From: Todd F. <tod...@ri...> - 2011-03-22 15:38:18
|
Hi Lavruschenko, We have mainly used gstd from vala or QT applications. I am currently working on a C application. I will post a simple program when I get back into the office next week. The two main steps are to convert the gstd factory and pipeline files into header files, like: dbus-binding-tool --mode=glib-client com.ridgerun.gstreamer.gstd.FactoryInterface.xml --output=gstd-factory-interface.h dbus-binding-tool --mode=glib-client com.ridgerun.gstreamer.gstd.PipelineInterface.xml --output=gstd-pipeline-interface.h and then connect to dbus to be able to send messages. Once that is done, you can use the functions in the generated header files to exchange messages. Todd On Mar 22, 2011, at 3:24 AM, Kpykcъ wrote: > > Are somewere available some example code in C for client application of > gstd. > I saw gst-client in distribution, but it written in vala, and generated C > code not really easy for reading. > > Thanks for answer. > > -- > WBR Lavruschenko Oleksandr > > ------------------------------------------------------------------------------ > Enable your software for Intel(R) Active Management Technology to meet the > growing manageability and security demands of your customers. Businesses > are taking advantage of Intel(R) vPro (TM) technology - will your software > be a part of the solution? Download the Intel(R) Manageability Checker > today! http://p.sf.net/sfu/intel-dev2devmar > _______________________________________________ > Gstd-devel mailing list > Gst...@li... > https://lists.sourceforge.net/lists/listinfo/gstd-devel |
|
From: K. <kp...@gm...> - 2011-03-22 09:50:31
|
Hi, seems some example pipelines dont work, for ex.: gst-client create "videotestsrc ! warptv ! ffmpegcolorspace ! ximagesink" gst-client create "audiotestsrc wave=8 ! audioecho delay=1000000 intensity = 0.2 feedback=1 ! audioconvert ! alsasink" 0)gstd% gst-client create "audiotestsrc wave=8 ! audioecho delay=1000000 intensity = 0.2 feedback=1 ! audioconvert ! alsasink" Parse single command interactive: Error: Creating pipeline:Launcher could not run (out of memory) 1)gstd% gst-client create "videotestsrc ! warptv ! ffmpegcolorspace ! ximagesink" Parse single command interactive: Error: Creating pipeline:Launcher could not run (out of memory) Looks like some bug. But i can run this pipeline: gstd% gst-client --session create "filesrc name=fsrc location=rudy.mp3 ! mp3parse ! ffdec_mp3 ! alsasink" I'm on debian testing and use stock gstreamer packages: gstd% dpkg -l |gr gst ii gstd 1.0-1 Gstd: Streaming audio-video server ii gstreamer-tools 0.10.32-4 Tools for use with GStreamer ii gstreamer0.10-alsa 0.10.30-1 GStreamer plugin for ALSA ii gstreamer0.10-ffmpeg 0.10.11-4 FFmpeg plugin for GStreamer ii gstreamer0.10-gnomevfs 0.10.30-1 GStreamer plugin for GnomeVFS ii gstreamer0.10-gnonlin 0.10.17-2 non-linear editing module for GStreamer ii gstreamer0.10-nice 0.1.0-2 ICE library (GStreamer plugin) ii gstreamer0.10-pitfdll 0.9.1.1+cvs20080215-1 GStreamer plugin for using MS Windows binary codecs ii gstreamer0.10-plugins-bad 0.10.19-2.1 GStreamer plugins from the "bad" set ii gstreamer0.10-plugins-base 0.10.30-1 GStreamer plugins from the "base" set ii gstreamer0.10-plugins-base-apps 0.10.30-1 GStreamer helper programs from the "base" set ii gstreamer0.10-plugins-good 0.10.24-1 GStreamer plugins from the "good" set ii gstreamer0.10-plugins-ugly 0.10.15-1 GStreamer plugins from the "ugly" set ii gstreamer0.10-sdl 0.10.19-2.1 GStreamer plugin for SDL output ii gstreamer0.10-tools 0.10.32-4 Tools for use with GStreamer ii gstreamer0.10-x 0.10.30-1 GStreamer plugins for X11 and Pango ii libgstfarsight0.10-0 0.0.26-1 Audio/Video communications framework: core library ii libgstreamer-interfaces-perl 0.06-1 Perl interface to the GStreamer Interfaces library ii libgstreamer-perl 0.15-2 Perl interface to the GStreamer media processing framework ii libgstreamer-plugins-base0.10-0 0.10.30-1 GStreamer libraries from the "base" set ii libgstreamer-plugins-base0.10-dev 0.10.30-1 GStreamer development files for libraries from the "base" set ii libgstreamer-plugins-gl0.10-0 0.10.2-1 GStreamer libraries from the "gl" set ii libgstreamer-plugins-gl0.10-dev 0.10.2-1 GStreamer development files for libraries from the "gl" set ii libgstreamer0.10-0 0.10.32-4 Core GStreamer libraries and elements ii libgstreamer0.10-dev 0.10.32-4 GStreamer core development files ii python-gst0.10 0.10.19-2 generic media-playing framework (Python bindings) Any advices? -- WBR Lavruschenko Oleksandr |
|
From: K. <kp...@gm...> - 2011-03-22 09:29:03
|
Are somewere available some example code in C for client application of gstd. I saw gst-client in distribution, but it written in vala, and generated C code not really easy for reading. Thanks for answer. -- WBR Lavruschenko Oleksandr |
|
From: Todd F. <tod...@ri...> - 2010-04-15 04:25:27
|
From: Justin Hartman <jus...@gm...> > > Date: April 14, 2010 8:13:16 PM CST > > To: gstd-devel <gst...@li...> > > Subject: [Gstd-devel] Information from a pipeline > > > Hi guys, Hi Justin, You get the honor of having the first post to gstd! > I followed the instructions on the gstd website to clone the repo & build gstd. I was up and running in a matter of minutes. Gstd is awesome! Glad it worked so well for you. Please let us know what information is missing or if you generate any content you think would be helpful pass it our way. Diego and Maria and others will help get the caps feature working. I am responding to comment on several fronts. Several of our customers struggled trying to incorporate the GStreamer calls into their applications. We came up with a simplified framework for one customer, then the gstd light came on. We have thought about gstd for nearly a year before being able to make it real. GStreamer Daemon was developed as part of a bigger deliverable for Texas Instruments. I want to thank TI for their support of the FOSS community. We are hopeful that more embedded products will use GStreamer when they see how easy it is. If you have it found it already, you can see a QT GUI using gstd at http://showoff.git.sourceforge.net/git/gitweb.cgi?p=showoff/showoff;a=summary We have thought a lot about Vala for a while as well. It was a bit risky to decide to use Vala, but the more we use it, the more amazed at how it makes us more successful. That said, Vala is still in development. I believe we found one Vala and/or binding defect and it might be you found another. We will work to get the feedback upstream to the Vala team as needed. gstd seemed like a good first use of Vala for GStreamer. > Thanks for the great work on this! I'm really excited to start using it. In many ways gstd is still in its infancy. Please provide any and all feedback - small or big. We have several use models in mind and would love to hear your ideas as well. I am also looking for a CGI implementation showing how to interact with gstd via a web interface. If you have anything to share along that front, pass it along. > Thanks, > > -Justin Todd |
|
From: Justin H. <jus...@gm...> - 2010-04-15 04:09:34
|
Wow, I can't believe I'm the first post... nice!
Bear in mind, all my comments come from a few hours of playing around with
this... so that says a couple things: (1) having never even heard of Vala
before, you can see that it was simple enough for me to add a method,
recompile, and get going in a short time, so kudos to Vala for that; on the
other hand (2) given my very little background with gstreamer, it's quite
possible I am recommending something that could already be done in a
different (better) way, hence my request for advice.
Yes, as you said, in some previous code when i was working with gstreamer
directly, without a Gnome/GObject binding, I was essentially trying to run
gst-launch in a child process, parse its standard out, send it signals, etc.
It worked, but it definitely wasn't pretty. GStreamer daemon is definitely a
better solution to this problem.
-Justin
On Wed, Apr 14, 2010 at 11:58 PM, Todd Fischer <tod...@ri...>wrote:
> From: Justin Hartman <jus...@gm...>
> >
> > Date: April 14, 2010 8:13:16 PM CST
> >
> > To: gstd-devel <gst...@li...>
> >
> > Subject: [Gstd-devel] Information from a pipeline
> >
> >
> > Hi guys,
>
> Hi Justin,
>
> You get the honor of having the first post to gstd!
>
>
> > I followed the instructions on the gstd website to clone the repo & build
> gstd. I was up and running in a matter of minutes. Gstd is awesome!
>
> Glad it worked so well for you. Please let us know what information is
> missing or if you generate any content you think would be helpful pass it
> our way.
>
> Diego and Maria and others will help get the caps feature working.
>
> I am responding to comment on several fronts. Several of our customers
> struggled trying to incorporate the GStreamer calls into their
> applications. We came up with a simplified framework for one customer, then
> the gstd light came on.
>
> We have thought about gstd for nearly a year before being able to make it
> real. GStreamer Daemon was developed as part of a bigger deliverable for
> Texas Instruments. I want to thank TI for their support of the FOSS
> community. We are hopeful that more embedded products will use GStreamer
> when they see how easy it is. If you have it found it already, you can see
> a QT GUI using gstd at
> http://showoff.git.sourceforge.net/git/gitweb.cgi?p=showoff/showoff;a=summary
>
> We have thought a lot about Vala for a while as well. It was a bit risky
> to decide to use Vala, but the more we use it, the more amazed at how it
> makes us more successful. That said, Vala is still in development. I
> believe we found one Vala and/or binding defect and it might be you found
> another. We will work to get the feedback upstream to the Vala team as
> needed. gstd seemed like a good first use of Vala for GStreamer.
>
>
> > Thanks for the great work on this! I'm really excited to start using it.
>
> In many ways gstd is still in its infancy. Please provide any and all
> feedback - small or big. We have several use models in mind and would love
> to hear your ideas as well.
>
> I am also looking for a CGI implementation showing how to interact with
> gstd via a web interface. If you have anything to share along that front,
> pass it along.
>
> > Thanks,
> >
> > -Justin
>
> Todd
>
>
|
|
From: Justin H. <jus...@gm...> - 2010-04-15 02:13:25
|
Hi guys,
I followed the instructions on the gstd website to clone the repo & build
gstd. I was up and running in a matter of minutes. Gstd is awesome!
When I was using gstreamer before, I would always call gst-launch with "-v",
because I needed to parse the verbose output to get some information from
the caps output for the various elements. I was hoping I would be able to
retrieve some of this information from gst-client, but it looks like I can
only retrieve element properties (but not element pad caps).
So next I installed the Vala compiler and changed gstd-pipeline.vala, adding
the following method:
/**
Gets the actual caps for a pad of an element in the pipeline.
@param element, whose property value wants to be known
@param pad, pad name
*/
public string ? PadGetActualCaps (string element,
string pad)
{
Element e;
Pad p;
Caps caps;
Gst.Pipeline pipe;
pipe = pipeline as Gst.Pipeline;
e = pipe.get_child_by_name (element) as Element;
if (e == null) {
if (debug)
stderr.printf ("Gstd: Element %s not found on pipeline",
element);
return null;
}
p = e.get_pad (pad) as Pad;
if (p == null) {
if (debug)
stderr.printf ("Gstd: Pad %s of element %s not found", pad,
element);
return null;
}
caps = p.caps as Caps;
if (caps == null) {
if (debug)
stderr.printf ("Gstd: Caps not found for pad %s of element %s",
pad, element);
return null;
}
return caps.to_string ();
}
I was able to compile this and run it; the only problem is I need to get at
GST_PAD_CAPS(pad) rather than gst_pad_get_caps(pad), which is what Vala
seems to generate. (The macro returns whatever caps have been set on the
pad, whereas the function returns the set of caps the pad is capable of. In
my case, the former returns the same string I get from gst-launch, whereas
the latter returns "ANY".)
Now for the questions:
(1) Does my approach seem correct?
(2) Is this of any value to the project? I would be happy to push changes,
but want to make sure I'm following your standards / patterns / practices.
(3) Do you know what (if any) Vala code I can use to get GST_PAD_CAPS
instead of gst_pad_get_caps? I wound up just modifying and building the
generated C code...
Thanks for the great work on this! I'm really excited to start using it.
Thanks,
-Justin
|