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 650555 - [aacparse] AAC profiles needed in caps
[aacparse] AAC profiles needed in caps
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
git master
Other Linux
: Normal normal
: 0.10.31
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on: 650594 650595 650596
Reported: 2011-05-19 08:56 UTC by Christian Fredrik Kalager Schaller
Modified: 2011-10-17 10:18 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Christian Fredrik Kalager Schaller 2011-05-19 08:56:51 UTC
We been talking for some time of adding the codec profiles to caps,
one of the main codecs needing this, which I would like to see added so I can support it in Transmageddon is AAC.

Currently I use the .prs files which looks like this:

_meta/comment=Low Complexity Profile

[Profile Main]
_meta/comment=Main Profile

[Profile Sample Rate Scalable]
_meta/comment=Sample Rate Scalable Profile

[Profile Long Term Prediction]
_meta/comment=Long Term Prediction Profile

But it would be better if Low Complexity, Main Profile, Sample Rate Scalable and Long Term Predition was added to the caps instead.
Comment 1 Sebastian Dröge (slomo) 2011-05-19 09:26:04 UTC
This would be needed in aacparse then and maybe in voaacenc and faac, right? Could you open new bugs for the encoders?
Comment 2 Christian Fredrik Kalager Schaller 2011-05-19 14:54:11 UTC
I probably filed this against the wrong module, I don't think the parser needs anything, just the encoders. Filed one for the FAAC plugin already.
Comment 3 Christian Fredrik Kalager Schaller 2011-05-19 15:11:27 UTC
added bugs for vdpau and ffmpeg plugins. I guess libva might soon pop up too.
Comment 4 Christian Fredrik Kalager Schaller 2011-10-17 10:18:45 UTC
This was actually fixed some time ago, closing.