Changes between Version 2 and Version 4 of Ticket #1888


Ignore:
Timestamp:
Oct 6, 2015 7:59:46 AM (9 years ago)
Author:
ming
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1888

    • Property Status changed from new to closed
    • Property Resolution changed from to fixed

  • Ticket #1888 – Description

    v2 v4  
    1 = How to build WebRTC = 
     1[[Image()]]= How to build WebRTC = 
    22== Mac == 
    33Refer to !WebRtc development guide [http://www.webrtc.org/native-code/development here]. 
    … …  
    2222}}} 
    2323 
    24 == Android (ARM) ==  
     24== Android ==  
    2525Android development is only supported on Linux (reference [http://www.webrtc.org/native-code/android here]), so if you use other platforms, you need to set up a Linux virtual machine. 
    2626 
    … …  
    6161To use !WebRtc AEC, specify the value {{{PJMEDIA_ECHO_WEBRTC}}} in {{{pjsua_media_config.ec_options}}} ({{{MediaConfig.ecOptions}}} for PJSUA2), and specify the delay estimate for sound card and system buffers in {{{pjsua_media_config.ec_tail_len}}} ({{{MediaConfig.ecTailLen}}} for PJSUA2). !WebRtc AEC's performance is very dependent on this delay calculation. A poor estimate, even by as little as 40ms, may affect the echo cancellation results greatly. Our !WebRtc wrapper has enabled the delay agnostic feature, which will adjust the delay accordingly, however it may take some time (5-10s or more) for the Aec module to learn the optimal delay, thus a good initial estimate is necessary for good EC quality in the beginning of a call. 
    6262 
     63The delay should be '''at least''' as much as frame time (by default, ptime is 20ms) + {{{PJMEDIA_WSOLA_DELAY_MSEC}}} (the default is 5ms). 
     64 
    6365In PJSUA sample application, run it with the options {{{--ec-opt=3}}} and specify the delay estimate in {{{--ec-tail}}} options. For example: 
    6466{{{ 
    65 ./pjsua --ec-opt=3 --ec-tail=40 
     67./pjsua --ec-opt=3 --ec-tail=30 
    6668}}} 
    6769