Description:
We are experiencing an issue with the Zoom Windows Meeting SDK after upgrading from version V6.0.4.38187 to V6.4.6.64463 where the event related to detecting a change in the active speaker (onRenderUserChanged callback) is not triggering reliably or at all during a meeting session.
Please look into this issue, thanks!
Details:
SDK Version: 6.4.6 (latest)
Platform: Windows
Issue: The expected event for notifying when the active speaker has changed does not consistently trigger, even though audio activity is occurring and the active speaker visibly changes in the Zoom UI.
Expected Behavior: The SDK should fire the corresponding callback each time the active speaker changes.
Actual Behavior: The callback is either not triggered at all or is triggered inconsistently.
Reproducibility: The issue occurs across multiple meetings and test environments.
Troubleshooting Routes
Go to custom_ui_mgr.cpp in SDK solution
Set Debugger point for the function name : onRenderUserChanged
Run Application and filter for IVideoRenderElement as Active
The Debugger point never hits even though active speaker user changed
Device (please complete the following information):
Thanks for the context, I see you posted something similar here and while no one from the Zoom team has gotten back to you yet, I’ll do my best to help in the meantime!
It’s tough to say if this is a bug with the Zoom Windows Meeting SDK or something else. You mentioned onRenderUserChanged isn’t triggering consistently, could you test if other callbacks like onRenderDataTypeChanged is also flaky? If they are, it might point to an issue with how the SDK is initialized
While we wait for the Zoom team to weigh in, here are a couple of options to keep you moving:
Workaround: Try using onUserVideoStatusChange from IMeetingVideoCtrlEvent. It’s not as direct as onRenderUserChanged, but it might let you track video status changes tied to the active speaker
Revert back to working version: If you’re stuck and need it working ASAP, rolling back to the previous working SDK version would resolve this
I tried to upload video recording and log files. but, It does not supports to upload in this post.
Right now, I am providing a file share link where you can download and view the files.
I checked that the link related to logs and video recording was expired.
Please do refer the updated link, which has a validity of max 3 days : Unique Download Link | WeTransfer
I would appreciate it if you could prioritize this and respond shortly.
Hi @kisappdev sorry did not hear back. Can you please submit a support ticket and I will flag internally once you provide the ticket number so I can expedite?
Thank you for your earlier response and for offering to flag this internally.
As requested, I had submitted a support ticket earlier, and the internal reference number provided by Zoom Engineering is ZSEE-171421.
As per the email conversation with Zoom Support (shared below), the engineering team had identified the issue and mentioned that a fix was tentatively planned for version 6.5.10. Since the current SDK release is already version 6.6.0, could you please confirm whether this fix has now been deployed or is still pending in a future release?
For your reference, please find the complete email conversation below:
Email Conversation:
From:Elisa Levet Sent:Wednesday, July 9, 2025, 9:20 AM To:Durga Prasad Pennada Subject:Re: Follow-Up: Zoom Windows Meeting SDK onRenderUserChanged Callback Issue | 132397
Hi Durga,
Hope you’re doing well and thank you very much for your patience.
I have an update for you now.
Our Engineering team has identified the issue preventing the event from being triggered after the callback. They are targeting a fix in one of the upcoming releases (tentatively version 6.5.10), so it will take some time before the permanent solution is available. But in the meantime, they have shared this with me:
“It looks like whatever should be triggering the event which calls the callback is no longer doing so. I do have the following events which might work for our customer until we can get something released that would resolve the problem.”
virtual void onActiveSpeakerVideoUserChanged(unsigned int userid);
virtual void onActiveVideoUserChanged(unsigned int userid);
“I have verified these events on the latest build and they do work with custom UIs. The demo itself might not have everything filled in for this, but it should follow the same pattern for the other event functions in custom_ui_mgr_flow.cpp which flow back to custom_ui_mgr.cpp.”
Let me know if this helps!
— Elisa
From:Durga Prasad Pennada Sent:Wednesday, July 9, 2025, 9:20 AM To:Elisa Levet
Hi Elisa,
Thanks for the update.
Could you please let me know how to track the status update for the internal ticket number mentioned below?
Additionally, could you provide me with any information related to the expected delivery date of the fix?
I just wanted to update you on this and I was able to get some movement from our Engineering team, and they were able to mark this as a bug on our end and have opened up a bug fix request for this (ZSEE-171421 internal ticket number for reference).
I will keep pushing for this to be fixed ASAP.
— Elisa
Looking forward to your confirmation on whether this fix (ZSEE-171421) has been included in version 6.6.0 or is still pending deployment in a future SDK update.