[jitsi-users] Last-N support status

#1

Hi,

I've seen this issue on github:
https://github.com/jitsi/jitsi-meet/issues/9

This is really exciting! Basically, it tells that active speaker detection and last-N features are now supported by Jitsi.

Could you elaborate a bit about the status and plans for it?

E.g. I have the following questions:

1) Is it only supported at the Colibri protocol level, i.e. new messages, etc? Or have you already implemented the server-side logic for really analyzing audio streams and filtering out the last-N streams?

2) If you have already implemented active speaker detection, which audio formats are supported?

3) How Jitsi signals to the client that certain streams are not sending at the moment?

4) How Jitsi signals to the client which participants are the last-N ones?

5) Have you considered the API/Colibri protocol extension which would allow a participant to explicitly pick which streams (i.e. from which participants) it would like to receive? What do you think of having such a feature? It would allow for scenarios where you want to have explicit floor control, etc...

Thanks,
Leo

#2

Any hope to get an answer about the status of the Last-N feature?

Thanks,
Leo

#3

Hey Leo,

Hi,

I've seen this issue on github:
https://github.com/jitsi/jitsi-meet/issues/9

This is really exciting! Basically, it tells that active speaker
detection and last-N features are now supported by Jitsi.

Could you elaborate a bit about the status and plans for it?

There's more work there. What we do support is tracking audio activity in the bridge and filtering video streams based on that. This is not currently usable with the WebRTC API and we are working on

a) improving dominant speaker detection.
b) sending dominant speaker notifications to the Browsers.
c) adding support for key frame requests.

E.g. I have the following questions:

1) Is it only supported at the Colibri protocol level, i.e. new
messages, etc? Or have you already implemented the server-side logic for
really analyzing audio streams and filtering out the last-N streams?

More like the latter.

2) If you have already implemented active speaker detection, which audio
formats are supported?

It works in a format-independent way. Both Opus and G.711 are supported.

3) How Jitsi signals to the client that certain streams are not sending
at the moment?

It doesn't do that just yet. That's what we are working on.

4) How Jitsi signals to the client which participants are the last-N ones?

Isn't this the same question? Or am I missing something?

5) Have you considered the API/Colibri protocol extension which would
allow a participant to explicitly pick which streams (i.e. from which
participants) it would like to receive? What do you think of having such
a feature? It would allow for scenarios where you want to have explicit
floor control, etc...

We are thinking about this right now but we are more likely to do this independently of COLIBRI. The organiser (focus) is the only one that has a COLIBRI connection with the server and everyone else doesn't.

We are planning on using DataChannels for this purpose.

Hope this helps,
Emil

ยทยทยท

On 03.04.14, 15:23, Leo Romanoff wrote:

--
https://jitsi.org