Description
One of our regular users started getting the error VIDEO_VB_SETTING_ERROR on ZoomVideo.createLocalVideoTrack().start() after the update from v2.3.5 to v2.3.12. The session id is hdr8QX99S8yC//QSnMCZJw== if that is helpful for video previews (sounds like they were not able to join the session)
I see in the docs that there is a VIDEO_VB_INITIALIZE_ERROR but not one that matches the video preview error of VIDEO_VB_SETTING_ERROR.
Assuming it is a video blurring issue with the local video preview, what is the best way to check if the user’s device should have a blur option? Currently we are disabling it on firefox and mobile in the local preview, and use zmClient?.getMediaStream()?.isSupportVirtualBackground() in session.
Is it possible/is there documentation for using zmClient?.getMediaStream()?.isSupportVirtualBackground() before calling zmClient.join()? I would appreciate it if you could let me know if this approach is possible (I got a CORS error in the console when trying this: Access to XMLHttpRequest at ‘https://log-external-gateway.zoom.us/meeting-external’ from origin [redacted] has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.)
Sorry, we’re unable to collect logs from before the user joined the session. May I know which browser the user is using? This type of error is usually related to the browser or device.
Also, zmClient?.getMediaStream()?.isSupportVirtualBackground() is only applicable in in-session scenarios.
It looks like the browser is Safari v17.6. Also, what is the best way to set can blur in the local preview? Is it ok to have it always on? Or always on except mobile?
what is the best way to set can blur in the local preview? Is it ok to have it always on? Or always on except mobile?
Virtual background is not currently supported on mobile. On Chrome and Safari 18+, virtual background is supported by default, but it is still subject to the hardware capabilities of the device, such as the GPU.
Regarding the video_vb_setting_error, looks like something similar happened to another user in session id 3APTJuUCTYuccuDmNT0z+w==
He joined with chrome (as he usually does) but since the update, he has not been able to get the local video to start and gets video_vb_setting_error. He noted that switching to using edge worked. Any chance this might provide more insight into what is going on?
I’m not sure which user in this session encountered the issue, but we found logs showing that one user did not have a dedicated GPU, while virtual background requires a GPU for rendering.
We will also optimize virtual background in preview in the next release.