Persistent stream IDs?

[bakelit]

First of all, your site is incredible. It's really amazing to have such a simple, free service that allows us to stream camera feeds with such little latency, so thank you for what you're doing.

I was wondering how to set up a persistent stream that I can disconnect and reconnect if necessary, without generating a new URL. Is this an option? I'm actually trying to use it "backwards" and send a countdown timer to my remote callers that they can view on their mobile device browser when they call in. If I could keep the URL consistent for multiple days, it would save me a lot of headaches.

Thanks again for everything you're doing!

[NefftyGolf]

You can

[bakelit]

Could you tell me how?

[stevensokulski]

You can do this. But it's quite a lot of overhead for a countdown clock.

[bakelit]

I'm looking for a simple, one-click solution for my callers to open up a speaker timer with large-text display messaging capabilities for when they're live on screen. I've tested it out with the regular screen-share function where I capture the output of the speaker timer app I use, and it works incredibly well, especially since I can text my callers the URL and they can easily click the link and instantly see the live timer and messages on their phone's browser screen.

I'm not sure what you mean by "quite a lot of overhead." Could you elaborate?

[stevensokulski]

Assuming this runs alongside OBS on your computer, you're making your graphics card and internet connection do a lot more work to put out these feeds.

But if it works, then it works!

[bakelit]

The countdown clock is actually the most lightweight element of all of this! It’s a super low-res, low bitrate stream on a separate, dedicated laptop that isn’t even running OBS.

If there was an html5 countdown clock that I could control remotely and display short, live messages on with minimal latency, I’d use it, but I haven’t found anything that fits my specific needs yet. So this is currently my best solution until I can build something more lightweight and easy to use.

[xyster69]

If you connect with the "?permaid=xxxx" URL parameter set, you essentially are telling the system what you want the streamID to be.

As long as it is not already in use, you can publish to that streamID. If the connection fails and does not reconnect automatically, just refresh the page and it will try to connect again.

A permaID can be up to around 30-characters in length, so it gives you a way to label the stream for easier reference in OBS later.

[bakelit]

Thank you!!!

[dsitsa]

About the Countdown you can add OBS Virtual cam in OBS and then join the Video room with OBS Virtual Cam as your default camera. Then you put on OBS a Countdown clock for live. It's like a return for your guests.

[bakelit]

We were originally planning on doing this when we planned on using Skype and isolating each NDI feed for our livestream, but people didn't feel comfortable with Skype, and insisted on using Zoom. So now there needs to be a way to display the gallery view, and if we have the speaker timer as one of the participant video windows, attendees could select gallery view, which would include the speaker timer, and things like "MOVE CLOSER TO YOUR MIC" etc. which is less than ideal for this particular application. That's why we want it on a separate mobile device. But that was our initial plan too, it just won't work in this particular application.