[FFmpeg-devel] [PATCH] mp4a-latm rtp output & dynamic payload type from URL

Luca Abeni lucabe72
Thu Dec 17 16:22:29 CET 2009


Sergiy wrote:
> 2009/10/12 Luca Abeni <lucabe72 at email.it>:
>> Hi Michael,
>>> for muxing maybe AVStream.id could be usefull? but we can also add a new
>>> field if its insufficient
>>> Also if id is used it should be used consistently by demuxer & muxer of
>>> the same container format
>> Ok, thanks. I'll have a look at using AVStream.id for the payload type in
>> the RTP muxer
> Unfortunaly AVStream.id is always 0 when raw h263/amr streamed.
> But AVOutputStream.file_index can be used to increase rtp dynamic type.
> Here is simple patch that adds AVFormatContext.file_index and increase
> payload_type for every dynamic stream.

Thanks for your patch; I am currently testing the AVStream.id thing,
but I have no working solution yet (in case failure with the AVStream.id
approach, I was thinking about a solution derived from your previous patch:
but I want to test other options first).

I am wondering if it is possible to set the AVStream.id in ffmpeg.c, similarly
to what you do with oc->file_index.
If this fails and if Michael is fine with adding the file_index field, I am
ok with your patch.


More information about the ffmpeg-devel mailing list