crystal light mic issue with voice attack

[Abarth595]

Hi just got my crystal light yesterday and i am having a few issues with voice attack not detecting the mic , been into win 11 settings and made sure the pimax mic is the only one working and set to default ,the only work around is when i start voice attack i have to restart the hmd or service in pimax play  and then it works ok until i quit and will have to do the same again .

ps i am on the latest pimax play .

regards graham 

[Abarth595]

may have solved it ,tried another usb on mb ,seems to be more stable at the min ,fingers crossed .

[tangobravo]

I had the same issue, I deleted the mic in device manager unplugged and reinserted the USB, apparently this installs the driver again. I also uninstalled everything to do with WMR and OXR (from my previous G2 days). Still happens from time to time but it now I just have click on Restart Device in pimax play. Hope this helps. 

[Calvin.Pimax]

Have you tried to switch to other USB port? 

[Abarth595]

Hey thanks for the replys ,yes swapped to another usb and seems better ,

1 hour ago, tangobravo said:

I had the same issue, I deleted the mic in device manager unplugged and reinserted the USB, apparently this installs the driver again. I also uninstalled everything to do with WMR and OXR (from my previous G2 days). Still happens from time to time but it now I just have click on Restart Device in pimax play. Hope this helps. 

yes still got to delete all wmr rubbish as well !!!!

thanks again graham

[Dangerzone]

Am I right in assuming that the Pimax software has to be running in order for Windows to detect (and use it) as the default device? I thought this was the case but reading above, I'm wondering if I am wrong.

In my instance - when I first start windows, and then launch the Pimax app - I have to go into windows mixer, and select Pimax as the device every time in order to have it be used as the default windows device. it's as though when Windows first starts, it can't see it - so defaults back to something else, and then the device is loaded, but it's too late - windows has reset it.

I've been able to get around this by setting it every time I start the PC as part of my manual start-up procedures and thought this was normal, but after reading this - wondering if I'm doing something wrong?

[Keith Briscoe]

I have this issue of PCL mic usually not be recognized by voice Attack. This and the periodic floating / bad tracking...  Honestly this is kind of a piece of $#!7.  And I didnt even have issues with lenses that others had.

Only just came back to try PCL again with new Pimax play. Looks good and works fine at first. Then all these gremlins surface, just like when I originally got my PCL.  Seriously such a regret. 

Will probably go right on back to G2 and just keep delaying 24h2 update.

[Dangerzone]

17 hours ago, Keith Briscoe said:

I have this issue of PCL mic usually not be recognized by voice Attack. This and the periodic floating / bad tracking...  Honestly this is kind of a piece of $#!7.  And I didnt even have issues with lenses that others had.

Only just came back to try PCL again with new Pimax play. Looks good and works fine at first. Then all these gremlins surface, just like when I originally got my PCL.  Seriously such a regret. 

Will probably go right on back to G2 and just keep delaying 24h2 update.

Re the Mic - I had a lot of trouble to start with, but I found a particular way I need to launch my computer in order to get it to work. I need to open up Pimax Play first. Then go to windows sound mixer, and select Pimax for the source of both. Then after that, launch Voice Attack.

It seems that Pimax Mic/Speakers is not recognised by Windows until after Pimax Play is launched, and inbetween that time, since Windows can't find the Pimax hardware, it resets the sound devices back to what it see's as being available. 

It doesn't quite make sense to me. The hardware is connected right from the start, and I never had the issue with HP Reverb, even if WMR wasn't launched - but have just accepted for now that it is what it is.

As for the tracking issue, I haven't had issues with that myself, but have heard that some people find LED room/ceiling lights an issue with it that might be worth a consideration. 

[Keith Briscoe]

25 minutes ago, Dangerzone said:

Re the Mic - I had a lot of trouble to start with, but I found a particular way I need to launch my computer in order to get it to work. I need to open up Pimax Play first. Then go to windows sound mixer, and select Pimax for the source of both. Then after that, launch Voice Attack.

It seems that Pimax Mic/Speakers is not recognised by Windows until after Pimax Play is launched, and inbetween that time, since Windows can't find the Pimax hardware, it resets the sound devices back to what it see's as being available. 

It doesn't quite make sense to me. The hardware is connected right from the start, and I never had the issue with HP Reverb, even if WMR wasn't launched - but have just accepted for now that it is what it is.

As for the tracking issue, I haven't had issues with that myself, but have heard that some people find LED room/ceiling lights an issue with it that might be worth a consideration. 

thanks, I will try that order of opening apps!

[Dangerzone]

7 hours ago, Keith Briscoe said:

thanks, I will try that order of opening apps!

Don't forget to check windows sound mixer after opening pimax and re-setting your pimax devices in there too.

[Hillman]

I also have this issue with VoiceAttack and Pimax Crystal Light microphone. VA show a red microphone icon indicating it lost connection with the device. I did work previously so very strange.
When using software like BeyondATC I have no issues with the mic so seems like a VA issue?
Extremely frustrating to loose contact with VA when you are in VR and are depending on it...
 

[Dangerzone]

2 hours ago, Hillman said:

I also have this issue with VoiceAttack and Pimax Crystal Light microphone. VA show a red microphone icon indicating it lost connection with the device. I did work previously so very strange.
When using software like BeyondATC I have no issues with the mic so seems like a VA issue?
Extremely frustrating to loose contact with VA when you are in VR and are depending on it...
 

I've noticed some strange things such as:

Discord - I can hear people, they can hear me, but the notification sounds are going elsewhere

DCS and SRS seem to work OK - but Voice Attack doesn't send sounds to me (or can access my microphone).

HOWEVER  - if I go into Windows Mixer, and set the default sound devices to Pimax (they default elsewhere on each startup) - this appears to fix the issue.

My current conclusion is that Discord's voice input and output is different to the notifications. Notifications use windows default, where the other stuff you can set yourself.

I think it's also the same with Voice Attack - it appears to use the windows default sound (which changes/defaults on each startup because Pimax device isn't detectable until after their app is running). 

So my fix for this is:

1. Start Windows
2. Launch Pimax Play
3. Open Windows Mixer - and change the default input and output. (if it's on pimax, switch to something else and back again).
4. Only after all those - then open up Discord, and Voice Attack.

Give that a try and see how you go.

Cheers

DZ