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

[Eugen Dedu <Eugen Dedu pu-pm univ-fcomte fr>]

On 22/04/14 15:16, Julien Puydt wrote:
> Le 21/04/2014 17:18, Eugen Dedu a écrit :
> > On 02/04/14 09:34, Julien Puydt wrote:
> > > Hi,
> > >
> > > here is a new version of the test code. Now the user interface is a
> > > series of buttons and two combo boxes to choose from a few devices, both
> > > for audio and video (no proper device detection yet -- the V4L2 choice
> > > might fail if you don't have such a device).
> > >
> > > The next step is to add more comments, then make it possible to stop the
> > > "call" and start a new one.
> >
> > I compiled your code: everything goes well.
> >
> > When executing, I noticed two things:
> > - video is slow: perhaps 2-4 images per second
>
> That is extremely surprising, as I have been working on a quite slow box
> where I should have known about performance issues...
>
> > - the other video window is always several coloured vertical lines
>
> 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:~$

> 2. gst-launch videotestsrc ! agingtv ! ximagesink

The same erroneous window, with the same output.

> > 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

--
Eugen