Opened 11 years ago

Closed 6 years ago

Last modified 5 years ago

#551 closed enhancement (invalid)

Enhancements for ffmpeg 0.6.3 when dealing with live H264 stream

Reported by: ilevin Owned by:
Priority: minor Component: avformat
Version: unspecified Keywords: h264 mov h263
Cc: Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no


Add abilities when writing to/reading from 3gp/mov format, and with no decoding/encoding (handling already encoding live stream from the net):

  1. To store/retreive "btrt" bitrate box
  2. Store/retreive "max NALU size" for H264 stream
  3. Read "udta" box on a stream level

Attachments (3)

isom.h.diff (1012 bytes ) - added by ilevin 11 years ago.
mov.c.diff (9.0 KB ) - added by ilevin 11 years ago.
movenc.c.diff (7.9 KB ) - added by ilevin 11 years ago.

Download all attachments as: .zip

Change History (9)

by ilevin, 11 years ago

Attachment: isom.h.diff added

by ilevin, 11 years ago

Attachment: mov.c.diff added

by ilevin, 11 years ago

Attachment: movenc.c.diff added

comment:1 by Carl Eugen Hoyos, 11 years ago

Please provide samples for "btrt" and "udta" and please explain why "max NALU size" is needed.

comment:2 by ilevin, 11 years ago

"max NALU size" was required in my project to be reported to the streamer, thus it will know whether transcoding is needed depending on remote end SDP negotiated abilities. For example, when streaming over network with MTU 1500, and negotiated mode 0 (disallowing fragmentation for H264 payload), transcoding is required if there is any NALU greater than 1468 in the stream. In my project, decision about switching transcoding on or off has to be taken upfront, thus knowing the maximum NALU size in all the packets in the stream is crucial.

"btrt" box serves similar purpose - we have restricted requirements on the high limits of the bit rate in the stream, and need to know maximum stream bit rate in a sliding window of a second upfront to decide whether trans-rating is required.
"udta" on a stream level may hold an SDP information in sub boxes, and we were required to utilize that info if it existed.

comment:3 by Elon Musk, 9 years ago

Patches sent to tracker are ignored.

comment:4 by Elon Musk, 6 years ago

Resolution: invalid
Status: newclosed

in reply to:  4 comment:5 by Carl Eugen Hoyos, 6 years ago

Keywords: h264 mov h263 added; H264 removed

Replying to richardpl:
I hope you'll find the ticket if such files ever appear...

Note: See TracTickets for help on using tickets.