Not found sound device on startup

[IvanSaratov]

Hello.
I came across some interesting behavior.
I installed VA-Cable where all my music is routed, and I wanted to set it as the capture device. This cable is not the default input device in the system. I tried many combinations, but here’s what happened:

No matter what you select in the UI (different virtual cable outputs), it gets ignored.

If, after launching the program (I ran it via console with -c), you set the virtual cable as the input device via the Windows Volume Mixer, it starts listening to it and works. Otherwise, it throws the error: "Can't find audio device."

If the program launches via system autostart, it loses the mixer settings, and I’m back to point 1.

If you save the settings and restart the program, it freezes during initialization and has to be killed via taskkill.

Right now, I’m trying to figure out how to launch the program at system startup while ensuring the selected recording device is assigned at the system level. So far, I’m reading about how the Windows Task Scheduler works, but no success yet.

P.S. Also noticed heavy CPU usage (up to 100%) when enabling "fullscreen multi color fast" mode.

[awawa-dev]

Hi
The sound devices are detected only at HyperHDR startup. If the device appers later it wont be detected. But you can create BAT script (chatgpt will create it for you in a second) to make a delay before running HyperHDR and add it to autostart (instead of using default HyperHDR autostart mechanism) before running HyperHDR and give other sound devices some time to start-up.

P.S. Also noticed heavy CPU usage (up to 100%) when enabling "fullscreen multi color fast" mode.

will take a look later

[awawa-dev]

I think timeout is a delay command in BAT, then in the same BAT start HyperHDR executable

[IvanSaratov]

Hi.
I managed to set a delay using Windows Task Scheduler so that it launches after other audio programs initialize, and that fixed the issue. However, the CPU load problem is still relevant.
In any music mode, it spikes to 100%. I thought it might be because of Voicemeeter (maybe due to too many channels), but in the standard Skydimo app (I have their lighting), it works fine. Maybe I set up some synchronization or smoothing incorrectly?