When I try the example flow from the readme page, the "France 24 News" stream does not start playing:
First I thought that I might have setup something incorrect, but I "think" that the stream is down. Because I see this in my dashboard browser console log:
Can somebody please confirm this?
So I tried to find another public stream. The "Big Buck Bunny" stream (from this page) seems to work. But when I try the "Teers of steel" stream (from that same page), I get this in the console log:
I am now wondering if there will also be CORS policies issues when I will (later on) start creating m3u8 playlist file of my own camera's. Am I correct that this won't be a problem, since those playlists are being served via the same base path as the Node-RED dashboard. Because in that case there won't be any cross references ...
P.S. I assume the "Big Buck Bunny" stream works fine, because it responses with the following header:
From time to time I see these warnings in my browser console log:
Is that a problem, or can I ignore that?
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:
And indeed there had been a warning logged when I had installed the mp4 fragment node:
npm WARN firstname.lastname@example.org requires a peer of socket.io@2 || 3 || 4 but none is installed. You must install peer dependencies yourself.
After I installed the latest dashboard (3.0.4 with the socket.io update), those problems were solved automatically and both nodes became visible in the palette. I can understand the UI node requires the dashboard. But the other (non-ui) mp4 fragment node can also be used by folks that don't use the Node-RED dashboard. Do they need to install socket.io manually as a prerequisite? If so, that should perhaps be mentioned in the readme page.