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 558250 - [audioconvert] Doesn't negotiate optimal caps
[audioconvert] Doesn't negotiate optimal caps
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 628938 (view as bug list)
Depends on:
Blocks: 628938
 
 
Reported: 2008-10-28 15:02 UTC by Sebastian Dröge (slomo)
Modified: 2011-05-19 08:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastian Dröge (slomo) 2008-10-28 15:02:08 UTC
Hi,
audioconvert sometimes doesn't negotiate the optimal caps:

gst-launch-0.10 -v audiotestsrc num-buffers=1 ! audioconvert ! "audio/x-raw-int,endianness=little_endian,width=16,depth=16" ! audioconvert ! "audio/x-raw-int,endianness=big_endian,width=(int){32,24,16,8}" ! fakesink silent=true


This example creates width=32 at the sink while width=16 would be better and without any loss.

audioconvert should prefer (if just endianness differs) the same format as the input or at least the format with the least increase of size. Same goes for other conversions where audioconvert can even increase the depth although this is not necessary.
Comment 1 Sebastian Dröge (slomo) 2008-10-28 15:05:44 UTC
(In reply to comment #0)
> Same goes for
> other conversions where audioconvert can even increase the depth although this
> is not necessary.

The increase in depth happens if the downstream caps are like "audio/x-raw-int,width=32,depth={24,32};audio/x-raw-int,width=16,depth=16" in the above example. width=32 and depth=24 is chosen then.
Comment 2 Olivier Crête 2010-09-17 15:57:23 UTC
*** Bug 628938 has been marked as a duplicate of this bug. ***
Comment 3 Sebastian Dröge (slomo) 2011-05-19 08:58:05 UTC
This works as expected now in 0.10 and 0.11, not sure when and how this was fixed.