Figured out what was happening, it was using a nonexistent.txt file, deleted the config.txt and Dt990hrtf.txt, restarted the laptop and it started working.
Changes in the config editor doesn't change the sound or do anything but HeSuVi profiles still working.
64bit Floating point advantages: 1. Almost not restricted number summarize/multiply steps for achieving overflow (then for floating point resolutions). Very low noise level (below -190 dB) Fastest access to RAM (for 64-bit CPUs). Optimal bit size for 32- and 64-bit processors of computers. The reason why they are processing it as a floating point is for convenience in the computation and representation of very large /very small numbers and efficiency. This makes it possible to retain resolution while...
24bit is completely useless, 16 bit is more than enough since you will never hear -90dB in a non controlled setup. Do a dynamic range test and realize you wont need 24bit. The test: https://www.audiocheck.net/audiotests_dynamiccheck.php
You probably misunderstood me. My problem is that apps sometimes go above 48k and it disables my hesuvi until is close that app and restart the audio service.
Wait for the Oratory reddit to update the eq presets so it includes the 900x.For the second headset to get 7.1 you need to "plug it in" in the hesuvi connections panel and set it to virtualization.
Is it possible to increase the sampling rate from 48khz to 768khz or anything higher than 48k? It bothers me that if an app wants to use higher sampling rate HeSuVi stops working until i close the app.
I might be late but, In Eq APO do you have the "Include:" option? If not add it and select HeSuVi\hesuvi.txt as the config file.