Hello everyone,
I tried for a few months to "debug" the sporadic stream disconnects and now have to bother you guys here.
The log here: https://gist.github.com/490f314269720df25866 is one of quite a few. Sometimes it works flawlessly for hours, sometimes it dc's twice in an hour.
It happens on twitch and hitbox servers and seems unrelated to opencl=true x264 parameter.
Main "problem" as far as I think:
What exactly is happening with the FD_CLOSE? Is it a server side command which forces the dc? Why is the buffer empty? For pretty much everyone else I saw on the threads here, there was something in it.
Any input is appreciated, as I tried everything I could think of and what is to be found in threads here to fix the issue.
What I did:
I tried for a few months to "debug" the sporadic stream disconnects and now have to bother you guys here.
The log here: https://gist.github.com/490f314269720df25866 is one of quite a few. Sometimes it works flawlessly for hours, sometimes it dc's twice in an hour.
It happens on twitch and hitbox servers and seems unrelated to opencl=true x264 parameter.
Main "problem" as far as I think:
Code:
17:50:13: RTMPPublisher::SocketLoop: Received FD_CLOSE, 2 ms since last send (buffer: 0 / 335872)
17:50:13: RTMPPublisher::SocketLoop: Aborting due to FD_CLOSE, error 0What exactly is happening with the FD_CLOSE? Is it a server side command which forces the dc? Why is the buffer empty? For pretty much everyone else I saw on the threads here, there was something in it.
Any input is appreciated, as I tried everything I could think of and what is to be found in threads here to fix the issue.
What I did:
- different Modem
- different Ingest/whole different platforms
- different bitrates, fps, resolution and custom x264 encoder settings
- different Intel Network drivers (Generic Microsoft and Intel ones)
- everything else in the "drop frames dc issue thread"
- tried the AMD VCE fork but not enough to get some good tests going, will do so however
Last edited: