[FFmpeg-soc] vp8 de/packetizers
Josh Allmann
joshua.allmann at gmail.com
Wed Aug 11 09:47:18 CEST 2010
On 11 August 2010 00:46, Josh Allmann <joshua.allmann at gmail.com> wrote:
> On 4 August 2010 03:32, Luca Barbato <lu_zero at gentoo.org> wrote:
>> On 08/04/2010 09:59 AM, Martin Storsjö wrote:
>>> David, how large is this first data partition approximately? The frames
>>> are fragmented into RTP packets of around ~1450 bytes (usually) - so if
>>> we've got the first packet of a frame but not the rest, would we be better
>>> off returning this than just skipping it?
>>
>> Even better: is there a way to get this information?
>>
>> If is common for every packet/there is a known upper bound, we can pass
>> it through the sdp, or if not we could think about storing the value in
>> an extension header.
>>
>
> Not sure; I'd have to dig through the bitstream spec for this. Ronald,
> do you happen to know off the top of your head?
>
>> Still I guess we could extend the depacketizer interface to get all the
>> standard rtp information as well.
>>
>
> Attached patches should work against the updated VP8 rtp proposal*.
> Also pulled from latest trunk, so they also work with the Xiph stuff.
>
> The depacketizer now supports multiple VP8AUs in one packet but I
> haven't tested that codepath, because VP8AUs are not used by the
> packetizer.
>
> * https://groups.google.com/a/webmproject.org/group/webm-discuss/msg/eef6d312ac5c09c3?dmode=source&output=gplain
>
Attaching...
> Josh
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Add-RTP-packetization-of-VP8.patch
Type: text/x-patch
Size: 2769 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-soc/attachments/20100811/5f023d60/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Add-RTP-depacketization-of-VP8.patch
Type: text/x-patch
Size: 6416 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-soc/attachments/20100811/5f023d60/attachment-0001.bin>
More information about the FFmpeg-soc
mailing list