# Live Pattern Preview Binary Frames Format

**URL:** <https://forum.electromage.com/t/live-pattern-preview-binary-frames-format/1211>\
**Category:** Troubleshooting\
**Created:** [May 4, 2021, 10:47pm UTC](https://forum.electromage.com/t/live-pattern-preview-binary-frames-format/1211 "2021-05-04T22:47:57Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![wizard](https://forum.electromage.com/user_avatar/forum.electromage.com/wizard/32/4_2.png) [@wizard](https://forum.electromage.com/u/wizard)\
**Post date:** [May 4, 2021, 11:55pm UTC](https://forum.electromage.com/t/live-pattern-preview-binary-frames-format/1211/2 "2021-05-04T23:55:27Z")

</div>

Hi @Kamehana ,  
~~  
As @Nick_W mentioned [here](https://forum.electromage.com/t/dancing-led-stickman/1210/2):~~

~~ 

> [@Dancing LED Stickman](https://forum.electromage.com/t/dancing-led-stickman/1210/2):
>
> These have the first two bytes as `(5,4)`, followed by r,g,b values as bytes.

 ~~

~~So for 60 pixels, you should have a WebSocket frame of 60 \* 3 + 2 = 182 bytes.~~

UPDATE: oops, I should have double checked. It is 60 \* 3 + 1 = 181 bytes. These don’t have the flags byte, just the type.

The rest is probably the overhead of the WebSocket protocol itself (WS has it’s own frame headers) and wouldn’t be sent to your WebSocket client application.

If you view this in your browser console’s network tab, you can see the preview frames as they stream from the browser after the websocket protocol has been decoded.

---

_[View the full topic](https://forum.electromage.com/t/live-pattern-preview-binary-frames-format/1211)._
