Changes between Version 45 and Version 46 of Video_Users_Guide

Timestamp:

Apr 2, 2012 2:20:49 AM (12 years ago)

Author:

ming

Comment:

--

Video_Users_Guide

@@ -309 +309 @@
 Specify video picture dimension.
 
- a. For encoding direction, configured via {{{pjmedia_vid_codec_param.enc_fmt.vid.size}}}, e.g:
+ a. For encoding direction, configured via {{{pjmedia_vid_codec_param.enc_fmt.det.vid.size}}}, e.g:
     {{{
 /* Sending 1280 x 720 */
-param.enc_fmt.vid.size.w = 1280;
-param.enc_fmt.vid.size.h = 720;
+param.enc_fmt.det.vid.size.w = 1280;
+param.enc_fmt.det.vid.size.h = 720;
     }}}
     Note that there is a possibility that the value will be adjusted to follow remote capability. For example, if remote signals that maximum resolution supported is 640 x 480 and locally the encoding direction size is set to 1280 x 720, then 640 x 480 will be used.
  b. For decoding direction, two steps are needed:
-    1. {{{pjmedia_vid_codec_param.dec_fmt.vid.size}}} should be set to the highest value expected for incoming video size.
+    1. {{{pjmedia_vid_codec_param.dec_fmt.det.vid.size}}} should be set to the highest value expected for incoming video size.
     2. signalling to remote, configured via codec specific SDP format parameter (fmtp): {{{pjmedia_vid_codec_param.dec_fmtp}}}.
        - H263-1998, e.g:
@@ -324 +324 @@
 param.dec_fmtp.param[n].name = pj_str("CIF");
 /* The value actually specifies framerate, see framerate section below */
-param.dec_fmtp.param[n].value = pj_str("1");
+param.dec_fmtp.param[n].val = pj_str("1");
 /* 2nd preference: 176 x 144 (QCIF) */
 param.dec_fmtp.param[n+1].name = pj_str("QCIF");
 /* The value actually specifies framerate, see framerate section below */
-param.dec_fmtp.param[n+1].value = pj_str("1");
+param.dec_fmtp.param[n+1].val = pj_str("1");
          }}}
        - H264, the size is implicitly specified in H264 level (check the standard specification or [http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Levels this]) and on SDP, the H264 level is signalled via H264 SDP fmtp [http://tools.ietf.org/html/rfc6184#section-8.1 profile-level-id], e.g:
@@ -335 +335 @@
 param.dec_fmtp.param[n].name = pj_str("profile-level-id");
 /* Set the profile level to "1f", which means level 3.1 */
-param.dec_fmtp.param[n].value = pj_str("xxxx1f");
+param.dec_fmtp.param[n].val = pj_str("xxxx1f");
          }}}
 
@@ -342 +342 @@
 Specify number of frames processed per second.
 
- a. For encoding direction, configured via {{{pjmedia_vid_codec_param.enc_fmt.vid.fps}}}, e.g:
+ a. For encoding direction, configured via {{{pjmedia_vid_codec_param.enc_fmt.det.vid.fps}}}, e.g:
     {{{
 /* Sending @30fps */
-param.enc_fmt.vid.fps.num   = 30;
-param.enc_fmt.vid.fps.denum = 1;
+param.enc_fmt.det.vid.fps.num   = 30;
+param.enc_fmt.det.vid.fps.denum = 1;
     }}}
     Note that there is a possibility that the value will be adjusted to follow remote capability. For example, if remote signals that maximum framerate supported is 10fps and locally the encoding direction framerate is set to 30fps, then 10fps will be used.
  b. For decoding direction, two steps are needed:
-    1. {{{pjmedia_vid_codec_param.dec_fmt.vid.fps}}} should be set to the highest value expected for incoming video framerate. Note that it is even better if this is set to 1.5x (or more) of the expected incoming framerate because the renderer will use this setting for its clock and there is always possibility that remote clock runs a bit faster (clock drift), so setting it higher will avoid high latency issue caused by clock drift.
+    1. {{{pjmedia_vid_codec_param.dec_fmt.det.vid.fps}}} should be set to the highest value expected for incoming video framerate. Note that it is even better if this is set to 1.5x (or more) of the expected incoming framerate because the renderer will use this setting for its clock and there is always possibility that remote clock runs a bit faster (clock drift), so setting it higher will avoid high latency issue caused by clock drift.
     2. signalling to remote, configured via codec specific SDP format parameter (fmtp): {{{pjmedia_vid_codec_param.dec_fmtp}}}.
        - H263-1998, maximum framerate is specified per size/resolution basis, check [http://tools.ietf.org/html/rfc4629#section-8.1.1 here] for more info.
@@ -356 +356 @@
 /* 3000/(1.001*2) fps for CIF */
 param.dec_fmtp.param[m].name = pj_str("CIF");
-param.dec_fmtp.param[m].value = pj_str("2");
+param.dec_fmtp.param[m].val = pj_str("2");
 /* 3000/(1.001*1) fps for QCIF */
 param.dec_fmtp.param[n].name = pj_str("QCIF");
-param.dec_fmtp.param[n].value = pj_str("1");
+param.dec_fmtp.param[n].val = pj_str("1");
          }}}
        - H264, similar to size/resolution, the framerate is implicitly specified in H264 level (check the standard specification, or http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Levels) and the H264 level is signalled via H264 SDP fmtp {{{profile-level-id}}}, e.g:
@@ -365 +365 @@
 /* Can receive up to 1280×720 @30fps */
 param.dec_fmtp.param[n].name = pj_str("profile-level-id");
-param.dec_fmtp.param[n].value = pj_str("xxxx1f");
+param.dec_fmtp.param[n].val = pj_str("xxxx1f");
          }}}
 
@@ -372 +372 @@
 Specify bandwidth requirement for video payloads stream delivery.
 
-This is configurable via {{{pjmedia_vid_codec_param.enc_fmt.vid.avg_bps}}} and {{{pjmedia_vid_codec_param.enc_fmt.vid.max_bps}}}, e.g:
+This is configurable via {{{pjmedia_vid_codec_param.enc_fmt.det.vid.avg_bps}}} and {{{pjmedia_vid_codec_param.enc_fmt.det.vid.max_bps}}}, e.g:
 {{{
 /* Bitrate range preferred: 512-1024kbps */
-param.enc_fmt.vid.avg_bps = 512000;
-param.enc_fmt.vid.max_bps = 1024000;
+param.enc_fmt.det.vid.avg_bps = 512000;
+param.enc_fmt.det.vid.max_bps = 1024000;
 }}}
 
@@ -387 +387 @@
 /* H263 specific maximum bitrate 512kbps */
 param.dec_fmtp.param[n].name = pj_str("MaxBR");
-param.dec_fmtp.param[n].value = pj_str("5120"); /* = max_bps / 100 */
+param.dec_fmtp.param[n].val = pj_str("5120"); /* = max_bps / 100 */
    }}}