Question / Help Freezing On First Frame

DeeJayhX

New Member
Specs:
i7-4790K OC at 4.5ghz (Log file shows 4ghz, but it's wrong)
2133 Mhz DDR3 (Cas 9) Ram
GTX 960 SSC

I've been recording and streaming games PERFECTLY with the settings I currently have, up until one day, without any changes, OBS decided to start freezing the video on the first frame it sees. Audio works fine. This is for recording locally, not streaming (I have a different OBS instance set up for that which has also started freezing intermittently while playing the audio fine) These settings worked just fine for months, then suddenly this crazy nonsense...

Log file:
https://gist.github.com/anonymous/befbd2bb8f8d5af1faf7
 

DeeJayhX

New Member
22 days and twice at the top of the list during peak hours and no response. Should I take this as "you're shit out of luck"?
 

dping

Active Member
22 days and twice at the top of the list during peak hours and no response. Should I take this as "you're shit out of luck"?
you are "streaming"? you are streaming at 200mbps? as in 200,000kbps? as in 25MB/s? or are you local recording? either way,

Those local recording setting you have there the qp=6 is being ignored "
x264: VBV is incompatible with constant QP, ignored."

you are duplicating up to 26% of your frames so I dont know. what else are you running? those setttings are pretty high but depending on what else your CPU is doing could make a big difference.
 

DeeJayhX

New Member
you are "streaming"? you are streaming at 200mbps? as in 200,000kbps? as in 25MB/s? or are you local recording? either way,

Streaming instance:
Max Bitrate: 3500 kb/s
Buffer Size: 3500 (not using custom buffer size)

Reocrding instance:
Max Bitrate 200,000 kb/s
Buffer Size: 200,000 (not using custom buffer size)

Those local recording setting you have there the qp=6 is being ignored "
x264: VBV is incompatible with constant QP, ignored."

No idea what that means. I assume it's not breaking anything? The qp=6 is ONLY on my recording instance. My streaming instance does not have this.

you are duplicating up to 26% of your frames so I dont know. what else are you running? those setttings are pretty high but depending on what else your CPU is doing could make a big difference.

Usually just running a game and OBS, no real intensive background tasks. Like I said it was running perfectly for the longest time with no settings changed at all. It just started freezing on the first frame out of nowhere. I wonder why 26% of my frames are duplicating... I was going to ask if it would help to post all my settings, but I'm just going to go ahead and do it.


THESE PICS ARE FROM MY STREAMING INSTANCE OF OBS, BOTH MY RECORDING AND STREAMING INSTANCES WERE WORKING FINE, AND BOTH HAVE HAD THE FREEZING ISSUE

U99Mn.jpg

qqf1y.jpg


I live in Florida, and have tried the different servers, but I used Ashburn, because it always provides the best ping

ZV8DT.jpg

1nxBG.jpg

Qd0Rt.jpg
 

dping

Active Member
Streaming instance:
Max Bitrate: 3500 kb/s
Buffer Size: 3500 (not using custom buffer size)

Reocrding instance:
Max Bitrate 200,000 kb/s
Buffer Size: 200,000 (not using custom buffer size)



No idea what that means. I assume it's not breaking anything? The qp=6 is ONLY on my recording instance. My streaming instance does not have this.



Usually just running a game and OBS, no real intensive background tasks. Like I said it was running perfectly for the longest time with no settings changed at all. It just started freezing on the first frame out of nowhere. I wonder why 26% of my frames are duplicating... I was going to ask if it would help to post all my settings, but I'm just going to go ahead and do it.


THESE PICS ARE FROM MY STREAMING INSTANCE OF OBS, BOTH MY RECORDING AND STREAMING INSTANCES WERE WORKING FINE, AND BOTH HAVE HAD THE FREEZING ISSUE

U99Mn.jpg

qqf1y.jpg


I live in Florida, and have tried the different servers, but I used Ashburn, because it always provides the best ping

ZV8DT.jpg

1nxBG.jpg

Qd0Rt.jpg
we need a log from a streaming instance where you had a problem. screen shots only show that you know the settings that are incorrect so make the recommended changes and stream for 5 minutes then post a new logfile

EDIT: if both were having the issue, then the issue would be something else changed on your system or running at the same time as OBS that is interfering with it.

probably somehting taking up CPU usage, but could be as simple as a GPU driver change.
 

DeeJayhX

New Member
we need a log from a streaming instance where you had a problem. screen shots only show that you know the settings that are incorrect so make the recommended changes and stream for 5 minutes then post a new logfile

EDIT: if both were having the issue, then the issue would be something else changed on your system or running at the same time as OBS that is interfering with it.

probably somehting taking up CPU usage, but could be as simple as a GPU driver change.

This issue has persisted across multiple GPU driver updates, and started on a driver that had worked perfectly fine for months. ( as I said a few times, nothing had changed between when it was working great and when it started freezing)

CPU usage never goes beyond 25 percent that's while streaming with the streaming instance, recording with the recording instance, and playing witcher 3 all at the same time. None of the 8 individual threads or 4 actual cores ever go above 50% usage.

What were the "recommended changes"? I didn't see anyone recommend I change anything, but I'd certainly be happy to if it would fix the issue.

While recording & streaming the witcher 3 (two different instances of OBS; one for each purpose, both with different settings) BOTH instances of OBS would freeze up at exactly the same time, this was also seen in the stream and recorded into the video file. Only the video freezes, audio keeps going fine. Appears the video likes to start recording/streaming again when I alt-tab out and go back in, or randomly start working again on it's own. It does not just do this with the witcher, even simple games with no usage. It does not happen only when I run both, I can stream, or I can record, either will freeze.

Upload bandwidth can more than handle the settings:
vANntPZr.png

Although I don't see that making a difference in this particular case.

i7-4790K and a GTX960 shouldn't have any issues keeping up either (and according to resource monitors, don't)

Here is the new log from the streaming instance, for five minutes, as requested:
https://gist.github.com/anonymous/d0d89ffc3f177a7ea166
Pertinent Part of the Log said:
22:18:21: =====Stream Start: 2015-06-30, 22:18:21===============================================

22:18:21: Multithreaded optimizations: On

22:18:21: Base resolution: 1920x1080

22:18:21: Output resolution: 1280x720

22:18:21: ------------------------------------------

22:18:21: Loading up D3D10 on NVIDIA GeForce GTX 960 (Adapter 1)...

22:18:22: ------------------------------------------

22:18:22: Audio Format: 48000 Hz

22:18:22: ------------------------------------------

22:18:22: Audio Channels: 2 Ch

22:18:22: Playback device Default

22:18:22: ------------------------------------------

22:18:22: Using desktop audio input: Speakers (4- Logitech USB Headset)

22:18:22: Global Audio time adjust: 0

22:18:22: ------------------------------------------

22:18:22: Audio Encoding: AAC

22:18:22: bitrate: 256

22:18:22: Using Window Capture

22:18:22: Scene buffering time set to 400

22:18:22: ------------------------------------------

22:18:22: Video Encoding: x264

22:18:22: fps: 30

22:18:22: width: 1280, height: 720

22:18:22: preset: veryfast

22:18:22: profile: high

22:18:22: keyint: 60

22:18:22: CBR: no

22:18:22: CFR: yes

22:18:22: max bitrate: 3500

22:18:22: buffer size: 3500

22:18:22: quality: 10

22:18:22: ------------------------------------------

22:18:22: CLRHost:: Browser 3: Status message:

22:18:23: Using RTMP service: Twitch

22:18:23: Server selection: rtmp://live-jfk.twitch.tv/app

22:18:23: Interface: Intel(R) Ethernet Connection (2) I218-V (ethernet, 1000 mbps)

22:18:24: Completed handshake with rtmp://live-jfk.twitch.tv/app in 516 ms.

22:18:24: SO_SNDBUF was at 8192

22:18:24: SO_SNDBUF is now 65536

22:18:25: RTMPPublisher::SocketLoop: Increasing send buffer to ISB 131072 (buffer: 219 / 480256)

22:18:27: RTMPPublisher::SocketLoop: Increasing send buffer to ISB 262144 (buffer: 0 / 480256)

22:18:29: RTMPPublisher::SocketLoop: Increasing send buffer to ISB 524288 (buffer: 0 / 480256)

22:23:30: Total frames encoded: 9238, total frames duplicated: 4487 (48.57%)

22:23:30: Total frames rendered: 5388, number of late frames: 79 (1.47%) (it's okay for some frames to be late)

22:23:30:

22:23:30: Profiler time results:

22:23:30:

22:23:30: ==============================================================

22:23:30: video thread frame - [100%] [avg time: 34.864 ms] [children: 98.6%] [unaccounted: 1.42%]

22:23:30: | scene->Preprocess - [97.7%] [avg time: 34.063 ms]

22:23:30: | GPU download and conversion - [0.875%] [avg time: 0.305 ms] [children: 0.711%] [unaccounted: 0.163%]

22:23:30: | | flush - [0.637%] [avg time: 0.222 ms]

22:23:30: | | CopyResource - [0.0316%] [avg time: 0.011 ms]

22:23:30: | | conversion to 4:2:0 - [0.043%] [avg time: 0.015 ms]

22:23:30: Convert444Threads - [100%] [avg time: 0.89 ms] [children: 99.7%] [unaccounted: 0.337%]

22:23:30: | Convert444toNV12 - [99.7%] [avg time: 0.887 ms]

22:23:30: encoder thread frame - [100%] [avg time: 1.005 ms] [children: 4.28%] [unaccounted: 95.7%]

22:23:30: | sending stuff out - [4.28%] [avg time: 0.043 ms]

22:23:30: ==============================================================

22:23:30:

22:23:30:

22:23:30: Profiler CPU results:

22:23:30:

22:23:30: ==============================================================

22:23:30: video thread frame - [cpu time: avg 0.402 ms, total 2168.41 ms] [avg calls per frame: 1]

22:23:30: | scene->Preprocess - [cpu time: avg 0.06 ms, total 327.603 ms] [avg calls per frame: 1]

22:23:30: | GPU download and conversion - [cpu time: avg 0.06 ms, total 327.606 ms] [avg calls per frame: 1]

22:23:30: | | flush - [cpu time: avg 0.055 ms, total 296.406 ms] [avg calls per frame: 1]

22:23:30: | | CopyResource - [cpu time: avg 0.002 ms, total 15.6 ms] [avg calls per frame: 1]

22:23:30: | | conversion to 4:2:0 - [cpu time: avg 0.002 ms, total 15.6 ms] [avg calls per frame: 1]

22:23:30: Convert444Threads - [cpu time: avg 0.927 ms, total 9968.46 ms] [avg calls per frame: 2]

22:23:30: | Convert444toNV12 - [cpu time: avg 0.923 ms, total 9921.66 ms] [avg calls per frame: 2]

22:23:30: encoder thread frame - [cpu time: avg 0.341 ms, total 3151.22 ms] [avg calls per frame: 1]

22:23:30: | sending stuff out - [cpu time: avg 0.013 ms, total 124.801 ms] [avg calls per frame: 1]

22:23:30: ==============================================================

22:23:30:

22:23:30: =====Stream End: 2015-06-30, 22:23:30=================================================

22:23:30: ~RTMPPublisher: Packet flush completed in 124 ms

22:23:30: ~RTMPPublisher: Send thread terminated in 0 ms

22:23:30: RTMPPublisher::SocketLoop: Graceful loop exit

22:23:30: ~RTMPPublisher: Socket thread terminated in 0 ms

22:23:40: ~RTMPPublisher: Final socket shutdown completed in 10163 ms

22:23:40: Average send payload: 4705 bytes, average send interval: 26 ms

22:23:40: Number of times waited to send: 0, Waited for a total of 0 bytes

22:23:40: Number of b-frames dropped: 0 (0%), Number of p-frames dropped: 0 (0%), Total 0 (0%)

22:23:40: Number of bytes sent: 54729873
 
Last edited:

dping

Active Member
This issue has persisted across multiple GPU driver updates, and started on a driver that had worked perfectly fine for months. ( as I said a few times, nothing had changed between when it was working great and when it started freezing)

CPU usage never goes beyond 25 percent that's while streaming with the streaming instance, recording with the recording instance, and playing witcher 3 all at the same time. None of the 8 individual threads or 4 actual cores ever go above 50% usage.

What were the "recommended changes"? I didn't see anyone recommend I change anything, but I'd certainly be happy to if it would fix the issue.

While recording & streaming the witcher 3 (two different instances of OBS; one for each purpose, both with different settings) BOTH instances of OBS would freeze up at exactly the same time, this was also seen in the stream and recorded into the video file. Only the video freezes, audio keeps going fine. Appears the video likes to start recording/streaming again when I alt-tab out and go back in, or randomly start working again on it's own. It does not just do this with the witcher, even simple games with no usage. It does not happen only when I run both, I can stream, or I can record, either will freeze.

Upload bandwidth can more than handle the settings:
vANntPZr.png

Although I don't see that making a difference in this particular case.

i7-4790K and a GTX960 shouldn't have any issues keeping up either (and according to resource monitors, don't)

Here is the new log from the streaming instance, for five minutes, as requested:
https://gist.github.com/anonymous/d0d89ffc3f177a7ea166

For the streaming instance, I was talking about the settings highlighted in red here:
qqf1y.jpg



None the same. So are you using a guide to capture the same game with two instances of OBS? So what you wrote was a little confusing, but what I got out of it was the freezing occurs with either instance of OBS and/or both instances, correct?



most of the guides I see have local recording instance using NVENC and a raw game or window capture then the stream instance capturing the projected image from the local recording instance. Or the windows 8.1 option is to use monitor capture for the stream instance.
 

DeeJayhX

New Member
For the streaming instance, I was talking about the settings highlighted in red here:
qqf1y.jpg

Ah, gotcha, didn't notice, but will certainly try those optimizations and see if it fixes the issue.

None the same. So are you using a guide to capture the same game with two instances of OBS? So what you wrote was a little confusing, but what I got out of it was the freezing occurs with either instance of OBS and/or both instances, correct?

No and Yes, respectively. Though I looked it up, and others use x264 for both.

most of the guides I see have local recording instance using NVENC and a raw game or window capture then the stream instance capturing the projected image from the local recording instance. Or the windows 8.1 option is to use monitor capture for the stream instance.

That's not the case here, although yes I have seen those setups

---

I guess my biggest issue with all of this, is that it was working so flawlessly, for months, with the same exact settings you see there. I never open the settings menu, so there was nothing changed, intentionally or accidentally, that could have affected it. Then suddenly, it just starts freezing up randomly, or sometimes it even freezes on the first frame it sees. When that happens, it doesn't fix itself like the randoms. I'll try optimization advice in red, but let me know what you think.
 

dping

Active Member
Ah, gotcha, didn't notice, but will certainly try those optimizations and see if it fixes the issue.



No and Yes, respectively. Though I looked it up, and others use x264 for both.



That's not the case here, although yes I have seen those setups

---

I guess my biggest issue with all of this, is that it was working so flawlessly, for months, with the same exact settings you see there. I never open the settings menu, so there was nothing changed, intentionally or accidentally, that could have affected it. Then suddenly, it just starts freezing up randomly, or sometimes it even freezes on the first frame it sees. When that happens, it doesn't fix itself like the randoms. I'll try optimization advice in red, but let me know what you think.
I honestly think it could be maybe something with stability. This often happens in general while moving into summertime, I'm honestly not saying this as an excuse but something is always changing and to be considered.

in IT, out of 1500 computers in the winter I will have 5 systems have stability issues, but in the summer that number is closer to 100 systems. along with other factors. both heat and voltage at the wall can change and will cause the majority of stability issues.

TL;DR, dont rule out anything for being a factor with streaming/recording.


On another subject, with OBS MP, has built in streaming and recording at different bitrates and resolutions. the fps have to be the same but feel free to experiment with the new build instead of using two instances of OBS.

https://obsproject.com/forum/threads/latest-windows-test-build-0-10-1.23342/

NVENC or quicksync aren't built in yet but doing it this way might bring down your usage, YMMV.
 

DeeJayhX

New Member
I honestly think it could be maybe something with stability. This often happens in general while moving into summertime, I'm honestly not saying this as an excuse but something is always changing and to be considered.

in IT, out of 1500 computers in the winter I will have 5 systems have stability issues, but in the summer that number is closer to 100 systems. along with other factors. both heat and voltage at the wall can change and will cause the majority of stability issues.

TL;DR, dont rule out anything for being a factor with streaming/recording.

Yea I'm an IT guy too, and take great care of my equipment. I tried monitoring temps to see a difference, and it's marginal. Maybe a 1' celcius increase over 15 minutes of streaming, and for all we know that's just a change in ambient temps. I live in FL so the temps have been pretty consistent. I air condition the room my system runs in 24/7 and clean my hardware 1-2 times a months. I don't think voltage is a factor here, but who knows, I'm open minded.

On another subject, with OBS MP, has built in streaming and recording at different bitrates and resolutions. the fps have to be the same but feel free to experiment with the new build instead of using two instances of OBS.

https://obsproject.com/forum/threads/latest-windows-test-build-0-10-1.23342/

NVENC or quicksync aren't built in yet but doing it this way might bring down your usage, YMMV.

That is certainly interesting, and I may just give it a try to be done with this craziness. I was going to uninstall/reinstall, and start fresh, but I figured what's the point it may just do it again in a month. The real reason I had it set up this way was so I could stream 720p (to make it widely available on twitch) and record 1080p@60 and get recordings that were as if the game was actually being played for youtube.
 
Top