"bitrate" in janus.plugin.videoroom.cfg seems invalid to firefox

[dre...@gmail.com]

Hi,

    My idea is a publisher publishs both high  and low quality videos at the same time . The subscriber watches the low quality video by default. 

    Once the subscriber click on the video to zoom in, the low quality switch to high quality. 

    At anytime, only one video is high quality while all others are low.

    In this way, a videoroom can display more participants.(for instance 10, even 20).

    Further, we can add "page turning" feature to the plugin. Once we turn to next page, we switch the videos to new ones.

    It seems like we can display plenty of participants in a videoroom. (I know, there is plenty of work to achieve that . )

    My question is,  I set "bitrate=64000" in janus.plugin.videoroom.cfg . ( I know the plugin doesn't allow bitrate to go below 64kb. )

    But it seems  invalid to firefox 44.02.  The bitrate keeps at 200kb more or less. Can you tell me why? 

    By the way,  "secure_port=8889" in janus.transport.http.cfg seems should be "secure_port=8089" according to 49 line in videoroomtest.js . 

    I apologize if I have made a mistake.

    Thanks for your time.

[Lorenzo Miniero]

Hi,

not sure about this. For forcing a lower bitrate we use REMB, so it really depends on whether or not Firefox accepts directives to go under a certain threshold. I'll check on the port thing, I'm currently abroad for a conference: if it's a typo in the config I'll fix it.

Lorenzo

[Ancor Gonzalez Sosa]

El jueves, 14 de abril de 2016, 20:10:33 (UTC+2), dre...@gmail.com escribió:

    But it seems  invalid to firefox 44.02.  The bitrate keeps at 200kb more or less. Can you tell me why? 

Yes. That's a Firefox setting that can be adjusted via about:config:
 media.peerconnection.video.min_bitrate

It's set to 200 by default. Something I personally dislike. Should we maybe open a bug report on Firefox asking for setting it to a more "polite" default value?

Cheers.

[Mike]

Firefox does not parse the b=AS parameter in the SDP which Chrome uses to limit the bitrate.

See this bug on bugzilla;

https://bugzilla.mozilla.org/show_bug.cgi?id=976521

We've resorted to only allowing Chrome to publish cams for now, but it's not an ideal solution since it could be bypassed

If the client has to be trusted to send a lower bitrate, like Firefox doesn't seem to do, how could we in ensure the viewers don't get that high bitrate forced upon them?

Lorenzo, would you have any idea of creating a server side bottleneck of some sorts to force the bitrate that's going out to the subscribers is capped?

Ancor, have you actually been able to successfully limit the bitrate using that? I've just tried it again setting the min_ max_ and start_ bitrate to 64, but Firefox is still publishing around 200kbps

Thanks

[Ancor Gonzalez Sosa]

Yes. I did some successful experiments exactly one year ago. I have to admit I have not re-checked with recent versions.

Cheers.

[dre...@gmail.com]

 Ancor, thanks for your clear answer .  It's a great help !

 Your suggestion is considerable .  I may try it .

 Apologize for my late reply .

cheers.

在 2016年4月15日星期五 UTC+8下午7:07:20，Ancor Gonzalez Sosa写道：