# Color issue on the subscribing side

**URL:** <https://devforum.zoom.us/t/color-issue-on-the-subscribing-side/132672>\
**Category:** Video SDK\
**Created:** [May 12, 2025, 3:09pm UTC](https://devforum.zoom.us/t/color-issue-on-the-subscribing-side/132672 "2025-05-12T15:09:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hale](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/hale/32/49432_2.png) [@Hale](https://devforum.zoom.us/u/Hale)\
**Post date:** [May 12, 2025, 3:09pm UTC](https://devforum.zoom.us/t/color-issue-on-the-subscribing-side/132672/1 "2025-05-12T15:09:44Z")

</div>

I use Zoom Video SDK 2.2.0 on apps running iOS 18.x.

ZoomVideoSDKVideoSource is used to send pure white video frames (converting BGRA(255, 255, 255, 255) → I420 (0xEB, 0x80, 0x80)) and use ZoomVideoSDKVideoSender to transfer the video frames.

On the receiving side, ZoomVideoSDKRawDataPipeDelegate is used to inspect the received the video frames. The color is I420(0xD9, 0x80, 0x80). I would expect subscribing side get a color (Y) close to 0xEB.

Is this an expected behavior? Is there a way to receive a value close to 0xEB?

---

<div class="post-metadata">

**Author:** ![Hale](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/hale/32/49432_2.png) [@Hale](https://devforum.zoom.us/u/Hale)\
**Post date:** [July 17, 2025, 3:48am UTC](https://devforum.zoom.us/t/color-issue-on-the-subscribing-side/132672/2 "2025-07-17T03:48:42Z")

</div>

```auto
        [self.rawDataSender sendVideoFrame:(char*)frameBytes.bytes
                                     width:frameWidth
                                    height:frameHeight
                                dataLength:frameBytes.length
                                  rotation:rotation
                                    format:ZoomVideoSDKFrameDataFormat_I420_Limit];

```

Set the format to ZoomVideoSDKFrameDataFormat\_I420\_Limit doesn’t work. Zoom Video SDK still encode the video using full range, since of the video range.

My workaround is to convert a frame from video range to full range before sending it to rawDataSender