[FFmpeg-cvslog] r22288 - trunk/libavcodec/avcodec.h
Wed Mar 10 18:59:10 CET 2010
On Wed, Mar 10, 2010 at 07:57:45AM +0100, Reimar D?ffinger wrote:
> Different values for audio and video codecs possible?
> But I also want to note that huge padding for H.264 will not
> just kill small packet audio codecs, it will also become
> quite ugly with high-compression, low-resolution H.264,
> and the codec-specific padding will not help there.
> Although if we measure the amount of data wasted per second,
> the problem with "small packet audio codecs" should not
> be so big, if it wasn't for things like AVI demuxer that
> creates tiny PCM packets.
Note that a possible (although very ugly) solution would be
replacing av_malloc by a completely custom allocator,
for large sizes simply doing a larger malloc with additional
padding, for small sizes taking it from a pool with appropriate
extra padding. Additional memory can be saved by (where available)
allocating with mmap and padding with read-only 0 pages.
Wouldn't even need an API or ABI change.
Though I don't like having the complexity of a custom allocator
More information about the ffmpeg-cvslog