Bug 31320

Summary: Call example: using of StreamedMedia Channels
Product: Telepathy Reporter: Lutz Schoenemann <lutz.schoenemann>
Component: tp-qtAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED WONTFIX QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Dump of GstPipeline during a video call

Description Lutz Schoenemann 2010-11-02 06:36:48 UTC
The "call" example included in the Telepathy-Qt4 sources has some issues:
1. The incoming audio stream is not played back.
2. The incoming video stream display's a still image of the first frame
3. The outgoing video stream does not work entirely

I am using Telepathy-Qt4 0.3.4 on a openSUSE 11.2. The following libraries are installed:
- libtelepathy 0.3.3
- libtelepathy-farsight0 0.0.11
- libtelepathy-glib0 0.8.0
- farsight 0.1.28
- libfarsight2_0 0.0.20
- gstreamer-0_10-plugins-farsight 0.12.11
- libgstfarsight-0_10-0 0.0.16

I'm working on an instant messanger (Peregrine) and got audio streaming to work properly. The outgoing video stream is still not working. I dumped the running GStreamer pipeline into a dot-file. The sink pad from the FsRtpConference element that I connect the video stream to is only connected two more elements:
GstTee, GstValve
so nothing is done with the video streamed to the FsRtpConference element.
(See attachment. You can create a PNG file from that dot file by running:
#> dot -Tpng -o0.01.30.881504190-pipeline_dump.png 0.01.30.881504190-pipeline_dump.dot
)
Comment 1 Lutz Schoenemann 2010-11-02 06:38:56 UTC
Created attachment 39976 [details]
Dump of GstPipeline during a video call
Comment 2 Olli Salli 2010-11-05 01:18:18 UTC
We actually removed the Call example in 0.3.13 due to it being too broken and using a lot of deprecated StreamedMediaChannel API. We will only reinstate it once the new Call D-Bus API is finalized and we have high-level API for it.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.