One way speech path on Collab call

[smpallen99]

Check for existing issues

• [X] Completed

Describe the bug / provide steps to reproduce it

I tried my first collab session today but had an issue with the voice path. I could hear the other person, but the could now hear me. I tried with my Mac's builtin microphone as well as with a bluetooth headset. Neither worked. Attempted the call several times with no success. The other end noted they could hear a little noise, but nothing else.

We muted the speaker and mic on both ends and started a WebRTC call with my companies messaing app (from the same mac) and the call was fine. Dropped that call and the zed call. No luck, same symptoms.

Environment

Zed: v0.126.2 (Zed Preview) OS: macOS 13.3.1 Memory: 32 GiB Architecture: x86_64

If applicable, add mockups / screenshots to help explain present your vision of the feature

No response

If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.

No response

[ConradIrwin]

@smpallen99 Thanks for letting us know!

We're currently using LiveKit for audio, and not much beyond. Do you know (and are you willing to share?) some of the things that you do to ensure audio is reliable?

[smpallen99]

I'm looking over the LiveKit docs to understand it better. That might help me with some suggestions specific to LiveKit. However, before that, here are some tools I have used:

• Ability to enumerate input/output devices
• Ability to select input and output device from the list
• For the selected input device (microphone) , show a level meter (like you get in OSX System Settings -> Sound -> Input
• For the selected output device, show a play button` that plays a sound file over the device
• For webrtc, offer a diagnostics mode that shows a live view of connection statistics like the image below
• Log call setup events like offer and answer SDP, ICE candidates, etc.
• Offer an echo test feature, that when activated, plays a short audio message then plays back what is received by your microphone to you. This verifies that you input/output to/from the server is working

In my experiece, here are some of the most common issues with voice:

• NAT traversal
  • STUN servers help with this
  • TURN server may be required if a path cannot be determined (rtp relay)
• Host device locking
  • app B is holding onto the device so app A cannot use it. I see this (personally) occasionally and have not figured out how to detect is or workabound the issue

I hope that helps...

[ConradIrwin]

That's great, thank you!

We're currently working to rebuild LiveKit's rust client so we can make it work on windows. I'll make sure we consider these features as we're building it (and then it's "just" a case of building the UI :D).

That locking issue sounds nasty though..., but would be a bit better with a mechanism to debug it!

[smithxxl]

I too keep getting the chipmunk audio when muting myself. Very frustrating when stuffing my mouth with food while trying to listen to other collaborators. :pizza:

I am using Bluetooth headset with mic+audio.

Zed: v0.142.6 OS: macOS 14.5 Memory: 32 GiB Architecture: Intel