Jerome Humbert

+1 for this, just lost an hour trying to figure out why our build was linking against Debug CRT in Release config, just to realize this was only a problem...

It seems the Google implementation fails to open the audio device. Did you add the appropriate capabilities to the Android manifest of your app to allow `RECORD_AUDIO`?

The 2.0.1 and 2.0.2 have patches for unrelated things, so I didn't expect things to change. I just noted you say the VideoChatDemo works fine; so the audio is opened...

I'm puzzled/suspicious about this: > The VideoChatDemo scene works fine on the Android device. The crash in the logcat is from opening the audio capture device (microphone) on the Android...

Hi @Daniel4144, This is not supported out of the box. There are several ways to do that; I suggest you have a look at the discussions on webrtc-uwp/webrtc-uwp-sdk#10, w3c/strategy#133, https://groups.google.com/forum/#!topic/discuss-webrtc/CcJnxzUsVBE,...

Let me be a bit more clear: I totally see the value of this feature for MR apps, and I am sure you are not the only one to want...

I will leave that issue open as a feature request. We can re-prioritize if there's more demand.

All very good info, thanks @kspark-scott, and the others who also contributed. I also would be interested to see something done in this area, there seems to be some demand...

@kspark-scott beat me to it. Yes this is likely the alignment drift from using the wrong focus point. Unfortunately there is currently no control over that in MixedReality-WebRTC.

Any idea about what? I don't think Remote Assist uses WebRTC, so they won't have the issue of finding a way to send the head position through the WebRTC protocol.