I’m building a CXR client app for Oculus Quest 2. I tried having the server and client in the same WiFi network, and the audio input/output worked as expect. However, if I connect the client to the server on an AWS EC2 instance, the audio doesn’t work. It seems no audio devices are found. The EC2 instance was created with Nvidia’s AMI [NVIDIA CloudXR AMI Introductory Offer - WinServer 2019] in AWS Marketplace.
I observed that on my local machine CloudXR server creates virtual audio input and output devices when the client is connected, as listed under Audio Inputs and Outputs in Windows Device Manager.
On the EC2 instance, with the client connected, these virtual devices are not created, as shown in this screen capture.
Hi huong, thanks for your reply!
I saw your post, but I’m new to AWS and not sure if I can find the microphone privacy option you mentioned. Could you show me where it is?
I have allowed access to microphone in Windows settings, but it still doesn’t work.
Yes, the setup is correct, as audio input and output work correctly for the connection to my local server, and my local and aws server have the same setup.
I’m not sure if my issue is related to DCV/RDP. My question is why Nvidia Virtual Audio Device (WDM) is not added on my EC2 instance. I believe they should be added as in the first image in my original post.
Yes, note we call out explicitly in multiple places to NOT use RDP for connecting to remote server during cloudxr runs. The primary issue has been video capture, but as you’ve seen it can affect audio capture as well. We typically recommend using VNC, you might try that if you do need an interactive remote desktop on the instance while running your client.
Hi @tegradave , this is not correct in my case.
After I run cloudxr server(auto on startup), it will be blue-screen forever in case of NICE( even after close NICE ).
If I use RDP, it is only blue screen during session. Therefore, RDP is good for quick troubleshooting.