diff options
author | Martin Storsjö <martin@martin.st> | 2014-11-24 10:51:46 +0200 |
---|---|---|
committer | Martin Storsjö <martin@martin.st> | 2014-11-28 09:59:29 +0200 |
commit | 01eac895ab350027467ffbe7278740f89ae8be75 (patch) | |
tree | 32ad497019e61869ea0ebcc8c6742893fa467d7c /libavcodec/atrac3plus.c | |
parent | 44127b157e9f8acb837d4bb3a094f56b40da3ef5 (diff) | |
download | ffmpeg-01eac895ab350027467ffbe7278740f89ae8be75.tar.gz |
rtmpproto: Only prepend @setDataFrame for onMetaData and |RtmpSampleAccess
Currently, when streaming to an RTMP server, any time a packet of type
RTMP_PT_NOTIFY is encountered, the packet is prepended with @setDataFrame
before it gets sent to the server. This is incorrect; only packets for
onMetaData and |RtmpSampleAccess should invoke @setDataFrame on the RTMP
server. Specifically, the current bug manifests itself when trying to
stream onTextData or onCuePoint invocations.
This fix addresses that problem and ensures that the @setDataFrame is
only prepended for onMetaData and |RtmpSampleAccess.
Since data is fed to the rtmp_write function in smaller pieces (depending
on the calling IO buffer size), we can't generally assume that the
whole packet (or even the whole command string) is available at once,
therefore we can only check the command string once the full packet
has been transferred to us for sending.
Based on a patch by Jeffrey Wescott.
Signed-off-by: Martin Storsjö <martin@martin.st>
Diffstat (limited to 'libavcodec/atrac3plus.c')
0 files changed, 0 insertions, 0 deletions