RTX not set up properly for cast? |
|||||
Issue descriptionI ran some test casting to a hangout wile running chrome with logging turned on and came across a line that bothers me. I get a log line about rtx payload type not being configured: https://cs.chromium.org/chromium/src/third_party/webrtc/media/engine/webrtcvideoengine2.cc?q=webrtcvideoen+package:%5Echromium$&l=1748 The same line does not appear when go into a hangout and screenshare the "normal" way. If rtx is indeed not configured properly, it could cause some pretty severe disruptions to a video stream. skonig@ can you have a look or reassign to whomever knows how this is configured?
,
Mar 29 2017
Peter, do you know who on the realtime library side would be knowledgable about this?
,
Mar 29 2017
Can you open an internal bug for questions about the internal JS libraries? Thanks! You can assign to me for now, I'll reassign as necessary.
,
Mar 30 2017
I wasn't sure if he means internal JS or WebRTC. The bug is likely in the JS if there is one. So I will hand it off to Noah.
,
Mar 30 2017
Right, given that, can you open an internal bug? We don't track chromium for issues in the realtime library.
,
Apr 6 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by brandtr@chromium.org
, Mar 29 2017