|
|
Post by bluntblade on Aug 7, 2020 5:57:00 GMT
Hi there,
I'm currently using SIV to control my Corsair Commander Pro. Both the fans and the LEDs.
However, I would like to switch the LED control over to OpenRGB and maintain the fan control through SIV.
With testing it seems that SIV and OpenRGB conflict over the RGB control.
How do I disable LED control in SIV whilst maintaining fan control over the Commander Pro?
|
|
|
|
Post by siv on Aug 7, 2020 14:27:57 GMT
How do I disable LED control in SIV whilst maintaining fan control over the Commander Pro? Welcome to the forum and if you set the LEDs to a static colour then SIV will set this on start-up and then never touch them again. I suspect this will do at lest 99% of what you would like, but I suspect there may be locking issues. Does OpenRGB correctly use Global\CorsairLinkReadWriteGuardMutex to interlock access to the CLCP? To check look at the Menu->Help->Lock Handel panel and if OpenRGB is not listed then it needs to be fixed. Please post the panel. To check what locks OpenRGB uses on Menu->Windows->Processes Right/Click on it's [ PID ] button and select Locks, also post this panel. I have attached an example of SIV64X on this system. |
|
|
|
Post by bluntblade on Aug 7, 2020 18:25:31 GMT
How do I disable LED control in SIV whilst maintaining fan control over the Commander Pro? Welcome to the forum and if you set the LEDs to a static colour then SIV will set this on start-up and then never touch them again. I suspect this will do at lest 99% of what you would like, but I suspect there may be locking issues. Does OpenRGB correctly use Global\CorsairLinkReadWriteGuardMutex to interlock access to the CLCP? To check look at the Menu->Help->Lock Handel panel and if OpenRGB is not listed then it needs to be fixed. Please post the panel. To check what locks OpenRGB uses on Menu->Windows->Processes Right/Click on it's [ PID ] button and select Locks, also post this panel. I have attached an example of SIV64X on this system. Thank you so much for the reply. As you mentioned setting a static colour through SIV and then setting another setting through OpenRGB does seem to do the trick. I've attached the panels as requested, it doesn't seem that OpenRGB is using the CorsairLinkReadWriteGuardMutex. Here is the relevant page from the OpenRGB wiki: spams://gitlab.com/CalcProgrammer1/OpenRGB/-/wikis/Corsair-Lighting-Node-DevicesAttachments:
|
|
|
|
Post by siv on Aug 7, 2020 21:48:19 GMT
Thank you for the screen shots which clearly show that OpenRGB fails to use Global\CorsairLinkReadWriteGuardMutex. Given this I expect if you look at [ Link Status ] when OpenRGB is changing the colours the Tooltip for Corsair Link Commander Pro (CLCP) will show protocol errors have been seen. The only sensible solution is for OpenRGB to be corrected to use the lock and suggest you request it's developers to do this. Until OpenRGB has been fixed I suggest you don't use it when SIV is active and if you choose to do this it's at your own risk and I won't/can't sensibly support SIV. I also have concerns about the Corsair bloatware being active as they intentionally broke the support for their lock, see spams://siv.boards.net/thread/14/running-same-time-corsair-iPOO I just spotted the INUSE Wait 812 of 812 ms on [ Lock Handle ] which should be INUSE Wait 0 of 812 ms. The fact that the first number is 812 means that you have some software that fails to correctly use the SMBus hardware interlock. I know SIV correctly supports it as does HWiNFO (last time I checked). In this situation I should run just SIV, check it's INUSE Wait 0 of 812 ms, then run the other programs 'till it goes to INUSE Wait 812 of 812 ms then get that program fixed. My guess is that it's OpenRGB and it also fails to use Global\Access_SMBUS.HTP.Method when accessing DIMM LEDs  |
|
|
|
Post by bluntblade on Aug 8, 2020 18:56:44 GMT
Thank you so much.
I appreciate all the assistance.
|
|
|
|
Post by bluntblade on Sept 24, 2020 17:55:23 GMT
|
|
|
|
Post by siv on Sept 25, 2020 13:27:46 GMT
I followed the link and all I got was a blank screen. As I can't see what was said I can't sensibly comment and if the OpenRGB guys which to ask for clarification feel they should do so directly on this forum. Before they even start using the Global\Access_SMBUS.HTP.Method mutex I suspect they first need to fix their code to correctly use Is Use Status (IUS), see Intel PCH Datasheets. By default the mutex protection is incorrect and should be ad below. All in all it would be far easier to talk directly via email with the OpenRGB developers. Attachments:
|
|
|
|
Post by bluntblade on Sept 28, 2020 5:40:45 GMT
Thank you so much for the response.
That's odd, the OpenRGB Gitlab is open to the public.
In any case I will pass the message along.
Thank you so much for your willingness to assist with this.
Hopefully we can get all these apps working well along side each other with Corsair hardware (if only Corsair themselves were open to collaborating and getting iPOO to play ball as well).
|
|
