06:49:40.473: [qsv encoder: 'streaming_h264'] encode failed
06:49:40.490: Error encoding with encoder 'streaming_h264'
Code:06:49:40.473: [qsv encoder: 'streaming_h264'] encode failed 06:49:40.490: Error encoding with encoder 'streaming_h264'
Something happened with the quicksync encoder. Make sure your drivers are up to date, and you shouldn't have monitors plugged into both the dedicated GPU and the on-board iGPU. Move all your monitors to the actual GPU.
06:39:24.499: OBS 0.16.4 (64bit, windows)
Rolling back is never a good solution, especially right now with the Windows 10 AU causing havoc (I understand he isn't on windows 10).
Please don't suggest users roll back without a very good reason.
The quicksync code hasn't changed in ages in OBS, and certainly not between 0.15.4 and current. Have you reached out to @RytoEX to gather more information on what's actually going on? It's better to fix this, and bugs like this are usually very high priority for Jim to look at, we just need more info.
QS has multiple reported issues with 0.16.x+ but works fine on 0.15.4 as I use it myself. It's been suggested to rollback.
https://obsproject.com/forum/threads/obs-0-16-2-dropping-frames-upon-starting-stream.55465/
https://obsproject.com/forum/threads/stream-kb-s-randomly-tanks-and-stream-fails.57341
https://obsproject.com/forum/threads/obs-randomly-dropping-frames-no-obvious-culprit.56855
https://obsproject.com/forum/threads/quick-snyc-dont-work-for-stream.56973
https://obsproject.com/forum/threads/stream-disconnecting-randomly-when-using-quicksync.55551
https://obsproject.com/forum/threads/quicksync-issue.56328/
Did you uninstall .16 then reinstall the .15 version or just run the ,15 installer? When I just ran the .15 installer over my .16 installation I still had issues. I did an uninstall of .16 and installed .15.4 and managed to steam for like 8+ hours today with quicksync without issue.I did try to rollback to the 0.15 version but I've got the issue in that too, but it used to work on that before, and now it doesn't work there either. So for now I'm using x264, but I have to put it to superfast otherwise it's too much, that's why I was using quicksync.
@servcovep
Got a log for a 0.15.x version that shows the error occurring?
Did you uninstall .16 then reinstall the .15 version or just run the ,15 installer? When I just ran the .15 installer over my .16 installation I still had issues. I did an uninstall of .16 and installed .15.4 and managed to steam for like 8+ hours today with quicksync without issue.
I see, this issue just seems super weird the more I hear about it. I wish i could have reliability recreatde it so I could provide relevant logs too.No, I'm using the zip version, so not installed. Both 15.4 and 16.4 are there separately, they just use the same settings.
Just noticed your 0.16.4 log has the same error. That's a bit different from the "frame drops due to insufficient bandwidth" that I'm seeing in other logs, so I'm not sure that your issue is exactly the same.08:31:24.573: [qsv encoder: 'streaming_h264'] encode failed
08:31:24.582: Error encoding with encoder 'streaming_h264'
08:31:24.582: Called profile end with mismatching name: start("do_encode"[000007FEE5C69AE0]) <-> end("receive_video"[000007FEE5C69AF0])
Yes, bandwidth is not an issue, with CBR I can stream for hours without any dropped frames.Can anyone reproduce this in portable mode in either 0.15.4 or 0.16.5? The last user I asked had difficulty reproducing in portable mode, so I'd like to hear others' results on that.
@servcovep
From your log:
Just noticed your 0.16.4 log has the same error. That's a bit different from the "frame drops due to insufficient bandwidth" that I'm seeing in other logs, so I'm not sure that your issue is exactly the same.
Yep. Did some testing with @xKlokwerkz and @Osiris to confirm the commit where this behavior was introduced, and we reported it to Jim. He's looking into it now.Issue is still present in 16.5, actually it don't matter if it's in portable mode or not, doesn't work either way.
So is there anything I can do right now to make it work?Yep. Did some testing with @xKlokwerkz and @Osiris to confirm the commit where this behavior was introduced, and we reported it to Jim. He's looking into it now.