PC Drivers & Software

[elisson]

aa I'm not able to do lives I have an rx5700 and a ryzen 1600x with 24gb of ram but when I start live in obs it appears overload in the coding I've tried everything here on the forum and it didn't solve the problem I dawngraded the drives I dawngraded in obs and nothing worked Even Kuilios' solution didn't work for me, would anyone have a definitive solution for this please help me

[elstaci]

Not really familiar with OBS and Live Plugin but I am good at googling information.

Is this the Live Plugin you are using: https://support.streamelements.com/hc/en-us/articles/18771457842066-SE-Live-Overview

Supported Platforms

SE.Live is currently only supported on Windows operating systems. Support for SE.Live on Mac operating systems has been discontinued.

FAQs

• Q: Can I use SE.Live to stream to multiple platforms?
  A: SE.Live itself does not enable multi-platform streaming. However, it does provide multi-platform chat functionality via the multi-chat dock, allowing you to view and chats from different streaming platforms within OBS.
• Q: What happens if I have issues with OBS and SE.Live?
  A: We recommend that you take a look at our dedicated article about SE.Live Troubleshooting where we cover possible solutions to multiple common issues.

From the link from above website: https://support.streamelements.com/hc/en-us/articles/10474479415442-SE-Live-Troubleshooting

See if any of those issues concerns what is happening with your Live plugin.

Note: The Live Troubleshooting website has a Online Help CHAT that you might want to try and ask for their help.

Possibly it could be due to your fairly old CPU and powerful GPU Card. Just guessing though.

[VerMishelb]

It's actually an H.264 specific problem, and it doesn't depend on the power of GPU or CPU. My old setup was FX6350 + RX560 that later turned into 5900X + 6750GRE, part by part. Every combination has this issue. Even RX560 didn't have any problems recording with H.265 at QCP 21-23, and the GPU usage barely reached 50% iirc, but switch to H.264 (streaming doesn't support H.265) and you are doomed. The only solution is to fall back to software x264 and let the CPU suffer instead. At least in that case it actually works more or less fine.