You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 22, 2022. It is now read-only.
When I play a WebRTC video stream in a standalone test scene, playback is very smooth. But in our production app, playback is choppy and regularly halts for a second or more. Our app has a lot going on in it, but runs at a consistently high frame rate. Do you think the WebRTC worker threads could be getting starved? I'd like to try bumping their priority up. Do you have advice on how to best accomplish this? Would it make sense to add a field to PeerConnectionConfiguration to specify a thread priority that could be passed on to Google's native library?
I'm running with a locally built Microsoft.MixedReality.WebRTC.Native.dll, Release/x64 configuration.
When I play a WebRTC video stream in a standalone test scene, playback is very smooth. But in our production app, playback is choppy and regularly halts for a second or more. Our app has a lot going on in it, but runs at a consistently high frame rate. Do you think the WebRTC worker threads could be getting starved? I'd like to try bumping their priority up. Do you have advice on how to best accomplish this? Would it make sense to add a field to PeerConnectionConfiguration to specify a thread priority that could be passed on to Google's native library?
I'm running with a locally built Microsoft.MixedReality.WebRTC.Native.dll, Release/x64 configuration.