Peas4lunch
New Member
Log File: https://obsproject.com/logs/KYq2PgWwSmnpX79U
I'm at my wits end, i've been messing with settings like crazy!
I'm at my wits end, i've been messing with settings like crazy!
I keep dropping frames and its driving me crazy! Please Help!
- Thread starter Peas4lunch
- Start date
You try to drive a Formula 1 Race with a regular 5th hand 500$ street car.You Real wonder why there all x3 faster then you?'
The system have to less power to handle this job.
there is a chance that if you try use AMF and not x264 that it can work, need to test
the system is hard below "good for this type of work"
The system have to less power to handle this job.
there is a chance that if you try use AMF and not x264 that it can work, need to test
the system is hard below "good for this type of work"
Peas4lunch
New Member
To stream from a capture card? I didn't figure you'd need a $1200 gaming rig.
FerretBomb
Active Member
Real-time video encoding is EXTREMELY computationally demanding regardless of the initial source, especially at the low bitrates necessitated by livestreaming to a remote server. nVidia has a dedicated section of their GPUs just to handle it. AMD kind of half-assed one, but it's absolutely garbage.
All that said, dropped frames (not skipped frames or frames lost due to encoder lag) are always a network issue.
This is a problem with your connection to the server. Either you don't have the bandwidth to support the bitrate you're trying to stream at, or your connection has packet loss issues.
Peas4lunch
New Member
I did notice this, and this would make the most sense. My ISP suddenly started giving me issues a while back that i've been dealing with it just hasn't been as frequent as these stream tests. Besides that, I streamed a game from my computer without the capture card for two hours yesterday and didn't have a single issue. I don't know where to hammer this thing down. Thanks for the sensible reply.
FerretBomb
Active Member
You can install a piece of software called PingPlotter (they have a free version) and point it at the ingest you stream to. Just leave it running while you stream. At the end, check the window on the PL (packet loss) column. The first node in the chain with a number is having a problem, and the first place to check. If it's your modem/router, try power-cycling it (you can do that preemptively, but I usually nail the problem down first rather than just looking for a fix). If it's upstream from you, you'll have to talk to your ISP. But it'll give you information where the problem is happening... it can narrow things down to if it's inside your home network, on the line from your house to the local concentrator, or somewhere upstream.
It also arms you with information, and makes your ISP take you more seriously if you say "I'm showing 2% packet loss on the route node at [IP address]". It also can help them know where to start looking, if it IS a problem on their intranet. Of course, it could always be out of their control, further up the backbone or even the destination server itself crapping out. But yeah, first step to fixing is gathering information. :)