(Bug Report) Specific VoD with error #3000 example at a timestamp and fix
This is more of a bug report rather than any sort of suggestion, but this seems like the most applicable place to post it.
I was running into error #3000 frequently when watching a particular VOD, and eventually realized that the errors were not occurring randomly, but at specific time stamps in the video. One solution was to disable my chrome browser's hardware acceleration, but that resulted in heavy tearing on the video no matter what my vsync and other related settings were set to. Eventually, I found the solution in the form of using chrome://flags to explicitly either
1) Disable Hardware acceleration on video Decode (no tearing, but slightly reduced performance) or
2) Chose ANGLE graphics backend - set to openGL (no tearing, no performance lost, optimal solution)
Based on this solution, I can safely say that the following VOD, on my set up with an NVIDIA RTX 2070 GPU on Win10, will always encounter an error #3000 at this timestamp: https://www.twitch.tv/videos/1187291672?t=3h55m42s when using D3D11. There are various other spots that cause it too, that's just the one I caught when I realized it was at a specific time in playback.
Hopefully you'll be able to reproduce the issue using that information, and maybe figure out /why/ it's happening to find a fix, if it's not something just specific to my environment.