• xians's avatar
    Avoid reporting 0 as input level when AudioProcessing zero out the audio data. · ba5b0d78
    xians authored
    When the microphone volume is low, the pre-processed audio data contains energy, while the post-processed audio data has only 0, we report 0 as energy before this patch, which is wrong since the audio flow contains energy.
    
    This patch fix the problem by checking the energy of pre-processed data before reporting 0 as energy.
    
    BUG=424149
    TEST=1, use a USB headset.
    2, set the microphone volume low, like below 50%.
    3, join a hangout call.
    4, open chrome://webrtc-internals, and look at the energy of input stream, constantly it is 0 there.
    
    Review URL: https://codereview.chromium.org/661693003
    
    Cr-Commit-Position: refs/heads/master@{#300274}
    ba5b0d78
webrtc_local_audio_track.cc 9.55 KB