search

microsoft / live-share

Real-time collaborative development from the comfort of your favorite tools
http://aka.ms/vsls
Creative Commons Attribution 4.0 International
2.28k stars 253 forks source link

Audio Call feature is not working #3819

Closed dmswjd-6 closed 3 years ago

dmswjd-6 commented 4 years ago

Issue Type: Bug

I have already tried to uninstall Live Share Audio > close VS code > delete live share audio extension folder >reinstall the audio extension, but still encounter seeing 1 call participant (myself) when I start the 'audio call'. Not sure why I cannot see 2 call participants (a different user connected via visual studio codespaces).

My peer cannot retrieve the audio call I send via VS Code.

Extension version: 1.0.2731 VS Code version: Code 1.48.2 (a0479759d6e9ea56afa657e454193f72aef85bd0, 2020-08-25T10:13:11.295Z) OS version: Windows_NT x64 10.0.19041

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz (8 x 1498)| |GPU Status|2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: enabled
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: enabled| |Load (avg)|undefined| |Memory (System)|15.60GB (3.95GB free)| |Process Argv|| |Screen Reader|no| |VM|0%|
nandiniYeltiwar commented 4 years ago

@youkiee Can you try out joining the audio call with yourself and check if you are both participants? Also what version of Live Share Audio do you have installed?

dmswjd-6 commented 4 years ago

@nandiniYeltiwar Thanks for the comment. When I try joining the audio call myself, I don't see two participants. The version I installed is v.0.1.85

nandiniYeltiwar commented 4 years ago

@youkiee We have fixed the issue in the upcoming release. It will be available to you in couple of days.

lostintangent commented 3 years ago

We released an update to the audio extension that should address this issue, so I’m going to close it as resolved. Please re-open this issue if you’re still running into problems. Thanks!