Conflict with HWinfo64 when accessing memory module SMBus
Hi,
Latest pipeline (but not limited to it, it`s been like that since I first started using OpenRGB almost 2 years ago).
Under windows 10 21H1, OpenRGB is conflicting with the HWinfo64 temperature reading of my memory modules. The modules are Gskill royal-Z DDR4 and they use the ENE SMbus interface in OpenRGB (Address 0x71 + 0x73).
The conflict seems to be that both OpenRGB and HWinfo64 are trying to access the SMbus at the same time and eventually collide. When this happen, either HWinfo64 will cough up wrong temperature readings of the DIMMs or their RGB will become unresponsive until I shutdown + restart the PC.
From my research HWinfo64 has an implemented mechanism to circumvent this SMBus access issue, but it has to be implemented on both software to work. Martin from HWinfo64 calls it a Mutex (See section "SMBus locking" here: http://rh-software.com/). I'm pretty sure until (if) this mechanism is implemented to OpenRGB, this issue cannot be fixed.
I know that with DDR5, this might become a much more common issue as many have built in monitoring ICs. (it's already a thing, see here: https://www.reddit.com/r/OpenRGB/comments/rp5wqj/warning_be_very_careful_with_openrgb_asus_z690/)
So, my question is: Are there any plan to implement the Windows SMBus lock (mutex) to OpenRGB?