Owncast port 1935 with OBS

[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.

[RazielKanos]

Port 1936 still isn't working for me – OBS refuses to connect – do I have to open the port somewhere else?

[robi]

@RazielKanos said in Owncast port 1935 with OBS:

Port 1936

193-5 you mean?

Or perhaps you changed it in your install?

[RazielKanos]

@robi
I changed it during the installation since 1935 is used by peertube

[girish]

@RazielKanos I would test with port 1935 + OBS. Does OBS allow specifying a port in the first place? Any screenshots?

[RazielKanos]

@girish
I can connect via port 1935 and OBS to peertube. that works like a charm, and i did my livestream on my peertube instance, butowncast, still says no on any other port i tried so far

[girish]

@RazielKanos yeah, I think it's a client side issue that non 1935 ports don't work. I recall having this discussion somewhere.

[RazielKanos]

@girish said in Owncast port 1935 with OBS:

@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.

You said that in this topic in May last year

[girish]

@RazielKanos right.. we fixed the package to listen on any port However, I don't think most clients support them. Maybe we should add a note in the docs about this.