Discussion Locked

Zoom SDK issue: onRenderUserChanged not triggering in custom UI mode.

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

After upgrading the Zoom Windows Meeting SDK from version 6.0.4.38187 to 6.4.6.64463, the onRenderUserChanged callback in the Custom UI Manager is no longer triggering reliably. This callback is supposed to fire when the active speaker changes during a meeting session, which is critical for apps that display dynamic video layouts or highlight active participants.

Issue Observed:

The callback either doesn’t trigger at all or only fires sporadically.

The Zoom meeting UI does reflect changes in the active speaker visually, but the SDK fails to emit the expected event.

We've confirmed this behavior across multiple devices, test environments, and meeting sessions.

Troubleshooting Steps Taken:

Set breakpoints in custom_ui_mgr.cpp on the onRenderUserChanged method.

Filtered for IVideoRenderElement objects marked as Active.

Verified that audio activity was present and active speaker visually changed.

Despite this, the callback was not hit at runtime.

Expected Behavior:
Each time the active speaker changes, the SDK should invoke onRenderUserChanged to allow developers to update the UI accordingly (e.g., highlight active speaker’s tile).

Reproducibility:
This issue is reproducible on:

Windows 11 Pro

HP Devices (and others tested)

Zoom Meeting SDK 6.4.6.64463

Temporary Workaround:
We’re currently using a polling mechanism with getActiveVideoUserID() as a stopgap to detect speaker changes, but this approach is inefficient and doesn’t provide the event-driven precision needed for responsive UI updates.

Request for Input:
Has anyone else encountered this issue with the latest SDK version?
Are there any additional initialization steps required post-6.0.4 for this callback to work properly?
Any insights, confirmation from Zoom devs, or workaround suggestions would be appreciated.

6 replies

by birdmantd

You haven't provided enough information about the hardware details of the computer you are using for this. While I don't have any experience with this type of issue, I know that you need to identify the resources you are currently using to help find a solution/explanation of the issue.

by MathewCaudioo edited

You're right—hardware definitely plays a role in real-time video rendering issues. In our case, the issue has occurred across several setups including HP Spectre x360s and a couple of Lenovo ThinkPads, all running on Windows 11 with decent GPU (Intel Iris Xe and NVIDIA MX series). So far, it doesn't seem isolated to a particular config, which makes me think it's SDK-related rather than hardware-specific.

We’re building a content-rich platform around media tools and streaming tech, so this callback glitch really throws off our UI logic, especially in custom layouts.

Still hoping someone from Zoom or the community confirms whether there’s a change in how onRenderUserChanged should be initialized post v6.0.4. Meanwhile, our polling workaround works—but not ideal for production.

Appreciate your input!

by cartdaniel437 edited

Yes, seeing the same issue after updating to 6.4.6. Callback behavior is inconsistent. Using getActiveVideoUserID() with polling as a workaround too. Hoping for an official fix or guidance from Zoom devs.

by Mark Kavin

We’ve noticed the same issue after updating to 6.4.6 as well. It seems the onRenderUserChanged event isn’t firing consistently anymore. The polling workaround with getActiveVideoUserID() works, but it’s not ideal. Hopefully Zoom acknowledges this regression soon—looks like something changed in how the Custom UI Manager handles active speaker callbacks post-6.0.4.

by gracemiller8477 edited

After upgrading the Zoom Windows Meeting SDK to version 6.4.6.64463, the onRenderUserChanged callback in the Custom UI Manager no longer fires reliably when the active speaker changes, even though the Zoom UI updates correctly. This issue has been reproduced across multiple devices and environments. Current troubleshooting—setting breakpoints, checking IVideoRenderElement objects, and verifying audio activity—confirms the callback isn’t triggered as expected. As a temporary workaround, polling getActiveVideoUserID() is being used, but it’s inefficient and lacks event-driven precision. Input is requested on whether others have seen this issue, if additional initialization steps are needed post-6.0.4, or if there are recommended workarounds.

This discussion is closed to new replies.