hls.js | JavaScript library that plays HLS | Video Utils library

I have a .mov file which I run through ffmpeg to create HLS segments / chunks. However, when I playback the HLS video it is too bright.

For a sanity check, I ran the same .mov video file through the FlowPlayer processing pipeline and the results were the same, the output video is too bright!

I have a number of videos. Most do not have this problem but some (and only some) of the .mov files exhibit this issue.

A broken video stream reports (see below for full output):

I have three HTML5 media tags. One video and two audios. I stream them by HLS. I have the following code for the HLS setup.

The audios are good on major browsers except Safari. Audios are choppy for Safari on both macOS and iOS. I wonder if I'm missing something setting up HLS?

I have:

I'm rather new to backend stuff, so please excuse, if my question is trivial.
For an Intranet project, I want to present a video element in a webpage (React, HLS.js Player).
The video sources are mpeg-ts streams delivered as udp multicast.
A small node.js / express server should handle the ffmpeg commands, to transcode the multicast to hls to display them in a browser.

Problem is the Output:
The output is emitted on stderr... even the process is working as expected.
Here is the respective code I wrote for transcoding so far:

So I have managed to inject hls.js to work with nuxtjs $root element and this

I did so doing it like this (hls.client.js):

I'm trying to convert some videos (in the different formats, e.g., mp4, mkv, avi) with multiple audio streams to HLS with only one audio. I've tried different solutions with ffmpeg but non of them seem to be ideal.

For example ffmpeg -i in.mkv -codec: copy -f hls out.m3u8 from this gist works only if in.mkv has one audio stream (at least this is my understanding).

I've then tried:

I am serving my hls videos on S3 with Cloudfront and play them with hls.js library

Sometimes I am getting CORS errors, the weird part is if I disable cache in the browser, it's working fine, but when it's use the cached version it returns the CORS error

Although WebRTC is meant for conference calls, it's possible to capture a MediaStream and use that as a source for an RTCPeerConnection. As it happens, this could be a solution to a problem I'm facing: displaying a live-stream in a WebGL app that doesn't support them.

(The idea is to use a library like HLS.js to handle assembling and remuxing the live-stream, and then stream that video into my WebGL app. The app's built in Unity, the game engine, which has introduced a package for WebRTC, so I'd be able to display that.)

According to the docs, a server is required to act as a middleman between clients. From what I understood, however, this is essentially to help them find each other and agree to connect over a P2P network. Since the two apps—the WebGL app and a Node app/JS script—live on the same client, even the same browser window, maybe I could omit the middelman and connect directly?

Unfortunately, I haven't been able to find anything regarding this method—probably because it's such an unusual use-case. Is it possible? If so, is it feasible, and how might it be done?

I've got this code and it works with the direct links. I've even got the parser working, so it pulls the free2viewtv list, however when i click on one of the links created using the parser, it doesnt work..

However if i click on 247 Retro TV, that works perfectly, i know thats due to the 247 Retro TV being the direct link.

But for the life of me, i just cannot see what is going wrong with