| Summary: | Need a way to represent muting (part of) a call | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Will Thompson <will> |
| Component: | tp-spec | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | to fix in Call | ||
| i915 platform: | i915 features: | ||
| Bug Depends on: | 24936 | ||
| Bug Blocks: | |||
|
Description
Will Thompson
2009-05-21 03:11:29 UTC
Here's the Mute interface that Maemo 5 uses in GSM calls: http://git.collabora.co.uk/?p=rtcom-telepathy-glib.git;a=blob;f=rtcom-telepathy-glib/Channel_Interface_Mute.xml Maemo 5's interface just has a single boolean, "am I muting the call?". However, Sjoerd suggests that what we actually want (particularly for Muji) is a mute flag per content (so in practice, audio and video, where "muting video" means sending no frames, or sending black frames, or something). We briefly discussed the possibility of protocols existing where you could stop sending your audio to particular people, e.g. if I'm in a call with Sjoerd and Will, I could stop sending audio to Will but continue talking to Sjoerd. However, the only use-case we could see for this is complaining about Will behind his back; as well as being somewhat antisocial, this wouldn't actually work very well, because Sjoerd will still be sending audio to Will, and if Sjoerd's microphone picks up his speakers a little bit (in practice, it will), Will can still hear what I'm saying about him. Also, making a user interface for muting streams to individual contacts doesn't sound very plausible. There doesn't seem to be much point in adding this to StreamedMedia when Sjoerd's Call API (Bug #24936) is just round the corner, so we'll fix this in the Call channel type. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.