As mentioned in a few threads, @richard1 and I are the developers of the ZoomOSC application, hence our regular use of this forum! I am going to try to summarize the learnings from the many posts we’ve made recently.
I think it is fair to say that while this latest SDK release has brought some important features, there have been a series of very troubling bugs that make it hard for us to meet our deadlines and deliver a functional and platform-coherent application to our customers:
As we understand it, the current and most urgent issues are:
Video filter and virtual background controls are not functional together on Windows and macOS SDKs. On Windows, users get SDK Success for calling a change but the background does not change. MacOS sees the same behaviors on video filter setting.
Active Speaker is reporting the wrong user. This is extra troublesome for us because reporting this is a central feature of our app, and the functionality will need to be removed in the next update because of this.
Audio Events do not fire on Windows. I am currently getting around this by checking audio status on all users every program loop, but that should not be needed.
Breakout room controls are completely broken on the mac, and spotty at best on Windows.
Chat All does not appear to be working
Raising hands is broken at least on macOS
And then there are some weird things, such as new interfaces for multipinning promoted in this SDK, yet multipinning is not supported in all of the use cases that the SDK calls suggest. Also, now that the order of the gallery view can be changed by the users, we really do need a platform-agnostic way of getting the order of those users. Finally, the documentation for using the SDK needs a serious reworking, particularly in the area of code-signing. The existing documentation is wrong, and my team should not have to spend countless hours trying to figure it out from scratch (but we are always happy to share the results!).
I know that the SDK is an up and coming priority for Zoom, and the great community management and responsiveness from the team here on the forum recently is great evidence of that! Unfortunately, it is hard to build an app on this platform in its current state, especially when I need to eat my words to my own customers on features that will now not be available in our app because their SDK underpinnings are bugged beyond use. A timely hotfix for the SDK on all platforms is the first step in fixing this difficult scenario.
All this said, I am optimistic for the future of this SDK and the apps we are making for it! And as Richard said recently, we are more than happy to share Liminal’s internal validation tools to the SDK team to help with testing, or to give prompt feedback on beta builds of the SDK.
Let’s work together to get this SDK up to task and deliver great functionality to our combined customer base!