You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a custom video source from a video element on Chrome (have not tested on other browsers), the "remote" video stream is extremely over saturated. I've confirmed that the video stream captured from the video element is not the issue (by rendering the stream directly in a separate video element), and other remote streams render fine, so it appears to be something on the creation or transmission of the custom video track.
See screenshot from the custom video source demo below (left is the host publishing the sample.mp4, right is receiving it):
The text was updated successfully, but these errors were encountered:
tested on Chrome Version 96.0.4664.45 (Official Build) (arm64)
Seems cannot reproduced the issue, what's your browser build number? Do you have chance to verify on different browsers?
the captureStream API might be some supportability issue via different browsers.
for details you could check on https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement/captureStream
I'm on Version 95.0.4638.69 (Official Build) (64-bit), the latest on Ubuntu. I can test it on FF later today or my Windows machine this weekend and will update then.
When using a custom video source from a video element on Chrome (have not tested on other browsers), the "remote" video stream is extremely over saturated. I've confirmed that the video stream captured from the
video
element is not the issue (by rendering the stream directly in a separatevideo
element), and other remote streams render fine, so it appears to be something on the creation or transmission of the custom video track.See screenshot from the custom video source demo below (left is the host publishing the sample.mp4, right is receiving it):
The text was updated successfully, but these errors were encountered: