I think it's ready.
Discussion
yaa, that's good news. I've been working to get it going already, I’m integrating simulcast into a self-hosted web player using hls . js
The status API works correctly through my server proxy. When a stream is live, the API returns something like:
{
"isLive": true,
"hlsUrl": "https://simulcast.me/hls/.../index.m3u8?apiKey=..."
}
If I open the hlsUrl directly in a browser, I see a valid HLS manifest (#EXTM3U, segment_XXX.ts, etc.), so the HLS pipeline itself is working.
However, when hls . js inside my web player tries to load that same URL, I get:
HLS error: manifestLoadError
This usually happens when the HLS endpoint does not send CORS headers, preventing browsers from fetching the manifest via XHR/fetch.
Would it be possible to enable CORS on the HLS endpoints (for example, Access-Control-Allow-Origin: *)?
This would allow web players using hls . js to load the manifest and segments correctly.
Give it another try. Thanks for testing it and finding the errors I missed.
no problem, I've been testing all other stream services, happy to help,
I tested the hls stream again after your change.
The good news, my web player can now request the manifest, so cors is definitely working.
However, I’m seeing a few new issues when streaming from OBS,
The stream comes online, then drops offline
Sometimes it appears in the player for a moment, then the player reports the stream as offline again. A few seconds later it may come back, then drop again.
hls buffer append error & Autoplay failed: DOMException: The fetching process for the media resource was aborted
hls buffer append error
It looks like the manifest loads correctly, but some of the .ts segments might be failing intermittently, which triggers hls . js to treat the stream as broken and drop back to “offline.”
summary
OBS to Simulcast detects “stream online”
Player starts loading segments
Buffer append fails intermittently
hls . js recovers - fails - recovers - fails
(stream flickers online/offline)