[research] Mic level meter in the call bar while unmuted — what exists today? #146
Open
opened 2026-09-17 16:51:58 -04:00 by jared
·
1 comment
No Branch/Tag Specified
lotus
update-packages
sw-fix
read-me-update
image-path-changes
dm-calls
fix-2469
renovate/element-hq-element-call-embedded-0.x
renovate/npm-i18next-http-backend-vulnerability
renovate/npm-vite-vulnerability
dev
docs-update
more-theme
fix-257
imporve-thread-reply
revert-2402-improve-menu-congestion
mxidColor-toggle
update-sw-main-msg
v4.11.1
v4.10.5
v4.10.4
v4.10.3
v4.10.2
v4.10.1
v4.10.0
v4.9.1
v4.9.0
v4.8.1
v4.8.0
v4.7.1
v4.7.0
v4.6.0
v4.5.1
v4.5.0
v4.4.0
v4.3.2
v4.3.0
v4.2.3
v4.2.2
v4.2.1
v4.2.0
v4.1.0
v4.0.3
v4.0.0
v3.2.0
v3.1.0
v3.0.0
v2.2.6
v2.2.5
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.3
v2.1.2
v2.1.1
v2.1.0
v2.0.4
v2.0.3
v2.0.2
v2.0.1
v2.0.0
v1.8.2
v1.8.1
v1.8.0
v1.7.0
v1.6.1
v1.6.0
v1.5.1
v1.5.0
v1.4.0
v1.3.2
v1.3.1
v1.3.0
v1.2.1
v1.2.0
v1.1.0
v1.0.0
Labels
Clear labels
a11y
area: appearance
area: auth-session
area: build-ci
area: calls
area: desktop
area: media
area: messaging
area: mobile
area: moderation
area: navigation
area: notifications
area: settings
area: threads
bug
dependencies
docs
duplicate
enhancement
help wanted
invalid
needs-human-review
performance
planning
priority: critical
priority: high
priority: low
priority: medium
qa
question
research
security
tech-debt
ux
wontfix
Accessibility: keyboard, screen reader, contrast, motion
Client area: appearance
Client area: auth-session
Client area: build-ci
Client area: calls
Client area: desktop
Client area: media
Client area: messaging
Client area: mobile
Client area: moderation
Client area: navigation
Client area: notifications
Client area: settings
Client area: threads
Something is not working
Third-party package versions and advisories
README / LOTUS_* docs wrong or missing
This issue or pull request already exists
New feature
Need some help
Something is wrong
Re-render storms, leaks, heavy work on hot paths
Data loss, security hole, or crash on a main path
Broken feature or serious usability problem
Minor issue or polish
Wrong behaviour in an edge case or notable degradation
Manual QA: shipped, needs a human in a real environment
More information is needed
XSS, unsafe URLs, data leaks, auth/session
Code health, dead code, fragile patterns
Usability or visual inconsistency
This won't be fixed
Milestone
No items
No Milestone
Features 2026-Q4
Projects
Clear projects
No projects
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: LotusGuild/cinny#146
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Inventory: does the EC footer show a local mic level (upstream has a speaking indicator on the self tile); does cinny's call bar / PiP show anything; does
io.lotus.call_statecarry a level or only a booleanspeaking? Then propose the smallest addition (likely: a 3-bar glyph on the cinny mute button fed by alevelfield, only while unmuted). Decide after the write-up.Inventory (2026-09-20)
Element Call (fork) — what exists
vm.speaking$→ green speaking border (GridTile/MediaView.speakingBorder), sound-wave glyph in spotlight. Source is LiveKit's booleanparticipant.isSpeaking(SFU active-speaker updates, ~300 ms cadence, delta-only).participant.audioLevel(0–1) but it is only refreshed by the same active-speaker updates — coarse, not a meter.src/lotus/lotusMutedSpeech.ts(#117) already runs a local AnalyserNode RMS sampler on the mic track — but only while muted, feedingspeakingWhileMuted.io.lotus.call_stateparticipants carryspeaking: boolean(+speakingWhileMutedfor self). No level field. The stream is throttled to 500 ms trailing (#20) — far too slow for a meter even if a level were added.Cinny — what exists
MicrophoneButton(features/call-status/CallControl.tsx): plain Mic/MicMute icon, no activity feedback at all.MemberSpeaking: "Name is speaking…" driven by the boolean stream (includes yourself), andMemberGlancepromotes speaking avatars.So today: boolean only, 500 ms late, and nothing on the mute button itself.
Smallest useful addition (proposal)
observeLocalMicLevel$that runs whenever a mic track exists (muted or not), RMS → quantised 0–3 bars with a little hysteresis. Emit a new fromWidget actionio.lotus.mic_level { bars }only when the quantised value changes, capped at 10 Hz. Silence and steady speech therefore cost ~0 messages; active talking costs a handful per second. Keepcall_stateuntouched (its 500 ms throttle stays right for what it does).CallEmbedhandlesio.lotus.mic_level→micLevelAtom.MicrophoneButtonoverlays a 3-bar glyph (three 2×{3,5,7}px bars in the icon's bottom-right corner, Primary colour) only whileenabled && bars > 0. Nothing else changes; PiP could reuse the same atom later.bars>0 && muted= talking while muted).Cost: ~60 lines fork + ~50 lines cinny + a fork release. Alternative "zero-fork" option: pulse the mic icon from the existing boolean
speakingfor self — free, but it is a yes/no indicator, not a meter, and lags ~0.5 s.Recommendation: do (1)+(2). Waiting for a go/no-go before building — this is the "decide after the write-up" gate from the issue.