Re: [Ekiga-devel-list] Using gstreamer for everything audio and video in ekiga

[Julien Puydt <jpuydt free fr>]

Hi,

Le 23/04/2014 18:28, Eugen Dedu a écrit :
> On 22/04/14 15:16, Julien Puydt wrote:

> > Can you try the following two commands:
> > 1. gst-launch videotestsrc ! ximagesink
>
> It shows several coloured vertical lines.  The output is:
> snoopy:~$ gst-launch-1.0 videotestsrc ! ximagesink
> Setting pipeline to PAUSED ...
> Pipeline is PREROLLING ...
> Pipeline is PREROLLED ...
> Setting pipeline to PLAYING ...
> New clock: GstSystemClock
> ERROR: from element /GstPipeline:pipeline0/GstXImageSink:ximagesink0:
> Output window was closed
> Additional debug info:
> ximagesink.c(686): gst_ximagesink_handle_xevents ():
> /GstPipeline:pipeline0/GstXImageSink:ximagesink0
> Execution ended after 0:00:04.347078564
> Setting pipeline to PAUSED ...
> Setting pipeline to READY ...
> Setting pipeline to NULL ...
> Freeing pipeline ...
> snoopy:~$

So it doesn't look at all like the first window shot in this page: 
http://wiki.oz9aec.net/index.php/Gstreamer_cheat_sheet
? Only the lower right corner should move.


> > 2. gst-launch videotestsrc ! agingtv ! ximagesink
>
> The same erroneous window, with the same output.

It should be only slightly the same, with an aging special effect so the 
streams can be discerned apart (as I write "apart" I wonder if it 
shouldn't have been "one another" or something like this...).

> > > Could you explain what is the ekiga architecture for video?  We have
> > > clutter thing, v4l2 plugin thing, X code thing in ekiga, now you propose
> > > gstreamer thing... how are they related?  What precisely will gstreamer
> > > code replace?
> >
> > Gstreamer should replace mostly everything... connecting on one hand to
> > opal for the network part and to Damien's clutter code for the video
> > display.
>
> So will it replace all ptlib plugins?  Currently there is:
> /usr/lib/ptlib-2.10.12/devices/videoinput/v4l2_pwplugin.so
> /usr/lib/ptlib-2.10.12/devices/sound/oss_pwplugin.so
> /usr/lib/ptlib-2.10.12/devices/sound/pulse_pwplugin.so
> /usr/lib/ptlib-2.10.12/devices/sound/alsa_pwplugin.so

Yes. And the same code should work regardless of the platform.

Snark