nextcloud / nextcloud/spreed

Trigger threshold for visual outline sound indication insufficient + lack of outline visibility

Open
#12,920 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

design enhancement feature: call 📹
Dominant language
PHP
Stars
2.2k
Forks
587
Avg merge
18h 27m
Merged PRs (30d)
333

Description

My colleagues and I use Talk every day. Here's a statement that everyone agrees on.

In videoconferencing software, such as BigBlueButton, when a participant's background noise is detected, it's immediately obvious (the label with the participant's name lights up at the slightest noise), enabling the moderator(s) to spot the person concerned and ask them to do what's necessary, or even mute them until they need to speak.

In Talk, the white contour line is not sensitive enough and is only activated when the person is actually speaking. This lack of sensitivity may be intentional on your part, and is in line with speech time detection... except that, in the real world, with what I've just described, it has the perverse effect that video meetings are easily polluted by background noise without you being able to tell who it's coming from.

Is it possible to set a trigger threshold as low as possible, independently of the threshold used to measure speaking time?

I'd also like to take this opportunity to point out that the current white outline is not visible enough in my opinion, especially as it also looks too much like the white outline when the cursor is hovered over the person's block. I think it should be different, for example thicker, with a possible animation suggesting a sound flow ... or a microphone icon over the block (z-index), whose color (of the icon itself or of the background) would change to a clearly visible color.

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified in the issue. Start by locating the Talk participant audio-activity indicator and the threshold used for speaking detection, then review how the participant hover outline is rendered; done should include a distinct, more visible background-noise indication with a separate trigger threshold.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
audio-video-rtc, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.