5 Replies Latest reply on Feb 4, 2020 8:40 PM by AFA1K

    Philips SpeechMike Audio In Issue (Win10)

    epa80 Enthusiast

      Might be more of a Dell/Wyse question, but, wanted to see if anyone on these forums bumped into this.


      In our environment we use the Wyse 5010 w/ PCoIP terminal as our standard endpoint. We are a Windows 7 shop on Horizon 7.3.2. We are able to get the SpeechMikes passed into the Horizon session, via splitting the vid/pid at the terminal level. This setup has worked for us for a few years now, no issue.


      Recently we began developing a Win 10 image as well using Blast. Using the same terminal endpoint, signing into our Windows 10 image, Blast uses the mic just fine still. However, on PCoIP, no audio in is happening. We see the mi in device manager just fine, and audio OUT from the mic still works, just not audio in. The Philips control center client sees the device, it allows config of the buttons on the mic, all seems well, except audio in.


      In a nutshell:


      All from an identical endpoint:

      Win 7 Blast - Mic fine

      Win 7 PCoIP - Mic Fine

      Windows 10 Blast - Mic Fine

      Windows 10 PCoIP - Mic bad.


      I tried installing the teradici audio driver in the base just to see if it made a difference, but, no luck.


      I'm opening a ticket with Dell in parallel, but, any feedback here, I'd be happy to get.


      Thanks in advance.

        • 1. Re: Philips SpeechMike Audio In Issue (Win10)
          epa80 Enthusiast

          Bump. Dying to hear if anyone has come across a solution for this.


          I took a Windows 7 VMs where this worked via PCoIP (sound in), and upgraded it to Windows 10, and then I couldn't do sound in. So this wasn't 2 different VMs, it was a direct upgrade and it broke. What about Windows 10 and PCoIP sound in am I missing?

          • 2. Re: Philips SpeechMike Audio In Issue (Win10)
            BenFB Expert

            Just an FYI. If you install the Teradici Audio Driver and select that device you will not get any audio through Blast.

            • 3. Re: Philips SpeechMike Audio In Issue (Win10)
              FlowDE Novice



              we're working actually whit blast, speech mike and RTAV but the Input Quality is quite low a lot of background noise and bad quality. I tested PCOI whit the Teradici Audio driver.

              At the first moments i dindn't got any sound output but the input works. After declare the Teradici Sounddriver as default it works fine.


              We're using Igel ThinClients as a Host-System.




              • 4. Re: Philips SpeechMike Audio In Issue (Win10)
                FlowDE Novice

                Hey again,


                well it looks like their is no Sound-Input from Igel Clients..... https://help.teradici.com/s/article/1049



                • No audio output
                  • Check the pcoip.enable_audio variable in the pcoip-agent.conf file is not configured and set to disabled.
                  • Ensure the PCoIPVirtualOutput is the default playback device. If the device is missing, reinstall the agent.
                  • Check that the audio output is turned up
                  • Test audio playback on the local client machine if you are using the PCoIP Software Client
                  • On a PCoIP Zero Client, disconnect the session and use the audio test tone available from the AWI under Diagnostics > Audio.
                • No audio Input
                  • Audio input is not supported in the PCoIP Agent for Linux


                i got the same problem on my side....




                • 5. Re: Philips SpeechMike Audio In Issue (Win10)
                  AFA1K Novice
                  VMware Employees

                  What is the operating system on your WYSE 5010?

                  We have seen WYSE 5060 and 5070 with WYSE ThinOS do not support USB composite device splitting for PCoIP. (USB redirection can be used with PCoIP however).


                  Obvious test would be to take one of the endpoints that is using Blast/Windows 10 and connect using PCoIP instead to see if the mic continues to work. This will rule out the possibility that perhaps the configurations are not exactly identical.