Audit bandwidth settings

Question

Audit bandwidth settings

Opened this issue 5 years ago · 5 comments

Re-enable the settings section of the streamer page after deciding which settings should be there, and verifying what the settings actually do. Such as the bandwidth setting, what does it do, and does it actually need to be passed as a parameter.

Answer 1 · 2020-05-19T17:19:55.000Z

Could we split this up into a task to audit bandwidth (which we don't know much about / if it was working) and password (which is have an idea about and probably isn't secure) separately?

Answer 2 · 2020-05-29T04:55:14.000Z

@codysherman I believe I got the greenlight on this from you the other day, so I've split the password related work into #81, and updated this ticket to reflect just bandwidth.

Answer 3 · 2020-06-04T00:03:49.000Z

Relevant article to limiting the bandwidth via the sdp in WebRTC

Answer 4 · 2020-06-13T21:48:54.000Z

Front end UI in this branch: https://github.com/codysherman/2nfm/tree/bandwidth-slider

Answer 5 · 2020-08-12T10:10:54.000Z

I was previously using SDP munging to achieve bitrate constraints with varying success (due to different/newer encodings used, e.g. VP9).

Can't recall what RTCMultiConnection provides for stepping in during SDP negotiation, but it may be worth looking into a "new OOP method" mentioned by the SDP munging article.