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

Michael Niedermayer michaelni
Mon Oct 12 09:08:44 CEST 2009


On Mon, Oct 12, 2009 at 08:59:42AM +0200, Luca Abeni wrote:
> Hi Michael,
>
> Michael Niedermayer wrote:
>> On Sat, Oct 10, 2009 at 05:56:00PM +0200, Luca Abeni wrote:
>>> On Sat, 2009-10-10 at 01:25 +0200, Michael Niedermayer wrote:
>>>> On Fri, Oct 09, 2009 at 09:34:58AM +0200, Luca Abeni wrote:
>>>> [...]
>>>>> However, I think your patch mixes too many changes together, and it 
>>>>> should
>>>>> be split in various parts. I am also not convinced that all the 
>>>>> modifications
>>>>> to avio.*, etc are really needed...
>>>> that was exactly my first thought, "why that?!" more precissely
>>> I think we need to find a way to pass parameters such as payload type
>>> (or session ID, etc) to the muxer (other muxers might have similar
>>> requirements: 


>>> for example, it would be nice to be able to set the video
>>> PID and the audio PID in the TS muxer, ...).
>>>
>>> Does such a mechanism already exists (I do not think that adding
>>> muxer-specific fields in AVFormatContext is a great idea)? If yes, can
>>> you point me to it?
>> muxers return packets depending on what AVDiscard (AVStream.discard) is 
>> set
>> to
>
> So, are you saying that AVDiscard can be used to set the payload type (or
> the session ID, etc...)?

rereading your mail, my reply makes no sense ...
what i meant to say was that AVDiscard can be used to select what to
return from the mpeg demuxer and that a PID field would be unneeded for
that, but you spoke of muxing. ive definitly read your mail too quickly

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

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Frequently ignored awnser#1 FFmpeg bugs should be sent to our bugtracker. User
questions about the command line tools should be sent to the ffmpeg-user ML.
And questions about how to use libav* should be sent to the libav-user ML.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20091012/70284443/attachment.pgp>



More information about the ffmpeg-devel mailing list