![cqp recording quicksync obs cqp recording quicksync obs](https://devblogs.microsoft.com/cppblog/wp-content/uploads/sites/9/2019/03/Problems-Output-300x183.png)
- #CQP RECORDING QUICKSYNC OBS 1080P#
- #CQP RECORDING QUICKSYNC OBS DRIVERS#
- #CQP RECORDING QUICKSYNC OBS UPDATE#
- #CQP RECORDING QUICKSYNC OBS DRIVER#
Your original content will probably be at 1080p resolution, so, naturally, you’ll want all this quality in the output the question is – can your CPU handle it? If you see the message “Encoding overloaded” in OBS, your CPU is probably choking on the encoding. Since OBS records your screen in real time, CPU usage rises significantly with the number of pixels your processor has to handle for each frame. But what i posted here has nothing to do with that test since BF4 is a "less demanding game" and caused no problems to OBS.The resolution is a key factor that determines CPU usage. Just to be clear i'm the guy than make the VCE 2.0 video at Reddit. In the less demanding games OBS cause no hassle. There was already in past NVENC users complaining about OBS with too much duplicated/skipping frames against what Shadowplay was capable to do without loosing too much frames, since there always has some loses like 2-4 frames for second in a 60fps recording but OBS in heavy games cause too much loss. With Witcher 3 samething, with Win10DVR duplicated frames pratically disappear while with OBS has some randomly. I suspect it's the case about Win10DVR having better frame capture(lower latency/delay) than OBS has.
![cqp recording quicksync obs cqp recording quicksync obs](https://obsproject.com/forum/data/avatars/m/269/269948.jpg)
Using Win10DVR in AotS it duplicated only 3 of 60 frames at first second and duplicated 8 frames of 60 in the next second. In Witcher 3 game capture cause some duplicated frames but not too much like AotS, once every 5 frames sometimes after 10 frames, recording with fps unleashed. If i change from game capture to display capture then the duplicates decrease, yet dont look good enough but it decrease to something like 1x duplicated per frame what make playback feel smoother than game capture. So for start in AotS if i use game capture with VCE or Quicksync it duplicate same frame for like 3-4x consecutive causing video playback to look like 10fps. Just making some tests with Witcher 3 and Ashes of the singularity which are heavy CPU/GPU games, i pick that games because they are very hard to record with OBS/VCE without performance problem. I seeing the rx480 guys complaining about frameskipping/duplicate frames than the recording/encoding is causing so i decided to make some tests here to share something about VCE2 at least, probably is not samething to VCE3+. I want to share some findings about performance, i will post here if you think is not appropriate can move/delete. The day 1.4.0 + 16.11.1 come out i tested and it caused a targeted 15Mbit/s VBR to become 31Mbit/s output, so because that i get some concerns at that time, but this dont happens anymore. Just tested and was working fine, bitrate target was 50Mbit with 70Mbit peak and average bitrate becomes 40Mbit. VBR is already working properly in VCE2, the problem you guys are finding with VCE3+ is not a concern in VCE2. Only downside than CQP is totally broken now, encoder refuse to start with CQP enabled:ġ4:47:57.662: - d3d11 capture freed -ġ4:47:58.247: d3d11 shared texture capture successfulġ4:48:02.315: Starting up.ġ4:48:02.315: Plugin::AMD::VCEEncoder::VCEEncoder Initializing.ġ4:48:02.324: Plugin::AMD::VCEEncoder::VCEEncoder Initialization complete!ġ4:48:02.336: Plugin::AMD::VCEEncoder::SetTargetBitrate Setting to 0 bits failed with error AMF_OUT_OF_RANGE (code 5).ġ4:48:02.393: Warning: SetProperty TargetBitrate failed in AMFPropertyStorageExImpl with return code:0x5ġ4:48:02.545: Exception: Plugin::AMD::VCEEncoder::SetTargetBitrate Setting to 0 bits failed with error AMF_OUT_OF_RANGE (code 5).ġ4:48:02.545: Unable to create Encoder, see log for more information. 1.4.1.0+0.16.4 fixed B-frames problem for CBR, VBR_Latency and Peak constrained all of them working properly here.
![cqp recording quicksync obs cqp recording quicksync obs](http://www.wombaz.de/uploads/2014/09/qs2.jpg)
#CQP RECORDING QUICKSYNC OBS DRIVERS#
VCEencc was causing same image glitch too with b-frames added in previous AMD drivers so 16.11.1 fixed it there too. VCEencc even using old SDK is producing fine output with 3 b-frames without image glitch or framerate. In OBS Media foundation using b-frames video output is fine too besides MF cause MPC-HC to read fps wrong but real fps is right.
![cqp recording quicksync obs cqp recording quicksync obs](https://i.ytimg.com/vi/Cuh2jWn4SDU/maxresdefault.jpg)
But now recording with b-frames >0 in AMF encoder video output become very laggy at 16fps only(should be 59.940).
#CQP RECORDING QUICKSYNC OBS DRIVER#
B-frames were causing this flickering image glitch since some recently AMD driver like you already reported and 16.11.1 fixed the image issue.
#CQP RECORDING QUICKSYNC OBS UPDATE#
Second issue with update on b-frames for VCE2 in 16.11.1. VCEencc and OBS Media Foundation VBR still work like before with new driver so i guess new plugin version messed things up. Now it always record average of 31Mbit/s. It always produced average and max bitrate exactly what i specified in AMF encoder. So VBR(peak constrained) used to work before latest update 16.11.1+1.4.0 with my VCE 2.