paulhsu / csipsimple

Automatically exported from code.google.com/p/csipsimple
1 stars 1 forks source link

Sound get deformed on HTC Desire V with g729 #1974

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Install csipsimple
2. Enable g729
3. register and make a call

What is the expected output? What do you see instead?
Expected: the other side can hear sound normally and can make a conversation.
Actual: The other side still HEAR sound but the sound got heavily deformed and 
hardly to understand the meaning.

What version of the product are you using? On what operating system?
HTC Desire V

Please provide any additional information below.

- The work around is to goto the configuration page and set clock rate to 8khz 
then the problem disappear.

- If the software can adjust the clock rate based on the choosen codecs then it 
would be ideal.

Original issue reported on code.google.com by nguye...@gmail.com on 18 Sep 2012 at 7:23

GoogleCodeExporter commented 9 years ago
Mmmh, interesting point.

Actually oversampling of media device regarding the codec should not be a 
problem. There is a part of the code dedicated to resample. Having higher 
sample rate on device gives better perceived result in normal cases.

So here it could be several root cause.
 - Is it something you have only with g729 or is that observed for all codecs (for example pcmu/pcma)?
=> If you reproduce with other codecs it could be because of a problem with htc 
desire V when open micro @16kHz (and a bug on htc).

 - Else, maybe you can try to change the extra g729 frame per packet option? (maybe switching between 1 and 2 could produce differences).

 - If you are in expert setting mode, maybe changed the media quality option? By default it's 4, but changing the value may change the resampler implementation and make it consume more CPU.

Let me know how test goes. If case 1, I can automatically as workaround change 
the clock rate value for this htc device. It's already done for some devices 
that has known bad implementation (it's usually motorola devices).

Original comment by r3gis...@gmail.com on 18 Sep 2012 at 10:34