# \[beta testing\] nodes for live streaming mp4 **URL:** \ **Category:** Share Your Nodes\ **Created:** [4 October 2020 23:35 UTC](https://discourse.nodered.org/t/beta-testing-nodes-for-live-streaming-mp4/33743 "2020-10-04T23:35:12Z")\ **Posts on this page:** 1\ **Showing post:** 86

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\ **Post date:** [19 October 2020 09:28 UTC](https://discourse.nodered.org/t/beta-testing-nodes-for-live-streaming-mp4/33743/86 "2020-10-19T09:28:50Z")

> [@SuperNinja](#): > > To overcome this, I display my cameras in tabs (groups): when I deploy the tab the flow is started. When I close the tab, the stream is killed. Managed by "ui\_control node" which detects when a group changes state. That is indeed a nice solution. But if we are building a UI node, it would be nice IMHO to have this functionality in the node. Because that keeps our flows simple. I mean a checkbox _"don't push data if widget not visible"_. Then you can keep sending messages (containing m4 fragments) to the UI node, but they won't be pushed to the dashboard when the widget is not visible at the moment. Although I'm not sure (I'm not at my computer) whether it is possible currently - in the server side `beforeEmit` function - to stop a message from being send to the client. See the feedback from @dceejayin this [discussion](https://discourse.nodered.org/t/validate-input-message-in-ui-node/11393/5), where is advised to send a message containing e.g. null in those cases. But perhaps that is possible meanwhile... Anyway perhaps I'm going too much of topic now. If my proposal makes sense (and need further discussion), we better split this into a separate topic... --- _[View the full topic](https://discourse.nodered.org/t/beta-testing-nodes-for-live-streaming-mp4/33743)._