# Zoom Meeting SDK SourceId and node\_id inconsistancy

**URL:** <https://devforum.zoom.us/t/zoom-meeting-sdk-sourceid-and-node-id-inconsistancy/105284>\
**Category:** Meeting SDK\
**Created:** [March 8, 2024, 8:15am UTC](https://devforum.zoom.us/t/zoom-meeting-sdk-sourceid-and-node-id-inconsistancy/105284 "2024-03-08T08:15:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![striver.strikes](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/striver.strikes/32/51695_2.png) [@striver.strikes](https://devforum.zoom.us/u/striver.strikes)\
**Post date:** [March 8, 2024, 8:15am UTC](https://devforum.zoom.us/t/zoom-meeting-sdk-sourceid-and-node-id-inconsistancy/105284/1 "2024-03-08T08:15:17Z")

</div>

For a single user,  
data-\>GetSourceID() Gives a different id than the node\_id for the audio renderer

I am using this function for audio  
void ZoomSDKAudioRawData::onOneWayAudioRawDataReceived(AudioRawData\* audioRawData, uint32\_t node\_id)

This is what I am doing for video  
void ZoomSDKRenderer::onRawDataFrameReceived(YUVRawDataI420\* data)  
{ sourceId = std::to\_string(data-\>GetSourceID());  
}  
node\_id is different from the GetSourceId for video.

FYI node\_id seems to be correct

---

<div class="post-metadata">

**Author:** ![striver.strikes](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/striver.strikes/32/51695_2.png) [@striver.strikes](https://devforum.zoom.us/u/striver.strikes)\
**Post date:** [March 10, 2024, 12:34pm UTC](https://devforum.zoom.us/t/zoom-meeting-sdk-sourceid-and-node-id-inconsistancy/105284/2 "2024-03-10T12:34:10Z")

</div>

[chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom) Can you look into this and explain what’s going on?

---

<div class="post-metadata">

**Author:** ![jake-recall-ai](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jake-recall-ai/32/57607_2.png) [@jake-recall-ai](https://devforum.zoom.us/u/jake-recall-ai)\
**Post date:** [March 15, 2024, 6:52pm UTC](https://devforum.zoom.us/t/zoom-meeting-sdk-sourceid-and-node-id-inconsistancy/105284/3 "2024-03-15T18:52:34Z")

</div>

Hey Stiver!

We’ve run into a similar issue before. We run meeting bots at very large scale and use this SDK as well.

Our solution to this is that we actually don’t use GetSourceID - instead, we have a separate instance of the ZoomSDKRenderer for each video stream that we’re subscribing to. With this implementation, we don’t need to know which stream it’s for since we already know the stream ID when we create it.

Hopefully this helps.

Another alternative is to use [Recall.ai](https://www.recall.ai/)for your meeting bots instead. It’s a simple 3rd party API that lets you use meeting bots to get raw audio/video from meetings without you needing to spend months to build, scale and maintain these bots.

Let me know if you have any questions!
