Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with insertable-streams/video-processing #1698

Open
jcalfee opened this issue Jan 22, 2025 · 3 comments
Open

Issues with insertable-streams/video-processing #1698

jcalfee opened this issue Jan 22, 2025 · 3 comments

Comments

@jcalfee
Copy link

jcalfee commented Jan 22, 2025

In Chromium Version 132.0.6834.83

https://webrtc.github.io/samples/src/content/insertable-streams/video-processing/

Open the dev console, then select "Video" in the demo page and observe the warning:

video-processing/:1 [GroupMarkerNotSet(crbug.com/242999)!:C0A02D00242C0000]Automatic fallback to software WebGL has been deprecated. Please use the --enable-unsafe-swiftshader flag to opt in to lower security guarantees for trusted content.

The default is WebGL which likely triggers the warning. WebGL creates some sort of wave distortion effect around the edges (see the trees):

Image

If I change to canvas 2D, that probably gets ride of the webgl related error, but there is a dark border around the image:

Image

Can you recommend a setup that will likely work? I may need to go into a custom player if I can't do that here. Thank you..

@fippo
Copy link
Collaborator

fippo commented Jan 28, 2025

@beaufortfrancois do you know who would know what change caused this?

@beaufortfrancois
Copy link
Contributor

I assume this is related to https://chromium-review.googlesource.com/c/chromium/src/+/5675974 and https://issues.chromium.org/issues/40277080
Hopefully @vonture knows more

@vonture
Copy link

vonture commented Jan 29, 2025

@beaufortfrancois Found the right links. It looks like your setup does not have a GPU that Chrome is able to use or it is disabled with some flags. If this is for your own local development, you can use the flag in the deprecation message and it will continue to work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants