Hello
Not quite, the original intention seemingly is like this:
* If the external audio DSP is MS-Teams-certified, all the MS-sided audio processing will be turned off, be it on the cloud side OR within the local running app.
Reason: The certification process proved, that the in-room external DSP is able to do a good in enough or even better job than all MS' automagic.
* If the DSP is NOT certified, then MS does not switch off its own processing but forces it.
Reason: MS does not know, how "good" the DSP is, so better safe than sorry. Well, ....
* The external DSP can indeed signal to the host PC, that it does have AEC capabilities. This is done via the USB terminal type. Trusted rumors are, that for example SkypeConsumer uses this info to switch on/off local AEC. However MS Teams does NOT work that way. Teams is using its own whitelist = certification list to decide.
This has some serious consequences, which are far from optimal:
1. If you hook up a perfectly working but not-certified external DSP, then MS nevertheless throws in its own DSP/AEC. Now having two different DSPs trying to improve audio is almost a guarantee for more or less distratrous results.
==> If using a non-certified DSP (for whatever reason), do yourself a favour and switch off all its dynamic functions and also switch off all kinds of AEC, NR=noise reduction and other gizmos until MS wakes up and gives us audio guys some control over the MS side of audio processing.
=> AEC and NR are highly dynamic processes and work well only in an otherwise non-dynamic system. Their operation is pure "cause and effect" like you turning the driving wheel. As soon as someone else is also steering without you knowing, your wheel turning (cause) will have a different effect, from what you expected.
Means: If you have two or more of theses dynamic parts like AEC & NR in the signal change, things get very ugly very fast.
2. The algorithms in the cloud are most likely developed at a much faster pace and using much more smartness (like machine learning, etc.) compared to a local audio DSP, which is most likely installed, tuned and afterwards forgotten about.
Means: It could be very beneficial to combine both the on-site specific tuning of an in-room DSP setup by knowledeable people AS WELL AS still having access to advanced stuff like psycho-acoustic tricks from a cloud-based intelligence.
However, until audio guys dont have acess to both cloud-side as well as local (in-app) processing, it is close to impossible to tune for perfection. Also the cloud side can (and will!) change any time and the app-side can change with any monthly app update. So what used to work well can break any time!
3. Just installing a certified external DSP does not guarantee perfect results. There are so many parameters to tweak on a modern DSP => many possibilites to screw up.
Despite all their good intentions, MS can never be sure, that the external audio DSP is setup properly. The certification process proved, that the external box CAN be made sounding great, but has zero to do with the actual install.
Long story short:
In order to make it simply for a majority of people, MS does it make very difficult for people knowing what they are doing OR for applications which are "beyond" than the cubicle and standard conference room setup and therefor needing specialist audio know-how & hardware in the room.
As stated: Others give me as the audio guy at least some basic access but the whole concept is far from being perfect.
Hope this helps
HST
8605pemo wrote:
Graham, in general. Would you say that what he says can be applied? That if a DSP is non certified, audio processing will be ON in the cloud and if the DSP is certified, all audio processing will be handled within the cloud?
I have read already that when a device connectsto a pc, it will do some kind of driver handshake to identiy what built in driver/ profile that will be used depending on application.
This is a imortant subject to lift and the answer is not very clearly stated.
@8605pemo
