Bug#699049: libfarstream-0.1-0: seems farstream not detecting audiocodecs

Simon McVittie smcv at debian.org
Tue Jan 29 09:51:04 UTC 2013

On 28/01/13 18:32, Vladimir Berezenko wrote:
> В сообщении от 28 января 2013 13:18:14 автор Simon McVittie написал:
>>> on powerpc seems that farstream is not seing any audiocodecs.
>> This is likely to be caused by <http://bugs.debian.org/674156>, for
>> which powerpc is one of the affected architectures. Please try upgrading
>> to libgstreamer0.10-0 (>= 0.10.36-1.1) from unstable - that version
>> should be available on powerpc now (or within a couple of days if your
>> Debian mirror is slow).
> Seems that not helped. After regeneration of codecs.audio.powerpc.cache stayed  
> of the same size - 12 bytes. There's no any MIME types listed there.
> Of course, i've rebooted after installing 0.10.36-1.1 from unstable.

Farstream and Gst experts: any ideas?

Vladimir, if you run "gst-inspect-0.10 speexenc", "gst-inspect-0.10
rtpspeexpay" on your powerpc, what do you get? Any warning messages? (If
everything is working, you should get some details of the plugins,
resembling <http://paste.debian.net/229996/>.)

If you run a Farstream application from a gnome-terminal or something,
do you get any warnings from that?

Does ~/.gstreamer-0.10/registry.*.bin list details of elements like
speexenc and rtpspeexpay in its binary data? If you remove both
codecs.audio.powerpc.cache and ~/.gstreamer-0.10/registry.*.bin,
then re-run a Farstream application, does that help?


More information about the pkg-gstreamer-maintainers mailing list