After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 399289 - Make it possible to use gstreamer codecs as codecs
Make it possible to use gstreamer codecs as codecs
Status: RESOLVED WONTFIX
Product: ekiga
Classification: Applications
Component: general
GIT master
Other All
: Normal enhancement
: ---
Assigned To: Snark
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-22 07:54 UTC by Snark
Modified: 2008-09-23 05:44 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Snark 2007-01-22 07:54:52 UTC 
Once we have gstreamer usable for audio input/output and video input, the last thing we'll need to have a real gstreamer support is gstreamer codecs.
Comment 1 Snark 2007-03-30 05:09:30 UTC 
I'll need some opal-codec guru help here : I got the impression that a codec was mostly an implementation of :
    virtual int ConvertOne(int sample) const = 0;

which is as synchronous as one can get :-/

The gstreamer organisation is to push data at one end, and get data at the other end.
Comment 2 Matthias Schneider 2008-09-22 20:18:39 UTC 
In my opinion it does not make sense to rely on gstreamer codecs. Why? Because the main work of writing a codec plugin is dealing with all the capabilities that have to be negotiated between the two parties, a task that is not provided by gstreamer (Actually, I think most other software does not do this correctly, including commercial endpoints). Also, I am not 100% sure about the RTP encapsulation and deencapsulation of gstreamer. Just passing the frame to the encoder/decoder is rather trivial, you do not need gstreamer for that.
Comment 3 Snark 2008-09-23 05:44:41 UTC 
Ok, then let's close.