Fiery

1) Smooth transitions and animations are not supported because of the limitations of the LCD rendering engine. It's really not designed to handle such effects and it doesn't support complex associations between slides/pages. 2) It'd be quite difficult to automatically detect which type of usage is currently going on on the computer And due to multi-tasking, detecting the starting or stopping of certain processes could be misleading too. 2) VLC is not supported at this time. Do you have a sample code that can take such details from a running VLC process? BTW, Winamp should be able to play movies too -- although it's not the ideal tool for the job 3) It's because fan duty cycle is a misleading value that shall be ignored. You should rather focus on the fan RPM readings. The GPU duty cycle was implemented only because certain video cards only support duty cycle detection, and doesn't support fan RPM measurement. For most motherboard fans both are always supported, so we only deal with the RPM measurement for motherboards. 4) Please send me your updated French language module in email, and I'll take a look into those changes Thank you!

Thank you, we'll fix that issue in the next AIDA64 beta update

We've contacted MSI to find out what causes the discrepancies between the information they've provided us, and the way their own monitoring software works. Meanwhile, we've added the missing +3.3V reading in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

The above mentioned new AIDA64 beta build is available for download at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

The above mentioned new AIDA64 beta build is available for download at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

The above mentioned new AIDA64 beta build is now available for download at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

The mentioned new AIDA64 beta build is available for download at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

Thank you. Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

We've fixed the issue in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery

Thank you for your help! It's always great to work with guys skilled in both electronics and C++

Please use MSI's own software as a reference on MSI motherboards, and Asus' own software as a reference on Asus motherboards. We'll add CPU VID voltage below the CPU Vcore reading to the Sensor page as well, so you can see both values listed.

We follow MSI's recommendations on how to handle the sensor registers on MSI Z270 motherboards. What exactly is the issue about the Vcore? Does MSI's own monitoring software measure a different value or the same value?

We've notified the authors of CPU-Z about this issue, asking them to implement the synchronization mutex that we've defined in order to avoid this issue. I'm not sure if it is already implemented in HWiNFO, so we'll ping its authors too.

Meanwhile we've found a solution to fix the collision between AIDA64 and aquasuite 2017. It will be implemented in the next AIDA64 beta update. I'm not sure if it helps about the slow updates too, but it's worth a try

The collision issue between AIDA64 and aquasuite 2017 will be fixed in the next AIDA64 beta update. I'll post a message into this topic once the new beta update is available for download. As for the 10 drives limit, yes, it's a limit built into AIDA64. Do you have more than 10 drives, so you would like to see the limit expanded? If so, how many drives do you have?

The issue will be fixed in the next AIDA64 beta update. I'll post a message into this topic once the new beta update is available for download.

I'm not sure what you're looking for. Can you please explain what exactly do you want to do about your E3815 CPU?

Thank you. Apparently the 4 fan registers corresponding to Chassis #n fans are all zero after waking up from sleep. We suspect it's because the BIOS fails to properly re-initialize the sensor registers after the computer comes back from sleep. I would have suggested you to update the BIOS, but you seem to be using the latest version of it. Apart from asking Asus about this, and reporting them about this potential BIOS bug, I'm not sure what can be done to get around this issue

The missing drives could be because of Aquasuite. The latest version of that software seems to open drives exclusively, and monitors them in a way that makes other software unable to access the drives

Thank you. We'll check it on a similar Sandy Bridge configuration soon.

Thank you. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Please repeat that dump after the computer wakes up from sleep and the fans already disappeared. Thanks, Fiery

We've checked the foobar2000 SDK, but it seems quite complicated to use. For such a minor improvement we simply find it too awkward and complex to deal with. Maybe we're looking at the wrong bits and pieces though, so if you (or someone else) can provide a short source code to detect the information you're looking for, we'd be happy to implement it. I'm afraid we have no plans about an audio visualizer for AIDA64.

We've checked the foobar2000 SDK, but it seems quite complicated to use. For such a minor improvement we simply find it too awkward and complex to deal with. Maybe we're looking at the wrong bits and pieces though, so if you (or someone else) can provide a short source code to detect the information you're looking for, we'd be happy to implement it.

Thank you for your feedback