Repository navigation
Version 2.4 missing DLL on Windows #154
Description
Activity
Try this one. It includes all dependencies statically. Should also work without the hidapi.dll
If it works for you I make a new release
It "almost" worked:
> headsetcontrol.exe -b Found Corsair Headset Device! Failed to request battery. Error: -1: Incorrect function.Did it work before with the old version?
And do other things work, like sidetone or
-n 0?Version 2.3 did not find my headset.
All commands seem to have the same issue:>headsetcontrol.exe -n 0 Found Corsair Headset Device! Failed to send notification sound. Error: -1: Incorrect function.Thats difficult then. It means that the usagepage and usageid for your headset differs (and Windows cares for that).
You basically have to download the testgui from HIDAPI https://github.com/signal11/hidapi/releases
it is located in the folderhidapi-0.7.0.zip\hidapi-0.7.0\testguiit should show all usagepage and usageids."all usagepage and usageids".
They are after the word usage inside your screenshot. So you have a pair of three. The last one (ff00:0001) is the one in the current implementation
Try copy pasting this besides Send Feature Report:
0xff 0xb 0 0xff 0x4 0xe 0xff 0x5 0x1 0x4 0 0xfa 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0Then click on the button, and do this for all 3 entrys, and see if it works for one of them.
(it should set the sidetone to high)
It seemed to work (at least no error was shown) for the last device:
ff00:0001Ah I think I know then what the issue is.
Did you explicitly try Sidetone?
e.g.
headsetcontrol -s 128Sidetone works!
>headsetcontrol.exe -s 128 Found Corsair Headset Device! Success!I see.
The problem is, the different features are basically in different so called usage-pages (the different ids you see). That means the software can currently only support one feature at a time, as it wasn't developed with that in mind (as on Linux, it does not matter which usage-page you use, as there is none). So unfortunately you can only use one feature without recompiling the software.
Oh I see. That's a bummer but I understand. Thank you!
How would I go about changing the usage-page to support for instance turning the LED on/off? I know I need to recompile after, so my question is what portion of the code I need to change to accomplish that?
You need to change those lines in corsair_void.c
HeadsetControl/src/devices/corsair_void.c
Lines 55 to 56 in 9011bc5
device_void.idUsagePage = 0xff00; device_void.idUsage = 0x1; The new release has everything statically linked on windows and can be run directly: https://github.com/Sapd/HeadsetControl/releases
The new release has everything statically linked on windows and can be run directly: https://github.com/Sapd/HeadsetControl/releases
Sadly, this behaviour remains for me.
- Headset: Corsair Void RGB
- Release 2.5
- Windows 11
Example:
headsetcontrol.exe -b Found Corsair Headset Device! Failed to request battery. Error: -1: Incorrect function.headsetcontrol.exe -s 0 Found Corsair Headset Device! Success!The new release has everything statically linked on windows and can be run directly: https://github.com/Sapd/HeadsetControl/releases
Sadly, this behaviour remains for me.
This was not addressed by this release. I already have an idea of how to solve it, however it will still take a bit of time
(feel free to open up an seperate issue, if none exists yet)
The new release has everything statically linked on windows and can be run directly: https://github.com/Sapd/HeadsetControl/releases
Sadly, this behaviour remains for me.
This was not addressed by this release. I already have an idea of how to solve it, however it will still take a bit of time
Ah, my bad! Thanks for the clarification :)
The new release has everything statically linked on windows and can be run directly: https://github.com/Sapd/HeadsetControl/releases
Sadly, this behaviour remains for me.
This was not addressed by this release. I already have an idea of how to solve it, however it will still take a bit of time
Ah, my bad! Thanks for the clarification :)
@vcekron The new version completely fixed it. Should now work out of the box with all features. Feel free to create a new issue if there are still problems

I'm receiving this error when trying to run version 2.4 on Windows 10 Pro x64:
The code execution cannot proceed because libwinpthread-1.dll was not found. Reinistalling the program may fix this problem.