FFMpeg处理RTMP流的总结

FFMpeg处理RTMP流有两种方式:
  一个是使用自带的RTMP代码功能；
  一个是使用第三方库librtmp；
下面就这两种方式的一些使用和差异做了个总结；

一、自带RTMP代码功能
FFmpeg自带的RTMP代码只支持RTMP协议，不支持rtmpt,rtmpe,rtmpte和rtmps协议；
命令行设置如下:
1. 将RTMP流原样保存成文件
# ./ffmpeg -i rtmp://192.168.1.11:1935/live/teststream -acodec copy -vcodec copy -f flv -y test.flv


2. 将RTMP流转码保存成文件
# ./ffmpeg -i rtmp://192.168.1.11:1935/live/teststream -acodec ... -vcodec ... -f mp4 -y test.mp4


3. 将RTMP流转码后再以RTMP流的方式推送到RTMP流服务器
# ./ffmpeg -i rtmp://192.168.1.11:1935/live/teststream -acodec ... -vcodec ... -f flv rtmp://10.2.11.111/live/newstream


NOTE:
FFMpeg自带RTMP代码只支持RTMP流格式如:
rtmp://server:port/app/stream_name (eg: rtmp://192.168.1.11:80/live/test)
不支持RTMP流格式如:
rtmp://192.168.1.11:80/live/app/test
要想支持这种格式的RTMP流，就需要更专业和强大的每三方库librtmp; 

二、第三方库librtmp
如何让FFMpeg链接该库可以参见文章:
http://blog.csdn.net/fireroll/article/details/8607955

这样FFMpeg就可以支持rtmp://, rtmpt://, rtmpe://, rtmpte://,以及 rtmps://协议了。
链接了librtmp的FFMpeg接受一个字符串的输入方式，
如："rtmp://server:port/app/playpath/stream_name live=1 playpath=xxx ..."
NOTE：引号是必须的;

1. 保存RTMP直播流原样保存成文件：
# ./ffmpeg -i "rtmp://pub1.guoshi.com/live/newcetv1 live=1" -vcodec copy -acodec copy -y cetv1.flv   

2. 将RTMP流转码后再以RTMP流的方式推送到RTMP流服务器
# ./ffmpeg -i "rtmp://192.168.1.11:1935/live/app/teststream live=1" -acodec ... -vcodec ... -f flv rtmp://10.2.11.111/live/newstream

3. 用ffplay播放RTMP直播流：
ffplay "rtmp://pub1.guoshi.com/live/newcetv1 live=1" 

4. 在使用FFMPEG类库进行编程的时候，也是一样的，
只需要将字符串传递给avformat_open_input()就行了，形如：
ffplay "rtmp://pub1.guoshi.com/live/newcetv1 live=1"  

char url[]="rtmp://live.hkstv.hk.lxdns.com/live/hks live=1";  
avformat_open_input(&pFormatCtx,url,NULL,&avdic)  

三、librtmp支持的参数：
http://rtmpdump.mplayerhq.hu/librtmp.3.html
1. NAME
librtmp RTMPDump Real-Time Messaging Protocol API

2. LIBRARY
RTMPDump RTMP (librtmp, -lrtmp)

3. SYNOPSIS
#include <librtmp/rtmp.h>

4. DESCRIPTION
The Real-Time Messaging Protocol (RTMP) is used for streaming multimedia content across a TCP/IP network. 
This API provides most client functions and a few server functions needed to support RTMP, RTMP tunneled in HTTP (RTMPT), 
encrypted RTMP (RTMPE), RTMP over SSL/TLS (RTMPS) and tunneled variants of these encrypted types (RTMPTE, RTMPTS). 
The basic RTMP specification has been published by Adobe but this API was reverse-engineered without use of the Adobe specification. 
As such, it may deviate from any published specifications but it usually duplicates the actual behavior of the original Adobe clients.
The RTMPDump software package includes a basic client utility program in rtmpdump(1), some sample servers, 
and a library used to provide programmatic access to the RTMP protocol. This man page gives an overview of the RTMP library routines. 
These routines are found in the -lrtmp library. Many other routines are also available, but they are not documented yet.


The basic interaction is as follows. A session handle is created using RTMP_Alloc() and initialized using RTMP_Init(). 
All session parameters are provided using RTMP_SetupURL(). The network connection is established using RTMP_Connect(), 
and then the RTMP session is established using RTMP_ConnectStream(). The stream is read using RTMP_Read(). 
A client can publish a stream by calling RTMP_EnableWrite() before the RTMP_Connect() call, 
and then using RTMP_Write() after the session is established. While a stream is playing it may be paused and unpaused 
using RTMP_Pause(). The stream playback position can be moved using RTMP_Seek(). When RTMP_Read() returns 0 bytes, 
the stream is complete and may be closed using RTMP_Close(). The session handle is freed using RTMP_Free().


All data is transferred using FLV format. The basic session requires an RTMP URL. The RTMP URL format is of the form
  rtmp[t][e|s]://hostname[:port][/app[/playpath]]


Plain rtmp, as well as tunneled and encrypted sessions are supported.
Additional options may be specified by appending space-separated key=value pairs to the URL. 
Special characters in values may need to be escaped to prevent misinterpretation by the option parser. 
The escape encoding uses a backslash followed by two hexadecimal digits representing the ASCII value of the character. 
E.g., spaces must be escaped as \20 and backslashes must be escaped as \5c.

5. OPTIONS
5.1 Network Parameters
These options define how to connect to the media server.
  socks=host:port

Use the specified SOCKS4 proxy.

5.2 Connection Parameters
These options define the content of the RTMP Connect request packet. 
If correct values are not provided, the media server will reject the connection attempt.
  app=name
      Name of application to connect to on the RTMP server. Overrides the app in the RTMP URL. 
      Sometimes the librtmp URL parser cannot determine the app name automatically, 
      so it must be given explicitly using this option.

  tcUrl=url
      URL of the target stream. Defaults to rtmp[t][e|s]://host[:port]/app.

  pageUrl=url
      URL of the web page in which the media was embedded. By default no value will be sent.

  swfUrl=url
      URL of the SWF player for the media. By default no value will be sent.

  flashVer=version
      Version of the Flash plugin used to run the SWF player. The default is "LNX 10,0,32,18".

  conn=type:data
      Append arbitrary AMF data to the Connect message. 
      The type must be B for Boolean, N for number, S for string, O for object, or Z for null. 
      For Booleans the data must be either 0 or 1 for FALSE or TRUE, respectively. 
      Likewise for Objects the data must be 0 or 1 to end or begin an object, respectively. 
      Data items in subobjects may be named, by prefixing the type with 'N' and specifying the name before the value, 
      e.g. NB:myFlag:1. This option may be used multiple times to construct arbitrary AMF sequences. E.g.

        conn=B:1 conn=S:authMe conn=O:1 conn=NN:code:1.23 conn=NS:flag:ok conn=O:0

5.3 Session Parameters
These options take effect after the Connect request has succeeded.
  playpath=path
     Overrides the playpath parsed from the RTMP URL. 
     Sometimes the rtmpdump URL parser cannot determine the correct playpath automatically, 
     so it must be given explicitly using this option.

  playlist=0|1
    If the value is 1 or TRUE, issue a set_playlist command before sending the play command. 
    The playlist will just contain the current playpath. If the value is 0 or FALSE, the set_playlist command will not be sent. 
    The default is FALSE.

  live=0|1
    Specify that the media is a live stream. No resuming or seeking in live streams is possible.

  subscribe=path
    Name of live stream to subscribe to. Defaults to playpath.

  start=num
    Start at num seconds into the stream. Not valid for live streams.

  stop=num
    Stop at num seconds into the stream.

  buffer=num
    Set buffer time to num milliseconds. The default is 30000.

  timeout=num
    Timeout the session after num seconds without receiving any data from the server. The default is 120.

5.4 Security Parameters
These options handle additional authentication requests from the server.
  token=key
    Key for SecureToken response, used if the server requires SecureToken authentication.

  jtv=JSON
    JSON token used by legacy Justin.tv servers. Invokes NetStream.Authenticate.UsherToken

  swfVfy=0|1
    If the value is 1 or TRUE, the SWF player is retrieved from the specified swfUrl for performing SWF Verification. 
    The SWF hash and size (used in the verification step) are computed automatically. 
    Also the SWF information is cached in a .swfinfo file in the user's home directory, 
    so that it doesn't need to be retrieved and recalculated every time. The .swfinfo file records the SWF URL, 
    the time it was fetched, the modification timestamp of the SWF file, its size, and its hash. 
    By default, the cached info will be used for 30 days before re-checking.

  swfAge=days
    Specify how many days to use the cached SWF info before re-checking. 
    Use 0 to always check the SWF URL. Note that if the check shows that the SWF file has the same modification timestamp as before, 
    it will not be retrieved again.

5.5 EXAMPLES
An example character string suitable for use with RTMP_SetupURL():
  "rtmp://flashserver:1935/ondemand/thefile swfUrl=http://flashserver/player.swf swfVfy=1"

 

《rtmp中flv和flv文件的区别》

rtmp中flv：

* 当format为0时，rtmp的header为12字节，其中3字节表示timestamp，3字节表示body size，即rtmp单个包的长度。

* 当format为1时，rtmp的header为8字节(没有4字节的stream id)，其中3字节表示delta timestamp，3字节表示body size，即rtmp单个包的长度。

* 当format为2时，rtmp的header为4字节(没有4字节的stream id，没有1字节的type id，没有3字节的body size)，只有1个字节的chunk basic header和3个个字节的delta timestamp。

* 当format为3时，只有1个字节的chunk basic header。

body体表示的是音频或者视频的数据。

flv文件：

* flv每个tag的头都是11字节，tag头中3字节表示data size，即每个音频或者视频包的长度。另外每个tag的结束会有4个字节表示tag 头 +tag体的长度

 

区别：

1. flv文件中每个tag的头长度固定，都是11字节，其中timestamp都是绝对值；另外在每个tag的结束会有4字节previous tag size表示该tag的头+tag的body的长度。

2. rtmp中flv数据，rtmp packet 头的长度不固定，可能的取值为12,8,4,1.当chunk basic header中format为0时，timestamp为绝对值；当chunk basic header中format为1,2时，timestamp为相对值。rtmp flv中body体的内容和flv文件中的body体内容相同，但是没有4字节的previous tag size。