I'm doing some research on next-gen voice codecs and obviously want to know as much as I can about Microsoft Satin and Google Lyra, if anyone on this board can help.
I have two overarching questions about these codecs, if any of you know, and their smartphone compatibility and implementation. (And forgive the potentially nonsensical nature of these questions – I am not that technical!)
1. Do either of these codecs need to be included in either iOS or Android in order for them to be activated when using compatible apps – i.e. Microsoft Teams, Skype, or Google Meet – on a smartphone? Or, is the codec included within these Satin- or Lyra-compatible apps within iOS or Android with no OS or chip-based Satin or Lyra codec necessary? In other words, how are these codecs activated/implemented on a smartphone since they are not supported by iOS or Android or by WebRTC?
2. How likely is it that Satin or Lyra is eventually, sooner or later, included in WebRTC or either iOS or Android? Or, is it that if/when Satin or Lyra is implemented within WebRTC that one or the other will automatically be included in iOS and Android? Neither Satin nor Lyra would be implemented within iOS or Android separately without WebRTC, right?
I'm happy to move this conversation to email if appropriate. I just don't know if it's allowed to list email addresses here.
Thanks in advance if anyone can help!
On Sep 10, 2022, at 10:37 PM, Roman Shpount <rshp...@gmail.com> wrote:
1. No, neither of those codecs need to be included as part of the operating system, such as iOS or Android. This is just another library that application developers will use when building their own implementation of conferencing clients. Considering that these are audio codecs, there is little benefit of hardware optimization or making them part of the operating system. In fact, there are existing smartphone applications (Google Duo and Teams) that use these codecs
You received this message because you are subscribed to a topic in the Google Groups "discuss-webrtc" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/discuss-webrtc/-jLeZAQoSP8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/bc6a47b2-9528-4ddc-82bd-ef6f0937fa27n%40googlegroups.com.
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/ED1BDE2D-6A53-49B8-8D06-FC2B6A475C29%40gmail.com.
On Sep 11, 2022, at 10:37 AM, 'Philipp Hancke' via discuss-webrtc <discuss...@googlegroups.com> wrote: