Disable googAvailableSendBandwidth to go back to 300kbps

692 views
Skip to first unread message

vib...@browserstack.com

unread,
Oct 6, 2014, 12:21:20 PM10/6/14
to discuss...@googlegroups.com
Hi,

The googAvailableSendBandwidth seems to be always going back to 300kbps and not giving enough quality of video even when the network supports larger bandwidth.

Do we have any mechanism to disable the bwe algorithm from working on chromium and setting the bandwidth manually ?

Thanks
Vibhaj

Browserstack

Luca De Cicco

unread,
Oct 6, 2014, 1:25:30 PM10/6/14
to discuss...@googlegroups.com
Dear Vibhaj,

that's very weird, can you provide more details on your network scenario.
Manually setting the bandwidth is generally not a good idea.

Cheers,
--
Luca De Cicco, PhD, Eng.
Politecnico di Bari
Dipartimento di Elettrotecnica ed Elettronica
Via Re David, 200 - Bari - ITALY
Office: +39 080 596 3851

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Vikas

unread,
Oct 6, 2014, 8:42:48 PM10/6/14
to discuss...@googlegroups.com
You can use the b=AS sdp param to control bandwidth... Can you share more details about the problem and how you recreating it with chrome?

/Vikas

vib...@browserstack.com

unread,
Oct 7, 2014, 11:04:21 AM10/7/14
to discuss...@googlegroups.com
Hi Luca,

The issue comes with Chrome sending webRTC video to Firefox client. The BWE algorithm just doesnt seem to improve Firefox bandwidth usage. It was suggested somewhere that Chrome is unable to interpret the RTCP packets sent by Firefox and it assumes BWE to reduce bitrate causing the low quality of video.


Hence manually setting bandwidth seems to be a better idea, in a situation where quality matters more to end user than bandwidth consumption.

The b=AS parameter just doesnt work in Firefox. We add this to sdp and when we check about:webrtc, we note its not part of the description any more, its just ignored by Firefox.

Thanks
Vibhaj

Browserstack

Vikas

unread,
Oct 9, 2014, 3:02:02 AM10/9/14
to discuss...@googlegroups.com
Can you file a bug in webrtc issue tracker with details about your setup, including browser versions used?

/Vikas

SProgrammer

unread,
Oct 10, 2014, 6:23:53 AM10/10/14
to discuss...@googlegroups.com
I could not reproduce it in Chrome M37 /canary M40 (Linux Ubuntu 14.04, Fedora 20, CentOS 7, OSX 10.9.4, Windows 7/8.1).
Reply all
Reply to author
Forward
0 new messages