Travio
New Member
So, I've noticed since the update earlier this week, I've had some issues. I've been streaming emulated PS2 games the last couple days and have been noticing some massive stuttering going on from time to time during streams. I went through everything I could think of, assuming it was the emulator... and then happened to have my resource monitor open during one of these stutter sessions...
... and noticed that it was OBS deciding it needed to be using 85% of my CPU capacity for a brief period of time. After watching OBS during these periods where I'm noticing it massive increasing the amount of CPU it's using (my normal settings of 2000bps sit between 20 and 30% CPU), it seems that, for these very short periods of time, OBS is attempting to use a much higher bitrate - always over 8000bps and sometimes as high as 10000bps. This has only begun occurring since the update to OBS earlier this week.
This has been occurring as often as every thirty seconds for a two to five second interval.
https://gist.github.com/f18d964decc9ae9a494c - This is a log from my latest stream. I ran it through the Analyzer to see if there was any reports. It's spitting out three - streaming via Wireless (yes, I know it's not reliable, but I've done some extensive testing and it's good for what I need it until I can get a length of long enough ethernet cable, and this problem is on the local side), slow sources detected, and 1.3% dropped frames.
I tinkered around with the scenes - using only two scenes, I had a dxtory capture, a game capture, and a webcam capture, all of which are global sources (some additional graphics sources are unique to each scene). Thinking the issue might have originated from dxtory, I removed it as a source and shut down dxtory altogether and still encountered the problem - in fact, some of the worst cases, rising up to 10000bps, occurred after the dxtory shutdown.
The frames being dropped occur exclusively during the period of increased bitrate. Otherwise, I'm streaming perfectly fine with no frame loss - and have had multiple individuals check to ensure that, during periods without that spike, there's no quality degradation in the stream.
Essentially, I've narrowed it down to something within OBS causing the problem. Anyone else experiencing this or have any suggestions on how to deal with it?
I'm using a 2000 bitrate with no custom buffer, have tried both with and without minimize network impact turned on, have a base resolution of 720@30fps with no downscaling, have tried with mulithread optimization both on and off, and with a process priority of both above normal and normal.
I'm running on a Phenom II Black Edition stably OC'd to 3.6GHz, 8GB RAM, with an ATI Radeon HD 4600 (I'm aware it's old, but it works for what I'm doing). As far as I am aware, every one of my drivers is up to date.
I can confirm that I was streaming without this issue prior to the updates earlier this week; I completed the updates that OBS recommended plus updated to the most recent versions of the CLR Browser plugin.
Edit: There appears to have been a new version of OBS pushed; I haven't tested it actually streaming yet, but during a record test session just now, I managed to run half an hour without encountering this issue - so things are looking good. Will report back after I've had a chance to boot up the stream later this afternoon. Again, no changed settings from what was causing errors last night, just the new version of OBS.
Edit 2: During tonight's streaming sessions, I thought I was in the clear - two hours without a problem. Then, without warning, the stuttering began anew. It seemed to come and go, without warning or any apparent pattern, throughout the evening of streaming before vanishing entirely for an hour and a half period. Afterwards, however, it came back worse than ever. The log of tonight's stream can be found at https://gist.github.com/4cbec4044dada2c71ced - after analyzing it, I'm only getting Wireless and Slow Sources reported tonight.
... and noticed that it was OBS deciding it needed to be using 85% of my CPU capacity for a brief period of time. After watching OBS during these periods where I'm noticing it massive increasing the amount of CPU it's using (my normal settings of 2000bps sit between 20 and 30% CPU), it seems that, for these very short periods of time, OBS is attempting to use a much higher bitrate - always over 8000bps and sometimes as high as 10000bps. This has only begun occurring since the update to OBS earlier this week.
This has been occurring as often as every thirty seconds for a two to five second interval.
https://gist.github.com/f18d964decc9ae9a494c - This is a log from my latest stream. I ran it through the Analyzer to see if there was any reports. It's spitting out three - streaming via Wireless (yes, I know it's not reliable, but I've done some extensive testing and it's good for what I need it until I can get a length of long enough ethernet cable, and this problem is on the local side), slow sources detected, and 1.3% dropped frames.
I tinkered around with the scenes - using only two scenes, I had a dxtory capture, a game capture, and a webcam capture, all of which are global sources (some additional graphics sources are unique to each scene). Thinking the issue might have originated from dxtory, I removed it as a source and shut down dxtory altogether and still encountered the problem - in fact, some of the worst cases, rising up to 10000bps, occurred after the dxtory shutdown.
The frames being dropped occur exclusively during the period of increased bitrate. Otherwise, I'm streaming perfectly fine with no frame loss - and have had multiple individuals check to ensure that, during periods without that spike, there's no quality degradation in the stream.
Essentially, I've narrowed it down to something within OBS causing the problem. Anyone else experiencing this or have any suggestions on how to deal with it?
I'm using a 2000 bitrate with no custom buffer, have tried both with and without minimize network impact turned on, have a base resolution of 720@30fps with no downscaling, have tried with mulithread optimization both on and off, and with a process priority of both above normal and normal.
I'm running on a Phenom II Black Edition stably OC'd to 3.6GHz, 8GB RAM, with an ATI Radeon HD 4600 (I'm aware it's old, but it works for what I'm doing). As far as I am aware, every one of my drivers is up to date.
I can confirm that I was streaming without this issue prior to the updates earlier this week; I completed the updates that OBS recommended plus updated to the most recent versions of the CLR Browser plugin.
Edit: There appears to have been a new version of OBS pushed; I haven't tested it actually streaming yet, but during a record test session just now, I managed to run half an hour without encountering this issue - so things are looking good. Will report back after I've had a chance to boot up the stream later this afternoon. Again, no changed settings from what was causing errors last night, just the new version of OBS.
Edit 2: During tonight's streaming sessions, I thought I was in the clear - two hours without a problem. Then, without warning, the stuttering began anew. It seemed to come and go, without warning or any apparent pattern, throughout the evening of streaming before vanishing entirely for an hour and a half period. Afterwards, however, it came back worse than ever. The log of tonight's stream can be found at https://gist.github.com/4cbec4044dada2c71ced - after analyzing it, I'm only getting Wireless and Slow Sources reported tonight.
Last edited: