Question / Help Quick Sync output and corrupted pixels

[Vanille]

Hi!
Let's get straight to the problem:
I can record using quick sync 2560x1080 (21:9 monitor), 60fps @20k bitrate or whatever i decide to use and I can watch the output video without problems as long as I don't use the timeline. For example if I decide to go 20 seconds in the video that's the result I'll get for a couple of seconds http://image.prntscr.com/image/6e31dbc62631414cbb92f60a93df0414.png.
The same thing happens whenever I try to edit said video (sony vegas, after effects...hell even windows movie maker) as I can't cut, change the speed or do anything to the video or it'll "corrupt" that part.

Last log: https://gist.github.com/anonymous/0072447452259f1b21a1e5ec65c48d9a
Current log: https://gist.github.com/170ff908beb6c99bc7d0809968d632a4
Video made showing the problem (around 13 seconds): https://www.youtube.com/watch?v=rUtvDmt8Pj0

P.s. I have a 2 monitor setup, 1 connected to the gpu and one connected to the mobo (had this problem with quick sync even when i had both connected at the gpu or when i had only 1 monitor, thought i would share)

 

[Fenrir]

Why are you using CBR for local recordings? Strongly suggest you try the recording presets in simple output mode and see how they work for you.

 

[Vanille]

Why are you using CBR for local recordings? Strongly suggest you try the recording presets in simple output mode and see how they work for you.

Because using an higher encoding method while giving me better quality makes it almost impossible to edit because of that problem.
Also tried the simple output mode with no luck unfortunately

 

[Fenrir]

Sounds like you might be overloading your PC then. Have you monitored CPU/GPU usage during a stream to see if there's a correlation in spikes and the issue in the recorded files? From the example, it just looks like QuickSync is unable to keep up.

 

[Vanille]

Sounds like you might be overloading your PC then. Have you monitored CPU/GPU usage during a stream to see if there's a correlation in spikes and the issue in the recorded files? From the example, it just looks like QuickSync is unable to keep up.

Just tested to be sure, looks like it's not even that S:
90-120 fps
CPU: 51 c° - 50%~ usage (7gb ram)
GPU: 71 c° - 75%~ usage (2gb vram)
Intel gpu: 70-90% usage, sometimes 100% (255mb peak vram).

I tried doing shorter and longer video with almost no movement at all and the intel gpu sitting at 50% usage, the problem persists. I can watch the video without a single problem granted I just watch it (not using the timeline, no editing, nothing).
I'd use the amd codec but can't record at any resolution higher than 1920x1080

 

[Fenrir]

Sadly, I'm out of ideas then. I noticed that your logs are still 0.16.6, would recommend you update to 17.0.0 as there were several (seemingly unrelated, but who knows!) QuickSync bug fixes in that release.

 

[Vanille]

Sadly, I'm out of ideas then. I noticed that your logs are still 0.16.6, would recommend you update to 17.0.0 as there were several (seemingly unrelated, but who knows!) QuickSync bug fixes in that release.

Nope S: guess i'll just leave with that, thanks for the help nonetheless!

 

[Vanille]

Well fixed...if only I knew this before took months and it was so easy >.>
Record in FLV and remux in MP4 using obs (file-->remux recordings), a couple of seconds and you're done!

 

[Fenrir]

Recording to FLV and remuxing after is definitely the preferred method, as mp4 files are notoriously fragile when being recorded directly to. Glad you got everything working!