[FEATURE] FluidMeet: warn when my microphone is dropped, and support external speakers
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- macos, swift
- Domain
- audio-video-rtc, desktop
Research direction
The payload names two session-log events, voiceProcessingDeclined and transcriptCoverageIncomplete; search the Swift sources for those strings to find where voice processing is turned on or declined based on the output device. Done means a notice appears when recording starts and the microphone is not transcribed on the current output, and voice processing stays enabled on external speakers such as a Studio Display. The payload does not show whether echo cancellation can be enabled there, so check that before scoping the change.
Written by the indexing model from the issue text.
Description
FluidMeet left my whole side of a 54-minute Zoom call out of the transcript, and I only found out afterwards by reading the session files.
My Mac plays sound through a Studio Display (USB). The session log has two events:
voiceProcessingDeclined: "The output device is not the built-in speakers."transcriptCoverageIncomplete: "3224.5 seconds of microphone audio were excluded"
The microphone audio is on disk, but none of it reached the transcript. The other side of the call came through fine.
Two requests:
- Tell me at the start of a recording when my mic won't be transcribed. A notice like "Your microphone won't be transcribed on these speakers. Switch to the MacBook speakers or headphones" would have let me fix it while the call was still going. Right now FluidMeet drops my side of the call without telling me.
- Keep the microphone working when my Mac plays sound through a Studio Display or another external monitor. Zoom and Meet already cancel echo on these speakers, and plenty of people work at a desk with a monitor's speakers.
For now I switch the Mac's output to the MacBook speakers whenever a call starts.
Setup: FluidVoice 1.6.12-beta.1, macOS 27.0.1, MacBook Pro (Apple Silicon) with a Studio Display. Microphone: MacBook Pro Microphone. Meeting app: Zoom.
- Dominant language
- Swift
- Stars
- 11.9k
- Forks
- 863
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 28
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from altic-dev/FluidVoice
-
bug
Difficulty 4/5 1-2 days Newbie friendliness 35/100
altic-dev/FluidVoice#1138 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
altic-dev/FluidVoice#1137 ·
Maintainers usually reply within 1 day
-
[FEATURE] FluidMeet: recover excluded microphone audio after the call with offline echo cancellationOpen
Difficulty 5/5 Over a week Newbie friendliness 15/100
altic-dev/FluidVoice#1136 ·
Maintainers usually reply within 1 day
-
[BUG]Openbug
Difficulty 4/5 3-5 days Newbie friendliness 15/100
altic-dev/FluidVoice#1133 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
altic-dev/FluidVoice#1119 · 2 comments ·
Maintainers usually reply within 1 day
All issues in altic-dev/FluidVoice
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
meshtastic/Meshtastic-Apple#2603 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug Windows
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
fyi-ecosystem platform-ios team-ios
Difficulty 1/5 Under an hour Newbie friendliness 70/100
flutter/flutter#194348 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
freestylefly/WeChatBridge#44 ·
Maintainers usually reply within 1 day