#551(avformat:new): Enhancements for ffmpeg 0.6.3 when dealing with live H264 stream
#551: Enhancements for ffmpeg 0.6.3 when dealing with live H264 stream ----------------------------------+--------------------------------------- Reporter: ilevin | Type: enhancement Status: new | Priority: minor Component: avformat | Version: unspecified Keywords: H264 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+--------------------------------------- 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 -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/551> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker
#551: Enhancements for ffmpeg 0.6.3 when dealing with live H264 stream -------------------------------------+------------------------------------ Reporter: ilevin | Owner: Type: enhancement | Status: new Priority: minor | Component: avformat Version: unspecified | Resolution: Keywords: H264 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by cehoyos): Please provide samples for "btrt" and "udta" and please explain why "max NALU size" is needed. -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/551#comment:1> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker
#551: Enhancements for ffmpeg 0.6.3 when dealing with live H264 stream -------------------------------------+------------------------------------ Reporter: ilevin | Owner: Type: enhancement | Status: new Priority: minor | Component: avformat Version: unspecified | Resolution: Keywords: H264 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by ilevin): "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. -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/551#comment:2> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker
#551: Enhancements for ffmpeg 0.6.3 when dealing with live H264 stream -------------------------------------+------------------------------------ Reporter: ilevin | Owner: Type: enhancement | Status: new Priority: minor | Component: avformat Version: unspecified | Resolution: Keywords: H264 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by richardpl): Patches sent to tracker are ignored. -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/551#comment:3> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker
participants (1)
-
FFmpeg