Owncast port 1935 with OBS

[micmc]

I've a dedicated server with 64Gb RAM on which I've installed an instance of PeerTube which suggests to use port 1935 by default which I'd simply accepted as is and its running PT on this port.

Now, of course when I wanted to test Owncast, this app too 'suggest' the use of the same port -1935- by default. Now, of course if you forget CR kindly reminds you that the port is already taken if you try to accept the default suggested port as is. And that's the moment where I thought "ha true, peertube is already using this port" then what would you do? Exactly, I change the port to 1936 and now it installs and works pretty well.

A nice tip here: "stream key" and admin "password" in the settings are the same so don't do as I did, on my first install. That's just before clear specifications were put in a right place, I quickly went to change the "stream key" before anything else.

It's been a reflex I believe because it's the first thing you see once you're logged in:

moreover, I would have never imagined that this key would be the same as the admin access password. I mean, I've a long career of installing software online and with keys and all that stuff and I've never seen such thing, and I must admit I think it's pretty odd.

Anyway, don't fall for it, indications should be more obvious now.

That said, when I tried to connect to Owncast with OBS it was refusing the connection, I scratched my head a little bit, and checked a few things here and there (and everywhere...) to suddenly think "am I being forced to absolutely use that port with OBS through Owncast" I'd to step back a little and test a few things.

For now, I'd finally moved my PeerTube installation to port 1936 and it works fine, however I haven't had tested the broadcasting feature yet, and so I've yet to discover if the experience will be the same with OBS while attempting to connect to PT. If anyone would share its own experience in this matter, you're more than welcome.

And I'd set back Owncast to 1935 and now it connects perfectly and quickly, and very easily and it seems fun, but I've yet to play with broadcast settings.

I've also been looking for its broadcast capacity vs hardware required, if anyone has a clue that is welcome too.

[girish]

@micmc Good catch! This is actually a bug in the package that it doesn't let you listen on anything other than port 1935. I pushed a fix now.

[LoudLemur]

That is a fantastic amount of RAM. How does having so much memory help the instance?

[micmc]

@LoudLemur said in Owncast port 1935 with OBS:

That is a fantastic amount of RAM. How does having so much memory help the instance?

Are you serious? For over 30 years being in IT industry I've always been reminded from everywhere we look, the more RAM you can afford the better performance you will always get from a rig. No? I think so

I understand your question though, and if the instance was only for PeerTube this is something we might need to measure (which I have not really) to answer your question right now, however this is a CR instance and as such there are other apps that are running on it as well.

Now, you should know that apps with dependencies that are loading in RAM to run are much faster than if it has to solicit the swap file, or at worst the HD to execute and deliver a request to the client.

Hope that helps.

[LoudLemur]

Thanks! I might have to try a few experiments to feel the difference from an end-users point-of-view.

Perhaps if there is a particularly popular video on the day, it might help make things very rapid. I think as an admin, you would have a much easier life with it in RAM.