Compared to not having to, its certainly more cpu intensive, not so much compared to video transcoding.  Depending on the rates involved its probably less expensive than g729 or opus transcoding, more so than g711 transcoding.


On Jul 28, 2017, at 5:45 PM, Muhammad Naseer Bhatti <nbhatti@gmail.com> wrote:


Ok Awesome. So the transcoding from one sampling rate to other is expensive and does takes some CPU cycles, correct?

From: Anthony Minessale <anthony.minessale@gmail.com>
Reply: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>
Date: July 28, 2017 at 11:03:18 PM
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>
Subject:  Re: [Freeswitch-users] Is there Sampling rate conversion CPU penalty? 

Pro tip:

If the file path is /var/sounds/example.wav

you can create 

/var/sounds/8000/example.wav
/var/sounds/16000/example.wav
/var/sounds/32000/example.wav
/var/sounds/48000/example.wav

And it will auto-select the correct one that matches the sample rate of that call.


On Fri, Jul 28, 2017 at 2:53 PM, Tayeb Meftah <tayeb.meftah@gmail.com> wrote:
Hey,
The best practice is to transcode your wave files to the diferent rates your clients use
If your clients are only on pstn side, 8khz should be enough
If your clients is on sip side, better to generate 8, 16,32, and 48khz (mono) files
Converting rate is a cpu intencive task and its part of transcoding, so its not recomanded...
Thanks.

Envoyé de mon iPad

Le 28 juil. 2017 à 20:24, Muhammad Naseer Bhatti <nbhatti@gmail.com> a écrit :

Hi, I am streaming a wav file who’s sampling rate is 44100 and FreeSWITCH says sample rate 44100 doesn't match requested rate 8000. So I think it’s doing the conversion here. If so, is there any CPU performance penalty while doing the conversion? What’s the best practice here should I change the sampling rate of the file or just leave it like that?