RTMS Video Data - User IDs appear to be swapped/mixed up between participants

Realtime Media Streams
1

App type: General app, Platform: Real-time Media Streaming (RTMS) Issue: Video data event user_id attribution

Hi everyone,
I’m working with RTMS video streaming and need to confirm expected behaviour for video data events.

Issue: We’re experiencing user_id mismatching in video data events. The camera feed from one user is being tagged with another user’s user_id, causing incorrect attribution of video streams.

Question: Should the user_id attached to each video data event match the user_id of the participant whose video stream it originates from?

What we’re seeing:

  • User A’s video feed receives User B’s user_id in the data event
  • User IDs appear to be swapped/mixed up between participants
  • This makes it impossible to correctly track individual user video streams

Expected behaviour: user_id in video data event = user_id of the video stream’s source participant

Questions:

  • Is this expected behaviour or a known issue?
  • Are there any workarounds for reliable user video stream identification?
  • Should we be using a different identifier for tracking individual video feeds?

Any insights would be greatly appreciated.
Thanks!

1 Like
2

I’m experiencing this same issue. As a temporary workaround we’re using the audio data because the user ids for that appear to be correct. @chunsiong.zoom

3

Hi @ruarim, @noah.duncan, I’ll DM you for meeting information. We’re not able to reproduce this.

1 Like
4

@ruarim there is no individual video stream right now. What you are seeing from the video stream is the active speaker view. It shows the video of the person which is set as “active speaker”

image
image733×536 63.1 KB

1 Like
5

@chunsiong.zoom Yes the video data is correct, but the user_id attached to the video event does not match the active speaker.

6

Hey @ruarim, thanks for reporting this issue.

I haven’t been able to reproduce this just yet, so I wanted to confirm some details with you.

  • Is this happening with every meeting?
  • Does this happen even with 2 participants?
  • Are you using the Node.js SDK or using the RTMS protocol directly?
  • What version of the Zoom client are you using?
  • Are you auto-starting the RTMS stream or using the Zoom Apps SDK?

Lastly, I sent you a DM where you can share any details that you don’t want to send here.

If you can share how you are configuring the video parameters or any other relevant code to reproduce the issue, please send it there.

7

Hi @ruarim @noah.duncan @davidgarthe @Jeff5 - We were able to replicate the video data active speaker label issue on our end, and you are absolutely right, this was not the expected behavior. We have shared the details with our engineering team, and they have already implemented a fix that will be rolled out at the end of this month. :smiley:

Thank you all for flagging this. Your input not only helped us identify and resolve this issue, but also highlights the real value of this developer forum. Working together makes the product better for everyone.

1 Like
8

You guys are awesome! Thank you!

2 Likes
9

We hope you continue to feel confident building with RTMS. If you experience anything else worth sharing, please do not hesitate to reach out. Thank you!

10

@JenBrissman That is amazing. We are deep in planning and are excited to launch with RTMS! So that we can get our timing down, do you think the update will drop on the 30th? Thanks again! @davidgarthe

11

Awesome - so glad to hear it! This is slated to be fixed on your end BY September 30th.

1 Like