Audio/video codecs by ACS

%3CLINGO-SUB%20id%3D%22lingo-sub-2449366%22%20slang%3D%22en-US%22%3EAudio%2Fvideo%20codecs%20by%20ACS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2449366%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there%2C%20do%20you%20have%20any%20detailed%20information%20on%20the%20audio%20and%20video%20codecs%20used%20by%20ACS%20when%20embedded%20in%20a%20website%2FJS.%20Including%20maximum%20bitrate%20if%20possible%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2449407%22%20slang%3D%22en-US%22%3ERE%3A%20Audio%2Fvideo%20codecs%20by%20ACS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2449407%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F4820%22%20target%3D%22_blank%22%3E%40Richard%20Thorpe%3C%2FA%3E%2C%20we%20use%20G.722%2C%20SILK%20and%20G.711%20(mostly%20in%20Azure%20direct%20routing%20for%20SBC%20compatibility).%20Detailed%20BW%20requirements%20and%20bitrates%20are%20documented%20here%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fcommunication-services%2Fconcepts%2Fvoice-video-calling%2Fnetwork-requirements%23network-bandwidth%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fcommunication-services%2Fconcepts%2Fvoice-video-calling%2Fnetwork-requirements%23network-bandwidth%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2449477%22%20slang%3D%22en-US%22%3ERE%3A%20Audio%2Fvideo%20codecs%20by%20ACS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2449477%22%20slang%3D%22en-US%22%3EHi%20Nikolay%2C%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20for%20getting%20back%20to%20me%20so%20quickly.%20Unfortunately%20the%20link%20doesn%E2%80%99t%20talk%20to%20maximum%20bitrate%20only%20required%20bandwidth%2C%20do%20you%20have%20any%20more%20specifics%3F%3CBR%20%2F%3EAlso%2C%20do%20you%20know%20when%20ACS%20will%20use%20the%20Satin%20codec%20recently%20introduced%20by%20Teams%3F%20-%20my%20thought%20process%20being%20that%20I%20presumed%20they%20were%20powered%20by%20the%20same%20engine%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2449488%22%20slang%3D%22en-US%22%3ERE%3A%20Audio%2Fvideo%20codecs%20by%20ACS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2449488%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F32380%22%20target%3D%22_blank%22%3E%40Richard%3C%2FA%3E%20Thrope%2C%20thanks.%20Please%20see%20in%20the%20table.%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fcommunication-services%2Fconcepts%2Fvoice-video-calling%2Fnetwork-requirements%23network-bandwidth%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fcommunication-services%2Fconcepts%2Fvoice-video-calling%2Fnetwork-requirements%23network-bandwidth%3C%2FA%3E%20E.g.%20with%201.2%20Mbps%20you%20can%20get%20HD720%20with%2030%20fps.%20Note%20for%20JavaScript%20you%20cannot%20go%20beyong%20720p%20at%2030%20fps%2C%20for%20Native%20we%20can%20go%20up%20to%201080p%20at%2030%20fps.%20Is%20there%20other%20parameters%20you%20are%20looking%20for%3F%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi there, do you have any detailed information on the audio and video codecs used by ACS when embedded in a website/JS. Including maximum bitrate if possible

8 Replies
@Richard Thorpe, we use G.722, SILK and G.711 (mostly in Azure direct routing for SBC compatibility). Detailed BW requirements and bitrates are documented here https://docs.microsoft.com/en-us/azure/communication-services/concepts/voice-video-calling/network-r...
Hi Nikolay,

Thanks for getting back to me so quickly. Unfortunately the link doesn’t talk to maximum bitrate only required bandwidth, do you have any more specifics?
Also, do you know when ACS will use the Satin codec recently introduced by Teams? - my thought process being that I presumed they were powered by the same engine
@Richard Thrope, thanks. Please see in the table. https://docs.microsoft.com/en-us/azure/communication-services/concepts/voice-video-calling/network-r... E.g. with 1.2 Mbps you can get HD720 with 30 fps. Note for JavaScript you cannot go beyong 720p at 30 fps, for Native we can go up to 1080p at 30 fps. Is there other parameters you are looking for?
Thanks Nikolay,

My understanding is that G.722 offers an audio sample frequency of 16kHz which results in a maximum 8kHz output. SILK, I believe, was as a result of the Skype acquisition in 2011 which created super-wideband audio capable of reproducing 12kHz from a 24kHz sampled frequency.

The exciting part of the MS proprietary "Satin" codec was that whilst it currently provides 16kHz output from a 32kHz sample frequency, it was mentioned that in the coming months this would be increased to provide 'full-band' audio at 48kHz. A standard CD has a 44.1kHz sample frequency, so this update would significantly improve audio output. Currently, competitors such as Zoom are already offering this quality so I'm keen to understand when we can become competitive?
Streaming services such as Spotify use MP3 audio and provide various bitrates from 128Kbps to 320Kbps. Bitrate is effectively the number of kilobits of data streamed per second. This sort of information would be very helpful.
Thanks. We are working on adding more codecs in upcoming quarter. I noted the level of details you want to have in the documentation. We will get these details in docs
Finally, my understanding is that ACS is using the H.264 and VP8 video codec for P2P connections delivered over WebRTC - sadly, this is the factor that limits video quality to 720p in the browser. Technologies like Google Meet (also leveraging WebRTC) have implemented the VP9 codec used by YouTube which gives them 1080p (and in fact I think 4K) video quality. Is there any plans for Microsoft to improve the existing service too?
Thanks, we are working on getting more codecs supported by ACS. Thank you for the feedback.