Status
Not open for further replies.

zapoqx

New Member
There is a "Twitch" preset in the simple interface, use it..
O_o I did. That is what I said. I just didn't have a picture of it. I wasn't using the advanced section for that reason that I figured the preset as a few posts back said should detect and use what may be best for me.
 

ball2hi

Member
With certain settings the GPU gets slower and slower at encoding until eventually it just gives up. I'm not entirely sure why or how to fix it - it just happens. You can try underclocking your card back to reference, keeping it's fan always at maximum to keep it cool and forcing 3D clocks so it doesn't hiccup while encoding.
Ugh. I just had this problem happen again. 6½ hour local recording gone. I've never had this happen before, but I recently started playing CS:GO and I have my fps cap set to 999 in-game, and 71 in main menu. Maybe my fps cap of 999, or my low fps cap of 71 in the main menu is causing some issue?
 

locodicegr

Member
Ugh. I just had this problem happen again. 6½ hour local recording gone. I've never had this happen before, but I recently started playing CS:GO and I have my fps cap set to 999 in-game, and 71 in main menu. Maybe my fps cap of 999, or my low fps cap of 71 in the main menu is causing some issue?

no reason at all to cap 999.....cap 300 for cs entirely.
 

Xaymar

Active Member
I'm not sure what I'm doing wrong here, as I haven't changed any of my settings, but I'm getting massive dropped frames with 1.3.0 rc1. Bitrate skyrockets up to 10000 kb/s from 3000 kb/s as soon as I load a game, and I start getting dropped frames.

Start the game before you start OBS or find a tool that forces your GPU to always be in 3D gaming clock speeds.

O_o I did. That is what I said. I just didn't have a picture of it. I wasn't using the advanced section for that reason that I figured the preset as a few posts back said should detect and use what may be best for me.

It detects what it can and otherwise uses Twitch limits. Also sorry, i thought your post had images for the advanced one - too many people using the advanced interface without knowing shit about how to use it. You can try changing GOP Size to be larger or using a slightly larger Buffer Size than your bitrate. The exact settings to achieve maximum quality are different for everyone.
 

ball2hi

Member
Holy smokes, it happened again. Ever since I updated from Pre-7 my videos have been non-stop failing to finish through a whole recording. I am monitoring my GPU, temperatures never go above 65%, core clock never goes below 1330 (except during menu transitions, reaches 1100).

Could this be an issue with MKV? Maybe I should try reverting back to FLV. Something is just incredibly wrong, and this is getting very annoying how every stream now gets cut off on my disk. Could it be the CABAC option? I use h.264 for streaming and local encoding, perhaps having it enabled for both is a bad thing?
 

Xaymar

Active Member
You want to import a MKV in Premiere, isn´t?. You can´t do it directly.
https://forums.adobe.com/thread/998329

OBS supports remuxing, which is much more stable than directly recording to mp4. You can always redo the remux without much work - redoing a recording/stream is much harder.

No im not using premiere, im using sony vegas.
mp4 have problems with recording, better use mkv.

mkv, ts or flv. Depends on which you prefer - for me it's mkv and I mostly only test with mkv and ts.

Holy smokes, it happened again. Ever since I updated from Pre-7 my videos have been non-stop failing to finish through a whole recording. I am monitoring my GPU, temperatures never go above 65%, core clock never goes below 1330 (except during menu transitions, reaches 1100).

Could this be an issue with MKV? Maybe I should try reverting back to FLV. Something is just incredibly wrong, and this is getting very annoying how every stream now gets cut off on my disk. Could it be the CABAC option? I use h.264 for streaming and local encoding, perhaps having it enabled for both is a bad thing?

Are you on Driver Version 16.9.1? If so, make sure to first use Display Driver Uninstaller to remove the AMD driver and then install the new driver. I'm still waiting on it to happen to me so I can send AMD some memdumps (which can be >2GB in size).
 

ball2hi

Member
Are you on Driver Version 16.9.1? If so, make sure to first use Display Driver Uninstaller to remove the AMD driver and then install the new driver. I'm still waiting on it to happen to me so I can send AMD some memdumps (which can be >2GB in size).
I'm using the previous version to that. I can update, but I'm going to try disabling CABAC for my next stream. I'm getting really frustrated with losing some funny highlights. Let me go get DDU going and download the latets beta drivers.

EDIT: I've updated my drivers and updated to the newest plugin. I've disabled CABAC for both my stream and local encoder, and enabled debug tracing for my local encoder. Time to test this. Also like to point out as I don't know if it's a known issue still or not, but the the plugin is still refusing to listen to CBR. Even with "Filler Data" enabled, it drops as low as 150 kb/s during no action, and even though i have it set to 3000 bitrate with 1500 buffer, it can still jump to 4500 kb/s. Seems to hover at 3500 bitrate.
 
Last edited:

Xaymar

Active Member
Thx Xaymar!
I was upgrade my video card driver to 16.9.1 and downclock GPU to reference settings, so my streams no more freeze again.

But I have a question about quality of video at Twitch.
If I use Playclaw - I get a nice movie like this (Twitch) (Settings, Twitch Inspector)
But at OBS with settings like playclaw I get less acceptable movie (Twitch) (Settings, Twitch Inspector)

Do any one have ideas how to improve video quality?

Increase bitrate, lower QP, increase GOP Size. There are many ways to improve quality, you just have to find the one thing that you need to change.

I'm using the previous version to that. I can update, but I'm going to try disabling CABAC for my next stream. I'm getting really frustrated with losing some funny highlights. Let me go get DDU going and download the latets beta drivers.

EDIT: I've updated my drivers and updated to the newest plugin. I've disabled CABAC for both my stream and local encoder, and enabled debug tracing for my local encoder. Time to test this. Also like to point out as I don't know if it's a known issue still or not, but the the plugin is still refusing to listen to CBR. Even with "Filler Data" enabled, it drops as low as 150 kb/s during no action, and even though i have it set to 3000 bitrate with 1500 buffer, it can still jump to 4500 kb/s. Seems to hover at 3500 bitrate.
Alright so I've updated my drivers, updated the plugin, and disabled CABAC. I also wasn't even streaming this time, only local recording. It still happened!

Here is a log using debug tracing: https://gist.github.com/eed3867dac5aadc134308985944421d6

Maybe it's related to the profile level? It defaults to 5.2 in recording.

Looks like it's either that or a driver issue. If you want me to report it back to AMD, I need a full process dump of obs32.exe or obs64.exe. Simply open Task Manager, right click on obs32.exe or obs64.exe, select "Create dump file", wait, upload the file that it tells you the path of to a hoster (mediafire.com, mega.co.nz, ... - anything with dl speed above 200kbps) and then i can send it along to AMD with a log file and debug tracing active.
 

ball2hi

Member
Looks like it's either that or a driver issue. If you want me to report it back to AMD, I need a full process dump of obs32.exe or obs64.exe. Simply open Task Manager, right click on obs32.exe or obs64.exe, select "Create dump file", wait, upload the file that it tells you the path of to a hoster (mediafire.com, mega.co.nz, ... - anything with dl speed above 200kbps) and then i can send it along to AMD with a log file and debug tracing active.
It'd be incredibly odd as I haven't changed drivers, or settings. The only thing that has changed is the plugin version and the game I have been streaming. Either way, going to test 4.2 instead of 5.2 even though it's always been like that.

Do you need me to create a dump file before, after, or during streaming?
 

Xaymar

Active Member
It'd be incredibly odd as I haven't changed drivers, or settings. The only thing that has changed is the plugin version and the game I have been streaming. Either way, going to test 4.2 instead of 5.2 even though it's always been like that.

Do you need me to create a dump file before, after, or during streaming?

During streaming, as after will have already terminated the library. It needs to be after it stops sending/recording though.
 

ball2hi

Member
During streaming, as after will have already terminated the library. It needs to be after it stops sending/recording though.
That will be an issue... because I have no idea when it stops. I only find out after the fact. I guess I'll have to do a very long stream and then right before I end the stream request a dump.
 

ball2hi

Member
Here is the logs/dump:

http://www.mediafire.com/download/etotcx3r0i0r552/AMD_Plugin_Logs.zip
https://gist.github.com/anonymous/810c51895412ea527502400e7d7bc9ae

Until this is fixed I'll have to revert to older versions. Going to try this modified pre-8 you posted a while back. If that doesn't work, I'll go back to pre-7 and if that finally doesn't work then I'm not sure what's up.
 

Xaymar

Active Member
That will be an issue... because I have no idea when it stops. I only find out after the fact. I guess I'll have to do a very long stream and then right before I end the stream request a dump.
Here is the logs/dump:

http://www.mediafire.com/download/etotcx3r0i0r552/AMD_Plugin_Logs.zip
https://gist.github.com/anonymous/810c51895412ea527502400e7d7bc9ae

Until this is fixed I'll have to revert to older versions. Going to try this modified pre-8 you posted a while back. If that doesn't work, I'll go back to pre-7 and if that finally doesn't work then I'm not sure what's up.

Well, the issue is definitely not with the plugin, it looks like your GPU or Driver is in an incorrect state, I'm not entirely sure as to what could have caused it though. All I can see myself is that for whatever reason it started stacking up on packets (16 frames queued).

Edit: I'll have to forward that dump and log to AMD.
 

ball2hi

Member
Well, the issue is definitely not with the plugin, it looks like your GPU or Driver is in an incorrect state, I'm not entirely sure as to what could have caused it though. All I can see myself is that for whatever reason it started stacking up on packets (16 frames queued).

Edit: I'll have to forward that dump and log to AMD.
Alright so then it looks like we got to some conclusion, just have to find a solution. What do you mean by "state"? I made sure to use DDU before installing this current driver, same with the previous driver.
 

Xaymar

Active Member
Alright so then it looks like we got to some conclusion, just have to find a solution. What do you mean by "state"? I made sure to use DDU before installing this current driver, same with the previous driver.

It's no longer synchronous with what is being requested of it, since your output queue is larger than the input queue - this never happened in any of my tests.
 
Status
Not open for further replies.
Top