Aside from temporarily rolling back to OBS Studio 0.15.4, no.So is there anything I can do right now to make it work?
Yes, we are aware that the issue solely comes up in 0.16.x. The issue itself seems to be from something much deeper in the Quick Sync code that only became apparent in 0.16.x due to changes in how OBS drops frames during network congestion.I had this same issues with all 0.16.x iterations, I uninstalled and used 15.4 instead, issue as gone
If it's only 16.x why do I have the log posted here with 15.4 about the same error?Aside from temporarily rolling back to OBS Studio 0.15.4, no.
Yes, we are aware that the issue solely comes up in 0.16.x. The issue itself seems to be from something much deeper in the Quick Sync code that only became apparent in 0.16.x due to changes in how OBS drops frames during network congestion.
As I commented about your 0.15.4 log:If it's only 16.x why do I have the log posted here with 15.4 about the same error?
@servcovep
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.
Hi,
My OBS after random up time just stops streaming kbps dropped to zero without any error, and OBS still think its broadcasting.
Thanks man, looking forward to it!Going to release a hotfix soon. Just waiting on some secondary testing.
Going to release a hotfix soon. Just waiting on some secondary testing.
Not likely since I use win 7.I had the same issue, switched to Software encode. My fps and bitrate would drop to 0, sometimes it would recover and othertimes it would go offline till obs could reconnect using Quicksync. I'm sure is something to do with a win10 patch breaking Qsync
No. The issue with OBS 0.16.x and Quick Sync is due to a combination of a recent change in OBS frame dropping behavior and a possible Intel Quick Sync encoder bug.I had the same issue, switched to Software encode. My fps and bitrate would drop to 0, sometimes it would recover and othertimes it would go offline till obs could reconnect using Quicksync. I'm sure is something to do with a win10 patch breaking Qsync
Windows 7 has other issues with Quick Sync, as I previously mentioned:Not likely since I use win 7.
The issue you experienced in 0.15.4 is probably an issue with Quick Sync on Windows 7, as shown here. That is a separate issue, which is also being looked into by Jim. He can only do so many things at once, however, and the Windows 7 Quick Sync patch is pretty large and complex. I've just recently reviewed that patch, but I don't fully understand its contents.
So if it still doesn't work after we get the patch, hopefully soon, my only option is to upgrade to win 10?That remains to be seen. The specific issue that you originally cited in 0.16.x about the stream dropping to 0 Kbps will have been fixed in the next release. However, I can't say for sure if Quick Sync on Windows 7 will be problem free.
Until the other giant Quick Sync patch I mentioned is reviewed and merged, possibly.So if it still doesn't work after we get the patch, hopefully soon, my only option is to upgrade to win 10?
@servcovepoff topic question about quicksync, why is there no custom buffer size option? It uses cbr, and cbr has it, so do we not need it for this at all or?
@VorgunTheBetaUsing studio 0.16.6 and it still going to 0kb/s