GNOME Bugzilla – Bug 701384
rtsp-server needs to handle framed=true in addition to parsed=true
Last modified: 2014-02-25 22:28:36 UTC
Created attachment 245766 [details] [PATCH] [aacparse] add parsed=true in src caps The aacparse plugin does not set parse=true in srcpad caps. This results in problems using gst-rtsp-server. gst-rtsp-media-factory-uri autoplugs demuxers, decoders and parsers until the stream is "parsed", and then it chooses the right rtp payloader. An AAC audio stream always gets decoded to raw PCM audio, and then payloaded as MP4A-LATM. This way it is not possible to create an rtp stream with AAC audio. If the aacparse plugin sets "parsed=true" instead, it works as expected. See patch.
Created attachment 245768 [details] [review] [PATCH] aacparse: add parsed=true in src caps
It sounds more like rtsp-server should also look for the framed=true flag. We don't really have any good properties to marked the parsed state.
commit 3766914a184635896d05b2eda7d2addf86e86f1d Author: Tim-Philipp Müller <tim@centricular.net> Date: Thu Aug 22 18:39:59 2013 +0100 rtsp-media-factory-uri: check AAC properly for whether it's parsed or not For AAC we need to check for framed=true instead of parsed=true. https://bugzilla.gnome.org/show_bug.cgi?id=701384