Question / Help TCP Relay with OBS
- Thread starter Fitzback
- Start date
FerretBomb
Active Member
Set up a Custom RTMP connection, and use the standard TCPRelay settings you'd otherwise plug into XSplit.
It isn't going to do much though, OBS doesn't have the connection throughput problems XSplit did/does.
It isn't going to do much though, OBS doesn't have the connection throughput problems XSplit did/does.
FerretBomb
Active Member
Why would you EVER use a 32K send buffer?
Please don't follow most guides on the internet. Most of them are full of misleading, if not outright BAD information.
Please don't follow most guides on the internet. Most of them are full of misleading, if not outright BAD information.
FerretBomb
Active Member
Post a log file, ask people to take a look and give recommendations. TCPRelay isn't a magic bullet to make your stream not-shitty, it is/was there to address a specific network problem with a specific program, which OBS doesn't have.
FerretBomb
Active Member
1250kbps really isn't enough for 720p@30; the minimum for relatively poor-quality 720p is 1500kbps, with 2000kbps being strongly advised.
It may be time to downscale to 480p, or cut to 20fps if you can't bump the bitrate. Personally I'd go to 480p in that situation, as few view Twitch in fullscreen mode, and the smaller resolution would give the potential to go down a step or even two on the x264 encoder, to deliver better quality video even if it's 480p.
Also, is there a reason you have 10 graphics captures active in one of your scenes? Any you aren't using really should be unchecked, as they'll cause overhead.
You also may want to set your webcam up as a Global Source, so it doesn't have to turn off and then back on again each time you change scenes (meaning faster scene changes, and getting the quick-fade instead of the hard cut).
Your connection did have a couple of minor network issues, but nothing to be over-concerned about... very few frames dropped, well below the level for real concern.
It may be time to downscale to 480p, or cut to 20fps if you can't bump the bitrate. Personally I'd go to 480p in that situation, as few view Twitch in fullscreen mode, and the smaller resolution would give the potential to go down a step or even two on the x264 encoder, to deliver better quality video even if it's 480p.
Also, is there a reason you have 10 graphics captures active in one of your scenes? Any you aren't using really should be unchecked, as they'll cause overhead.
You also may want to set your webcam up as a Global Source, so it doesn't have to turn off and then back on again each time you change scenes (meaning faster scene changes, and getting the quick-fade instead of the hard cut).
Your connection did have a couple of minor network issues, but nothing to be over-concerned about... very few frames dropped, well below the level for real concern.
I will lose alot of space right ? having the game in not high resolution 480p .. it's kinda ugly right ? and what do you mean 10 games capture
FerretBomb
Active Member
It won't be as high resolution at 480p, but it will look a *lot* better.
Your current 720p is low-quality due to WAY too little bitrate. Even if it has the physical dimensions of 720p, it's going to look like trash.
Think of bitrate like paint. You only have so much. So either you can paint a smaller area and make it look good, or scrape it on super-thin and patchy and looking crappy. The latter is what you're currently doing.
You have a bunch of graphics captures in one of your scenes... literally 10. That's going to cause a lot of capture overhead, unless you're actually using that many for some reason.
Your current 720p is low-quality due to WAY too little bitrate. Even if it has the physical dimensions of 720p, it's going to look like trash.
Think of bitrate like paint. You only have so much. So either you can paint a smaller area and make it look good, or scrape it on super-thin and patchy and looking crappy. The latter is what you're currently doing.
You have a bunch of graphics captures in one of your scenes... literally 10. That's going to cause a lot of capture overhead, unless you're actually using that many for some reason.