Question / Help 15.4-16.5 Quicksync issue, kbps dropped to 0 without crash
- Thread starter servcovep
- Start date
Fenrir
Forum Admin
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.
Drivers are up to date, nothing is plugged in to the igpu.
xKlokwerkz
Member
Code:
06:39:24.499: OBS 0.16.4 (64bit, windows)Manually switch to another encoder, apply your settings, and then switch back to QS. If that doesn't work try rolling back to 0.15.4 and see if the issue still persists.
https://github.com/jp9000/obs-studio/releases/tag/0.15.4
xKlokwerkz
Member
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/
Fenrir
Forum Admin
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.
xKlokwerkz
Member
Already am in the process on debugging.
@xKlokwerkz
Rolling back is generally only acceptable if there is no viable alternatives in the current version or for testing purposes. There are viable alternatives - don't use Quick Sync to stream, use another encoder. If, for some reason, someone absolutely must use Quick Sync to stream, any recommendation to rollback must come with the caution and understanding that older versions may be broken. For example, 0.15.4 lacks:
That's just a summary. There are also lots of other fixes that I didn't mention. Users should also understand that many people here may not provide support or troubleshooting for older versions of OBS. If a user is okay with those conditions, then... I guess they can rollback, but I generally wouldn't recommend it.
Rolling back is generally only acceptable if there is no viable alternatives in the current version or for testing purposes. There are viable alternatives - don't use Quick Sync to stream, use another encoder. If, for some reason, someone absolutely must use Quick Sync to stream, any recommendation to rollback must come with the caution and understanding that older versions may be broken. For example, 0.15.4 lacks:
- the Windows 10 AU workaround code
- NVENC b-frames
- NVENC profile support
- fixes for NVENC crashes
- force stopping streams/recordings
- the AMD AMF encoder
- fixes for D3D9 game capture hooks
- text source fixes
- window position preservation fixes
- improved property dialog window UIs
- DX12 game capture (experimental)
That's just a summary. There are also lots of other fixes that I didn't mention. Users should also understand that many people here may not provide support or troubleshooting for older versions of OBS. If a user is okay with those conditions, then... I guess they can rollback, but I generally wouldn't recommend it.
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?
Got a log for a 0.15.x version that shows the error occurring?
Ragnorok64
Member
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.
Yes, here it is
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.
Ragnorok64
Member
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.
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:
@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.
Yes, bandwidth is not an issue, with CBR I can stream for hours without any dropped frames.
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.
So is there anything I can do right now to make it work?