-
-
Notifications
You must be signed in to change notification settings - Fork 238
OpenHardwareMonitor/LibreHardwareMonitor integration #52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Very good idea indeed! |
Your choice might still be better. OHM is looking fairly quiet on Github, lots of issues not many actual commits going on... |
I found https://github.com/LibreHardwareMonitor/LibreHardwareMonitor a fork of Open Hardware Monitor still maintained, will give it a try |
Hi guys, I've started the development of the LibreHardwareMonitor integration for Windows platform. This will not be a quick task though. I already found 3 ways:
|
Hello @Cyruz143 |
Awesome work! Will give it a run this weekend and let you know. |
Ran it this weekend, no real issues to report, worked as expected! I did see the CPU effective clock being incorrect but that's been picked up in another ticket already with a suggested fix. |
Is your feature request related to a problem? If so, please describe the problem.
In theory this should hopefully resolve a few issues.
Describe the feature / solution to your problem you'd like
Integration of the Open Hardware Monitor (https://github.com/openhardwaremonitor/openhardwaremonitor) libs to replace various other limited 3rd party Python libs for Windows.
Describe alternatives you've considered / and or tested
I'm sure you were already aware of this, just thought it might save people making multiple issues requesting features/reporting bugs that are now known limitations of the currently used libs.
Additional considerations
I hope this fits your license seeing as OHM is open source, not sure if you want to include a .dll compiled by someone else.
The text was updated successfully, but these errors were encountered: