# Issues while experimenting with node-red-contrib-ui-mp4frag

**URL:** <https://discourse.nodered.org/t/issues-while-experimenting-with-node-red-contrib-ui-mp4frag/51257>\
**Category:** General\
**Created:** [19 September 2021 21:13 UTC](https://discourse.nodered.org/t/issues-while-experimenting-with-node-red-contrib-ui-mp4frag/51257 "2021-09-19T21:13:46Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**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 September 2021 21:13 UTC](https://discourse.nodered.org/t/issues-while-experimenting-with-node-red-contrib-ui-mp4frag/51257/1 "2021-09-19T21:13:47Z")

</div>

Hi folks,

I started playing with the [node-red-contrib-ui-mp4frag](https://github.com/kevinGodell/node-red-contrib-ui-mp4frag) node of @kevinGodell, but I have a few beginner issues:

1. When I try the example flow from the readme page, the _"France 24 News"_ stream does not start playing:

2. So I tried to find another public stream. The _"Big Buck Bunny"_ stream (from this [page](https://ottverse.com/free-hls-m3u8-test-urls/)) seems to work. But when I try the _"Teers of steel"_ stream (from that same page), I get this in the console log:

3. From time to time I see these warnings in my browser console log:

4. I installed both mp4 frag nodes from Github, but they didn't became visible in my flow editor palette. After a while I saw (via _"Manage palette"_) that there was an issue:

Thanks !!!!  
Bart

---

<div class="post-metadata">

**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 September 2021 21:55 UTC](https://discourse.nodered.org/t/issues-while-experimenting-with-node-red-contrib-ui-mp4frag/51257/2 "2021-09-19T21:55:32Z")

</div>

> [@BartButenaers](#):
>
> Am I correct that this won't be a problem

Seems indeed that there is no problem to watch the same _"Teers of steel"_ stream, when I capture that same stream with ffmpeg and then stream if (via the node-red-contrib-mp4frag) node and fetch if by the node-red-contrib-ui-mp4frag node on my dashboard. So question 2 is answered already....

---

<div class="post-metadata">

**Author:** ![kevinGodell](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kevingodell/32/27040_2.png) [@kevinGodell](https://discourse.nodered.org/u/kevinGodell)\
**Post date:** [20 September 2021 11:11 UTC](https://discourse.nodered.org/t/issues-while-experimenting-with-node-red-contrib-ui-mp4frag/51257/3 "2021-09-20T11:11:33Z")

</div>

> [@BartButenaers](#):
>
> When I try the example flow from the readme page

You know me, I am not good with updating readme files. i should probably empty the file so that it is not keeping stale info.

> [@BartButenaers](#):
>
> wondering if there will also be CORS policies issues when I will (later on) start creating m3u8 playlist file of my own camera

it will not be an issue. Somebody probably noticed that those video streams were being accessed a little too much and tightened the access restrictions a little. But of course, the CORS thing is easily bypassed on the server side, since it is your browser that is trying to follow the headers from the server and keep you from being a bad boy.

> [@BartButenaers](#):
>
> From time to time I see these warnings in my browser console log

There used to be many, many more. i have slowly removed some debugging info as it has become more stable, but I still suggest using anything other than the socket\_io player. It became too much of an issue trying to keep track of the ever-changing socket. io versions and its feature changes while maintaining various browser compatibility.

> [@BartButenaers](#):
>
> After I installed the latest dashboard

Are you planning on using it anytime soon without having the dashboard? I was waiting for somebody to ask, but it seems that everybody uses node-red-dashboard that is using my nodes, so I haven't made the planned changes because it would require a big rewrite of the node. Although, I did rewrite the http routes recently in anticipation of the changes.

- 

The plan is that the serving of hls.m3u8, video.mp4, and socket\_io should each be an option in the node to turn on or off. socket\_io will also become an optional dependency instead of a peer dependency. It is possible to have a need to use node-red-contrib-mp4frag without ever hosting the video. It can be used to just output the buffer on the 2nd output, along with some other undocumented things that I am working on.

---

<div class="post-metadata">

**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:** [20 September 2021 15:17 UTC](https://discourse.nodered.org/t/issues-while-experimenting-with-node-red-contrib-ui-mp4frag/51257/4 "2021-09-20T15:17:17Z")

</div>

@kevinGodell : Thanks for your time to post feedback !

> [@kevinGodell](#):
>
> Are you planning on using it anytime soon without having the dashboard?

No no. I was just wondering that you should perhaps add a warning to your readme, that [socket.io](http://socket.io) should be installed manually if no Node-RED dashboard has been installed. It was only a tip 😉

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [19 November 2021 15:17 UTC](https://discourse.nodered.org/t/issues-while-experimenting-with-node-red-contrib-ui-mp4frag/51257/5 "2021-11-19T15:17:52Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.