Avatar
mnpezz
9367a951f3e58803ab88d3053a1b7b1be4539addcec555b61cfa19c5f2397e83
supertagger

I made a plugin that uses simulcast.me api so you can self host your live streams on your wordpress websites.

https://github.com/Mnpezz/simulcast.me-Wordpress-Player

That's great news. Thanks for the thorough update. I'll work on this soon.

Replying to Avatar mar

I’m trying to play my stream from my domain using hls .js.

Your status endpoint returns:

{

"isLive": true,

"hlsUrl": "https://simulcast.me/hls/8e4551823a23f584/index.m3u8?apiKey=-zlqHdG0KoqskMKLfnCfsH9zfKZ8oOe-",

"streamKeyLabel": "test",

"playbackToken": "8e4551823a23f584",

...

}

But when my browser (or hls.js) requests that URL, I get:

Status: 404 Not Found

Content-Type: application/json; charset=utf-8

Body: JSON error (not an .m3u8 playlist)

Hls . js reports:

type: "networkError"

details: "manifestLoadError"

fatal: true

url: "https://simulcast.me/hls/8e4551823a23f584/index.m3u8?apiKey=..."

So your API says isLive: true with that hlsUrl, but the manifest URL returns 404.

Can you check why that HLS path doesn’t exist or why it’s returning JSON instead of the .m3u8 file

just a note of how its expected to work

There's a 3–5 second delay after a stream starts before the HLS URL is available. hls.js should automatically retry and connect once the files are ready.

Replying to Avatar mar

I’m trying to play my stream from my domain using hls .js.

Your status endpoint returns:

{

"isLive": true,

"hlsUrl": "https://simulcast.me/hls/8e4551823a23f584/index.m3u8?apiKey=-zlqHdG0KoqskMKLfnCfsH9zfKZ8oOe-",

"streamKeyLabel": "test",

"playbackToken": "8e4551823a23f584",

...

}

But when my browser (or hls.js) requests that URL, I get:

Status: 404 Not Found

Content-Type: application/json; charset=utf-8

Body: JSON error (not an .m3u8 playlist)

Hls . js reports:

type: "networkError"

details: "manifestLoadError"

fatal: true

url: "https://simulcast.me/hls/8e4551823a23f584/index.m3u8?apiKey=..."

So your API says isLive: true with that hlsUrl, but the manifest URL returns 404.

Can you check why that HLS path doesn’t exist or why it’s returning JSON instead of the .m3u8 file

I made a little update. hopefully it fixed the issue. I have been using https://players.akamai.com/players/hlsjs to test the hls and it seems to work fine. let me know if you still have an error.

Replying to Avatar mar

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.

i am having a strange issue where i cant open Shosho app more than once without clearing storage, which resets everything. this is on a pixel 8a. My phone has a few quirks though so maybe its just this phone.

Btw it's free for 1 platform not just 1 hour. So if you wanted to use Shosho to stream to Rumble, for example, instead of nostr you could do that with simulcast.me for free. You get charged for any additional platforms but the first platform is free indefinitely.

Hey thanks for your interest. This is not a zap stream competitor but a way to stream to multiple platforms, including nostr:nprofile1qqsv73dxhgfk8tt76gf6q788zrfyz9dwwgwfk3aar6l5gk82a76v9fgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxthwden5te0wfjkccte9eekummjwsh8xmmrd9skctcppemhxue69uhkummn9ekx7mp0dutak6 , at the same time using OBS or nostr:nprofile1qqsgthcq5tm2jxz9x4xg6tvlh26qq2actdpztwh2kc86lvjc03gr36spzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtckgrenr.

I think a better comparison would be that this is more like a nostr/Bitcoin focused version of restream io.

For the NWC I suggest using coinos.io and sending some sats from wallet of Satoshi to coinos. I like NWC for many reasons but the main one is simulcast.me does not custody your unspent sats. I'll make this more clear on the website.

Simulcast.me is looking better every day

Simulcast.me progress update:

✔ RTMP ingest

✔ HLS playback

✔ Shosho compatibility

Simulcast.me now lets you multistream directly from your phone.

If you’ve ever wished nostr:npub1sh0spghk4yvy2d2v35kelw45qq4msk6zykaw4ds047e9slzs8r4qr7q2xa could broadcast to multiple platforms… now it can.

It works. You can now stream to multiple different platforms including zap.stream.

https://github.com/Mnpezz/NodeMediaServer-Simulcast-App

nostr:naddr1qqjxverxx5cn2vtx94nxzvf5956rjc3495uk2d3j94nrzery8yuk2cmrxvunsqg4waehxw309aex2mrp0yhxgctdw4eju6t09upzpn6956apxcad0mfp8grcuugdysg44eepex68h50t73zcathmfs49qvzqqqrkvu95vu6q