MartinKing
New Member
Hi,
since OBS is constantly crashing on my "stream and play" PC I wanted to set up a fail-safe protection with two different systems and OBS. To understand my motivation: I've looked through the logfiles and OBS crashes for different reasons, sometimes just closes without "leaving" a crahs report at all.
Basically I just want to add another system PC#2 into the chain, between my main PC#1 and the upload. Both running OBS. So that if my OBS crashes on PC#1 i can simply restart it without the connection being interrupted. PC#2 should not be busy with any kind of encoding or workload, basically just passing through the encoded signal by PC#1 to Restream/Twitch and keeping the connection alive when OBS crashes on PC#1.
Any advices on how to setup a system/network like this? I imagine instead of pointing the signal towas Twitch/Restream on PC#1 I have to target the OBS on PC#1 and make PC#1 a "browser source" that gets passed to Twitch/Restream.
since OBS is constantly crashing on my "stream and play" PC I wanted to set up a fail-safe protection with two different systems and OBS. To understand my motivation: I've looked through the logfiles and OBS crashes for different reasons, sometimes just closes without "leaving" a crahs report at all.
Basically I just want to add another system PC#2 into the chain, between my main PC#1 and the upload. Both running OBS. So that if my OBS crashes on PC#1 i can simply restart it without the connection being interrupted. PC#2 should not be busy with any kind of encoding or workload, basically just passing through the encoded signal by PC#1 to Restream/Twitch and keeping the connection alive when OBS crashes on PC#1.
Any advices on how to setup a system/network like this? I imagine instead of pointing the signal towas Twitch/Restream on PC#1 I have to target the OBS on PC#1 and make PC#1 a "browser source" that gets passed to Twitch/Restream.