On Tue, 2011-11-08 at 14:08 -0800, Paul Stuart wrote:
> After digging into why I can not pipe the output of TIAudenc1 into the
> avimux element, I found that the internal implementation of TIAudenc1 is
> not packetizing the output into "codec_data" in the caps structure, per
> this little snippet:
>
> "Some data streams (like h264, mpeg4, aac), require the generation of
> the "codec_data" buffer to be passed off band (in the caps of the sink
> pad), in order to be properly muxed into container formats like mp4 or
> avi.",
> (from
http://processors.wiki.ti.com/index.php/GStreamer_Plug-in_2.x_Design)
>
>
> Since muxing encoded audio into an avi along with one's H.264 video is
> fundamental to making "talkies", I'm wondering if I have just selected
> the wrong element for audio encoding element or muxer on the DM36x? I
> can't be the first person needing to do this.
>
> Before I dive into changing TIAudenc1 to be "mux-able" I just want to
> make sure I'm not missing some easier option.
Check if they have some kind of "byte[-]stream" property. If yes, try
setting it to FALSE. Alternatively, put an appropriate parser between
the encoder and the container. If the parser is recent enough, it might
convert into the format/packetisation required.
From memory, the these elements cater for both kinds of input and output
though (with out-of-band codec_data in the caps or for bytestream
format).
Cheers
-Tim
_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
Locked
