Not rendered by attachVideo() when blur is enabled in createLocalVideoTrack()

Video SDK Web
1

Video SDK Web and Version
Zoom Web Video SDK 1.11.0
Google Chrome
Version 125.0.6422.76 (arm64)

Description
Once start() to canvasTag with blur enabled after createLocalVideoTrack(), even after stop(), attachVideo() will not render any video other than its own.
When start() is done to videoTAg without blur enabled, it works fine.
The same is true for video-sdk-sample.

There is no error in attachVideo() itself.

1 Like
2

We have investigated with 1.11.6 following an update of the Zoom Web Video SDK and have confirmed the same behavior.

About the operations we performed

  1. launch videosdk-web-sample locally by npm run start.
  2. Launch 2 browser windows and access each window.
  3. In one window A, enter /preview, start camera, and do background blur.
  4. Browser back in window A and return to the menu.
  5. In window B, go to /video and turn on the camera.
  6. Go to /video in window A and turn on the camera
  7. The camera content that should be sent from window A is not rendered in window B because it is completely dark.

I am currently designing a transition like google meet that checks the preview before the session starts and then starts the session as is.

If I apply blur on the preview, it will not be a correct preview if the image is not sent to the other party. (I want to have blur during the session).

Is there any workaround for this?

3

Hey @H-Takesue

Thanks for your feedback.

May I assume that you are testing on Windows Chrome?

As you mentioned, you launched two browsers on the same computer. If you didn’t specify the camera ID, both browsers will use the default camera. When the second browser (window A) starts the video, it will fail because the camera is already occupied by the first browser (window B), resulting in a black screen in window B when viewing A.

It would be better if you could share the session ID with us for troubleshooting purposes.

To keep the preview audio/video settings in the session, you can implement this yourself. Store the state chosen during the preview and set the corresponding parameters in the session. Both stream.startAudio and stream.startVideo have options to specify the preset settings.

Thanks
Vic

4

Thank you for your reply.

The test was performed using google chrome on a Mac book pro.
MacBook Pro 14-inch,2021
M1 Max
Sonoma 14.4.1

When I checked the same situation locally again, the session id was eGOZ4UFISRSpmgn1XbkiOQ==

In localVideo, when Blur is not used, the camera information is properly displayed instead of a black screen.

This only happens when using Blur in localVideo.

5

Hey @H-Takesue

I’m sorry, our sample app might be somewhat misleading regarding the preview feature.

When you launch this sample, you will join the session by default, but the preview feature is typically a pre-session operation. To correct this behavior, you need to leave the session first and then navigate to the preview page. This way, after you finish the preview and return, you can click join to rejoin the session. This is for the pre-session virtual background feature.

For the in-session virtual background preview, you can directly call the stream.previewVirtualBackground method to preview the video.

Thanks
Vic

6

Hello Vic

Thank you for your reply.

I changed the timing of the join method to the timing of the transition from the preview screen to the session screen and verified it.

Both the preview rendered on the video and the preview rendered on the blurred canvas rendered correctly on the session screen.

We also verified that the background specification on the session screen also works correctly.

Thank you very much for sharing this information.

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.