[jitsi-dev] Jitsi-Meet VP9 support


#1

Hi,

Chrome will have VP9 by default in v48
https://www.chromestatus.com/feature/5652783105572864

Is jitsi meet ready?
which part need some love (jvb, jicofo, meet, ...)?

Thanks
Etienne


#2

Hi

Hi,

Chrome will have VP9 by default in v48
https://www.chromestatus.com/feature/5652783105572864

Is jitsi meet ready?
which part need some love (jvb, jicofo, meet, ...)?

Chrome 48 is out !
I've made a quick and dirty patch in
https://github.com/jitsi/jicofo/blob/master/src/main/java/org/jitsi/jicofo/util/JingleOfferFactory.java
just replacing VP8 with VP9 (and changing id 100 with 99 or 101 or ... to
be sure)
Chrome says googCodec = VP9 (in webrtc-internals) but there is no change in
bandwith usage, while some say VP9 can use up to 40% less than VP8

Regards
Etienne

···

Le 20 janv. 2016 18:54, "Etienne Champetier" <champetier.etienne@gmail.com> a écrit :


#3

I expect that it uses all available bandwidth, which would result in higher quality with VP9.

Regards,
Boris

···

On 22/01/16 09:23, Etienne Champetier wrote:

Hi

Le 20 janv. 2016 18:54, "Etienne Champetier"
<champetier.etienne@gmail.com <mailto:champetier.etienne@gmail.com>> a
écrit :
>
> Hi,
>
> Chrome will have VP9 by default in v48
> https://www.chromestatus.com/feature/5652783105572864
>
> Is jitsi meet ready?
> which part need some love (jvb, jicofo, meet, ...)?
>

Chrome 48 is out !
I've made a quick and dirty patch in
https://github.com/jitsi/jicofo/blob/master/src/main/java/org/jitsi/jicofo/util/JingleOfferFactory.java
just replacing VP8 with VP9 (and changing id 100 with 99 or 101 or ...
to be sure)
Chrome says googCodec = VP9 (in webrtc-internals) but there is no change
in bandwith usage, while some say VP9 can use up to 40% less than VP8


#4

Hi

Le 20 janv. 2016 18:54, "Etienne Champetier"
<champetier.etienne@gmail.com <mailto:champetier.etienne@gmail.com>> a

écrit :
>
> Hi,
>
> Chrome will have VP9 by default in v48
> https://www.chromestatus.com/feature/5652783105572864
>
> Is jitsi meet ready?
> which part need some love (jvb, jicofo, meet, ...)?
>

Chrome 48 is out !
I've made a quick and dirty patch in

https://github.com/jitsi/jicofo/blob/master/src/main/java/org/jitsi/jicofo/util/JingleOfferFactory.java

just replacing VP8 with VP9 (and changing id 100 with 99 or 101 or ...
to be sure)
Chrome says googCodec = VP9 (in webrtc-internals) but there is no change
in bandwith usage, while some say VP9 can use up to 40% less than VP8

I expect that it uses all available bandwidth, which would result in

higher quality with VP9.

Regards,
Boris

I see no change in quality (default resolution) and i would really prefer
reduced bandwidth usage (1800 kbits is too much when you only have ADSL)

Etienne

···

Le 22 janv. 2016 16:58, "Boris Grozev" <boris@jitsi.org> a écrit :

On 22/01/16 09:23, Etienne Champetier wrote: