EVGATech_JoseR

c1team
Got the card installed and everything on that front went smooth. For the software side I'm running into a few issues.
 
1. Nu Audio software didn't seem to add a start menu shortcut during the install. v0.2.0.7 on Windows version 10.0.17763 Build 17763 (1809)
2. The Save and Load feature is greyed out and I cant seem to use it. That a future release feature? I'm assuming this will be helpful for users with multiple headsets like myself. Using AT M50X and  Sennheiser Game One.
3. I also herd the crackling from the EQ when adjusting the 32, 64 sliders.
4. Whenever I use Ableton, the driver doesn't seem to release the ASIO and return back to direct when I close out. I get no audio and things like YouTube spin like it's buffering, same with local audio files. I have to log off and back in.
5. Didn't notice right away but I had line-in selected and my mic was still working.
 

1. You can create a shortcut by going to the directory where the Nu Audio driver was installed (default: C:/program files (x86)/EVGA/Nu Audio Card and right click on "NUA" to create shortcut on your desktop
2. Save and Load are for future use. If you notice, our Precision X1 software has a very similar interface and at some point we will be unifying the Nu Audio software into PX1. 
3. Check the sampling rate and see if reducing it affects this crackling noise. When you say sliders are you referring to the Abelton software?
4. I think this particular issue is software related which may be related to the latest update to the Nu Audio driver or possibly a Windows update but I will check with our product management. 
While using Abelton, does the Nu Audio software indicate "ASIO  Active" or "ASIO not active" under set up?
5. check the source for the mic in Windows audio properties under the recording tab.

c1team
4. So on the ASIO driver issue, I found the driver will release back after a few moments. This might be due with Ableton still closing?  The other thing is if an application is open during the change I would have to close the app and reopen it for the direct driver to work again. There more of a technical read up on the hand off between drivers?