Is the “Virtual Machine” issue related to the Zoom SDK’s internal implementation, or is it dependent on the client-side environment?
It’s related to the virtual machine as well as our implementation — we’re actively working on fixing this issue.
is there any way to mitigate or reduce the frequency of this bug on the client side while waiting for a fix in the upcoming version?
Specifying video_webrtc_mode: 1 in the JWT explicitly enables WebRTC video, which can indeed help with video rendering on virtual machines that lack physical GPUs. However, in this mode, you’ll need to adjust your video rendering implementation:
Use attachVideo() instead of renderVideo() for rendering video.
Thanks
Vic