[Bug 26807] Mute interface for Channel.Type.Call

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=26807


Olivier Crête <tester at tester.ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tester at tester.ca




--- Comment #10 from Olivier Crête <tester at tester.ca>  2010-03-30 12:45:12 PST ---
(In reply to comment #9)
> Do we need to tell Farsight to mute things, or just leave it up to the
> UI?

Mute can be implemented in two ways:

1. Turn the volume down to 0
2. Actually stop sending data

For case 1, then this is only for GSM as for everything else the UI can do it
by itself (like it happens right now in Fremantle). That said, Jingle has a
"mute" informational message that may be useful.

For case 2, that's what "direction = receive" is.

> Do we want to relay the fact that we've muted our mic to the other
> parties? We don't see any harm in it: it's useful metadata, and isn't an
> information leak because you can hear that someone's gone silent anyway.

For Jingle, we definitely want to do that. I don't think other protocols have
that.

> If we make the UI control the actual muting (or in the Maemo case, make
> it talk to s-e directly) then it could control whether not to tell the
> other guy by whether or not it call Mute() on the CM. But for GSM it
> needs to call Mute() on the CM because that's the thing which cares. So
> two semantics here: one informational, one a request.

On maemo right now, s-e does not do mute, the UI talks directly to pulseaudio
(or audiopolicy or something).

I think the real question is: Does GSM have a direction=receive that's
different from Mute? If yes, then we need a Mute() call, if not just change the
direction.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.