[jitsi-dev] last-n configuration


#1

I just read the article you guys published on https://developer.atlassian.com/blog/2015/07/video-conferencing/ and was wondering if in order to enable that I need latest git head for both JVB and jitsi-meet or if the versions currently pushed out of the Debian repos have that ability also?

Are there any instructions anywhere on how to go about configuring this? Does it involve settings on both JVB and jitsi-meet?

Cheers,

Roberto


#2

I’m guessing this MD file answers most of my questions?

https://github.com/jitsi/jitsi-videobridge/blob/master/doc/adaptive-last-n.md

···

From: Roberto Andrade
Date: Wednesday, August 5, 2015 at 12:24 PM
To: Jitsi Developers
Subject: last-n configuration

I just read the article you guys published on https://developer.atlassian.com/blog/2015/07/video-conferencing/ and was wondering if in order to enable that I need latest git head for both JVB and jitsi-meet or if the versions currently pushed out of the Debian repos have that ability also?

Are there any instructions anywhere on how to go about configuring this? Does it involve settings on both JVB and jitsi-meet?

Cheers,

Roberto


#3

Hi Roberto,

I’m guessing this MD file answers most of my questions?

https://github.com/jitsi/jitsi-videobridge/blob/master/doc/adaptive-last-n.md

This describes enabling *adaptive* last-n.

You probably just need last-n (what we talk about in the article). This should work with the debian packages, since they follow the master branches of our projects. I think you only need to set the option in config.js.

Regards,
Boris

···

On 05/08/15 13:08, Roberto Andrade wrote:

From: Roberto Andrade
Date: Wednesday, August 5, 2015 at 12:24 PM
To: Jitsi Developers
Subject: last-n configuration

I just read the article you guys published on
https://developer.atlassian.com/blog/2015/07/video-conferencing/ and was
wondering if in order to enable that I need latest git head for both JVB
and jitsi-meet or if the versions currently pushed out of the Debian
repos have that ability also?

Are there any instructions anywhere on how to go about configuring this?
Does it involve settings on both JVB and jitsi-meet?

Cheers,

Roberto

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#4

Ok, perfect. Thanks Boris.

···

On 8/7/15, 1:19 PM, "dev on behalf of Boris Grozev" <dev-bounces@jitsi.org on behalf of boris@jitsi.org> wrote:

Hi Roberto,

On 05/08/15 13:08, Roberto Andrade wrote:

I’m guessing this MD file answers most of my questions?

https://github.com/jitsi/jitsi-videobridge/blob/master/doc/adaptive-last-n.md

This describes enabling *adaptive* last-n.

You probably just need last-n (what we talk about in the article). This
should work with the debian packages, since they follow the master
branches of our projects. I think you only need to set the option in
config.js.

Regards,
Boris

From: Roberto Andrade
Date: Wednesday, August 5, 2015 at 12:24 PM
To: Jitsi Developers
Subject: last-n configuration

I just read the article you guys published on
https://developer.atlassian.com/blog/2015/07/video-conferencing/ and was
wondering if in order to enable that I need latest git head for both JVB
and jitsi-meet or if the versions currently pushed out of the Debian
repos have that ability also?

Are there any instructions anywhere on how to go about configuring this?
Does it involve settings on both JVB and jitsi-meet?

Cheers,

Roberto

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#5

And in case I'm using the fixed last-n value specified on meet. The bridge
receives that setting on each channel and then drops the video channel of
the non-dominant speakers (>last-n) by default or is meet doing that as
part of the endpoint logic?

···

On Friday, August 7, 2015, Roberto Andrade <roberto.andrade@gmail.com> wrote:

Ok, perfect. Thanks Boris.

On 8/7/15, 1:19 PM, "dev on behalf of Boris Grozev" <dev-bounces@jitsi.org
<javascript:;> on behalf of boris@jitsi.org <javascript:;>> wrote:

>Hi Roberto,
>
>On 05/08/15 13:08, Roberto Andrade wrote:
>> I’m guessing this MD file answers most of my questions?
>>
>>
https://github.com/jitsi/jitsi-videobridge/blob/master/doc/adaptive-last-n.md
>
>This describes enabling *adaptive* last-n.
>
>You probably just need last-n (what we talk about in the article). This
>should work with the debian packages, since they follow the master
>branches of our projects. I think you only need to set the option in
>config.js.
>
>
>Regards,
>Boris
>>
>>
>> From: Roberto Andrade
>> Date: Wednesday, August 5, 2015 at 12:24 PM
>> To: Jitsi Developers
>> Subject: last-n configuration
>>
>> I just read the article you guys published on
>> https://developer.atlassian.com/blog/2015/07/video-conferencing/ and
was
>> wondering if in order to enable that I need latest git head for both JVB
>> and jitsi-meet or if the versions currently pushed out of the Debian
>> repos have that ability also?
>>
>> Are there any instructions anywhere on how to go about configuring this?
>> Does it involve settings on both JVB and jitsi-meet?
>>
>> Cheers,
>>
>> Roberto
>>
>>
>> _______________________________________________
>> dev mailing list
>> dev@jitsi.org <javascript:;>
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/dev
>>
>
>
>_______________________________________________
>dev mailing list
>dev@jitsi.org <javascript:;>
>Unsubscribe instructions and other list options:
>http://lists.jitsi.org/mailman/listinfo/dev


#6

And in case I'm using the fixed last-n value specified on meet. The
bridge receives that setting on each channel and then drops the video
channel of the non-dominant speakers (>last-n) by default

Correct.

or is meet
doing that as part of the endpoint logic?

On the receiving side meet only adapts to what the bridge tells it (via data channels currently) it is sending.

These was work to make an endpoint stop sending while it is not being received by any other endpoint, but I am not sure whether it is currently used.

Regards,
Boris

···

On 17/08/15 06:08, Roberto Andrade wrote: