Removing Audio Calling from Live Share in Visual Studio Code

[fubaduba]

The Live Share team has made the decision to remove the audio extension that works in conjunction with Live Share. The date of removal will be announced on this issue.
Adding audio calling in Live Share was part of our effort increase the fidelity of pairing sessions. Since then, the pandemic has forced everyone to use a default communication tool that usually allows a generous guest and outside organization policy. While we do see some small and consistent use of the audio extension with Live Share, we want collaboration in the editor to focus first on coding related features, improve performance and usability of them, while innovating on ways to make it more enjoyable.
All of this brings us to the conclusion that Live Share will no longer support the audio extension in the upcoming year, and we will do a gradual sunset of it.
Please follow this issue for updates and support.

Audio extension in Visual Studio Code:
https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsliveshare-audio
https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsliveshare-pack

[RichNSD]

Now that you've decided to officially kill it (for now, at least), I have a sneaking suspicion that many more people were experiencing the very strange bug I had with another collaborator of mine.

For some strange reason, even though the Main LiveShare Extension was working without issue, as soon as my friend installed the Audio Extension, his entire LiveShare bundle decided to disappear from his VSCode Interface and none of my invites worked (they just opened his VSCode and did nothing). lol

So maybe it's a mercy killing and the rest is just convenient. 😛

[mengesb]

While I understand the motivations described above, I would much rather have embedded audio vs chat/text during a LiveShare session, would much rather have the power efficiency of one application vs two to get audio, and use a platform that doesn't even have the option for a camera. This appears to be a minority opinion, and I respect that, however am still sad. Making VSCode dependent on the likes of Slack, Teams, Skype, CallCentral, Twilio, HipChat, etc. for voice communications or a better pair-programing experience seems like a misstep IMO.

[alfredotp]

I am sorry that you have made this decision, I have tried this extension and it seemed very good collaboratively. I hope they reconsider this decision, which seems to me a step backwards.

[RichNSD]

I'm with @mengesb, honestly.

While I understand the motivations described above, I would much rather have embedded audio vs chat/text during a LiveShare session, would much rather have the power efficiency of one application vs two to get audio...

Not only do I find the text chat... clunky, for lack of a better term, but since VS Code lacks the UI Customization/Arrangement Freedoms that Visual Studio has, trying to keep the chat in-view while you work is (at best) tedious.

Making VSCode dependent on the likes of Slack, Teams, Skype, CallCentral, Twilio, HipChat, etc. for voice communications or a better pair-programing experience seems like a misstep IMO.

While I don't see an issue with being somewhat dependent upon these apps, which offer a significantly greater amount of control over calls & meetings, it would be nice not to require them for a simple audio chat. The biggest reason for that on my list, however, is in regards to System Resources (namely RAM), since the aforementioned apps do a lot more than just the call/meeting you want/need to be part of.

[amjedidiah]

Totally agree with @mengesb and @RichNSD
#bringbackliveshareaudio