Jump to content
AIDA64 Discussion Forum
vlad

Can we have a hotkey to turn RGB LED on/off?

Recommended Posts

Hello to the developers! Long time no talking....

If is not too much trouble, I would like to have the ability to turn on/off the RGB LED function via hotkey. It takes complete control of the keyboard and mouse rgb lightning and this is not always what I want. Having to dig through the menus is cumbersome.

Idealy would be the have a transparent background color that would let other lights from devices software to go through, although I do not know if that is possible..... It seems to me that the peripheral only lets one app to "tell it what to do".

Btw I use Razer Huntsman and Razer rgb mouse....

Share this post


Link to post
Share on other sites
On ‎5‎/‎14‎/‎2019 at 7:07 AM, vlad said:

Hello to the developers! Long time no talking....

If is not too much trouble, I would like to have the ability to turn on/off the RGB LED function via hotkey. It takes complete control of the keyboard and mouse rgb lightning and this is not always what I want. Having to dig through the menus is cumbersome.

Idealy would be the have a transparent background color that would let other lights from devices software to go through, although I do not know if that is possible..... It seems to me that the peripheral only lets one app to "tell it what to do".

Btw I use Razer Huntsman and Razer rgb mouse....

The requested feature has been implemented in the latest AIDA64 update of v6.00:

https://www.aida64.com/downloads/latesta64xe

Share this post


Link to post
Share on other sites

Thank you for considering my request.

There seems to be a bug here. Via hotkey you can not toggle the function, you can only turn it on. Also, regardless if the preferences panel is open or not, the "Enable RGB LED keyboard support" checkbox does not update when you use a shortcut hotkey.

Share this post


Link to post
Share on other sites
On ‎5‎/‎21‎/‎2019 at 8:45 AM, vlad said:

Thank you for considering my request.

There seems to be a bug here. Via hotkey you can not toggle the function, you can only turn it on. Also, regardless if the preferences panel is open or not, the "Enable RGB LED keyboard support" checkbox does not update when you use a shortcut hotkey.

We've fixed the issue in the latest AIDA64 beta update available at:

https://www.aida64.com/downloads/latesta64xebeta

Let me know how it works.

Share this post


Link to post
Share on other sites

It works fine now it works from any app. The only thing not updating is the check state of the box in the Prefences pannel, but that does not really matter.

 

Thank you for taking the time to implement and fix this. :)

Share this post


Link to post
Share on other sites
On ‎5‎/‎29‎/‎2019 at 11:08 AM, vlad said:

It works fine now it works from any app. The only thing not updating is the check state of the box in the Prefences pannel, but that does not really matter.

 

Thank you for taking the time to implement and fix this. :)

Thank you for your feedback ;) 

Share this post


Link to post
Share on other sites

Hello to the developers!
Thank you for keeping such a good care of this software product.

Regarding the feature that is the subject of this topic: after using it for 2 months I have some feedback.

 Right now, if you configure a raw of keys to show something, you loose the background color (the one you set globaly), so if the "bar" is half full, the rest of the key go unlit. Why this is a problem: if you have the qwerty, asdfg, zxcvb raws asigned to some sensors that do not reach 100% most of the time and instead go arond, let`s 50% you end up having most of your keys unlit, which is making the keaboard hard to use in dim light.

  If it is not to much trouble, it would be nice to have the extended areas of the keyboard and other rgb peripehrals available to maping (like zones on the mouse, extra keys on keyboard and so on...). I know that are a lot of peripherals out there so it may be hard to cover them all, but at least the products from the most used peripherals like Corsair, Logitech, Razer...

 

Anyway point 2 is not that important, but point one ( persistent background color for raws of keys ) it would improve usability.

In the hope that you will have time to address this request I thank you and wish you well!

Share this post


Link to post
Share on other sites
On ‎8‎/‎1‎/‎2019 at 7:09 AM, vlad said:

Hello to the developers!
Thank you for keeping such a good care of this software product.

Regarding the feature that is the subject of this topic: after using it for 2 months I have some feedback.

 Right now, if you configure a raw of keys to show something, you loose the background color (the one you set globaly), so if the "bar" is half full, the rest of the key go unlit. Why this is a problem: if you have the qwerty, asdfg, zxcvb raws asigned to some sensors that do not reach 100% most of the time and instead go arond, let`s 50% you end up having most of your keys unlit, which is making the keaboard hard to use in dim light.

  If it is not to much trouble, it would be nice to have the extended areas of the keyboard and other rgb peripehrals available to maping (like zones on the mouse, extra keys on keyboard and so on...). I know that are a lot of peripherals out there so it may be hard to cover them all, but at least the products from the most used peripherals like Corsair, Logitech, Razer...

 

Anyway point 2 is not that important, but point one ( persistent background color for raws of keys ) it would improve usability.

In the hope that you will have time to address this request I thank you and wish you well!

In the latest AIDA64 beta (Build 5146) we've added a lot more keys to unlock their mapping in the RGB LED module.  That may solve your issues about the dark background.

BTW, there's also an option called Keyboard backlight color on the AIDA64 / main menu / File / Preferences / Hardware Monitoring / RGB LED page to let you choose the "background color" of the RGB LED keyboard.

Share this post


Link to post
Share on other sites
19 hours ago, Fiery said:

BTW, there's also an option called Keyboard backlight color on the AIDA64 / main menu / File / Preferences / Hardware Monitoring / RGB LED page to let you choose the "background color" of the RGB LED keyboard.

Yes there is, but if you have a sensor maped to a raw of keys, say qwerty, and the "bar" is up to lets say "letter" the ones after it from"y" onward, will remain unlit, regardless of the "background color" chosen. So if you map 3 sensors  to the 3 raws of keys: "qwerty", "asdf" and "zxcv" you will have most of the key unlit, unless the sensor "bar" ar always close to 100%

Share this post


Link to post
Share on other sites
4 hours ago, vlad said:

Yes there is, but if you have a sensor maped to a raw of keys, say qwerty, and the "bar" is up to lets say "letter" the ones after it from"y" onward, will remain unlit, regardless of the "background color" chosen. So if you map 3 sensors  to the 3 raws of keys: "qwerty", "asdf" and "zxcv" you will have most of the key unlit, unless the sensor "bar" ar always close to 100%

We've solved that issue in the following new beta build of AIDA64:

https://www.aida64.com/downloads/latesta64xebeta

Share this post


Link to post
Share on other sites
On 8/14/2019 at 4:49 PM, Fiery said:

We've solved that issue in the following new beta build of AIDA64:

Thank you. It works much better. Still a problem with using 2 or 3 digits to represent a sensor, the number keys (top raw and and numpad numbers for 3 digits) not responding to background color (unlit).

Share this post


Link to post
Share on other sites
17 hours ago, vlad said:

Thank you. It works much better. Still a problem with using 2 or 3 digits to represent a sensor, the number keys (top raw and and numpad numbers for 3 digits) not responding to background color (unlit).

We'll fix the remaining issues in the next AIDA64 beta update ;) 

Share this post


Link to post
Share on other sites
25 minutes ago, vlad said:

It works as expected. Thank you for taking care of the problem. Excelent work!

Thank you for pointing out the bugs for us ;) 

Share this post


Link to post
Share on other sites
18 hours ago, Fiery said:

Thank you for pointing out the bugs for us ;) 

Have another bug for you:
The Numpad  numbers and and the top raw numbers (so only the part actualy used by a 2 or 3 digit meter) have the B <-->R channels swaped for the "background" color. Meaning that white shows white, but using any combination of RGB that does not have R and B equal results in wrong colors, compared to the rest of the keboard "background" keys.

If you put, for example a pure red you can see that very well, because the number keys "background" becomes blue instead.

Share this post


Link to post
Share on other sites

Noticed that this morning, when I swaped the white "background" color for a desaturated light blue that turned white on the said keys. Then I did some color testing and come up with the bug...

Share this post


Link to post
Share on other sites
5 hours ago, vlad said:

Have another bug for you:
The Numpad  numbers and and the top raw numbers (so only the part actualy used by a 2 or 3 digit meter) have the B <-->R channels swaped for the "background" color. Meaning that white shows white, but using any combination of RGB that does not have R and B equal results in wrong colors, compared to the rest of the keboard "background" keys.

If you put, for example a pure red you can see that very well, because the number keys "background" becomes blue instead.

Awesome, we will fix that as well as another one about Corsair RGB LED keyboards in the next AIDA64beta ;)  Thank you for your help!

Share this post


Link to post
Share on other sites
On ‎8‎/‎27‎/‎2019 at 6:48 AM, vlad said:

Noticed that this morning, when I swaped the white "background" color for a desaturated light blue that turned white on the said keys. Then I did some color testing and come up with the bug...

Here's the fix for this issue:

https://www.aida64.com/downloads/latesta64xebeta
 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

  • Similar Content

    • By schrutic
      There are a few of the sensors where the default unit and value are either too large or just aren't desired. For instance, the default Download Rate. Currently the default Download Rate displays in KB/s. While I can change the unit label, I don't have any way to change the value itself. My enhancement request is to allow what I'm calling Value Modifiers or Expressions. These would only be available for sensors whose values are numbers (ints, floats, etc.).
      Let's go through a real world example of how we could implement this. Here is my current sensor panel. Note the upload and download speeds being in KB/s (red box). While it's nice to see KB/s, I would rather it display in MB/s.

       
      With this enhancement, rather than requesting one off sensor calculations or modifications, I feel it would be easier and more powerful to let the end user decide how to display the values. With my proposed enhancement I would be able to modify the value of the Download Rate by creating a custom expression. Below, the end user would be able to choose a custom operator (+, -, /, *, ^, etc.) then choose which operand would be the sensor value and which operand would be the custom value. Because performing math on a given value could lead to out of control decimal places, it would be ideal to include some level of precision, hence adding a section for precision.

       
      My custom Value Modifier (above) would take the Sensor Value and divide it by my own Custom Value (1000). Essentially this would turn 1200.1 into 1.20. Next, I could use the already existing Show unit functionality and modify my label from KB/s to MB/s. Now I would have the value I desire and have much more flexibility with all of the other sensor values.
      I hope my intentions are clear and that my enhancement request is easy to understand. Please reach out if there is anything you would like me to clarify.
       
      This should go without saying, but thank you for all of your hard work on this application. I use it daily and greatly appreciate all of its features!
       
       
       
       
    • By Dkr
      I would like the sensor panel be able to have a gauge for the free space on a network attached drive with a drive letter, currently it only allows gauges for local drives.
      A wifi signal strength meter would be nice also.
       
    • By Haaldor
      Hello!

      I often recommend my customers using Aida64 to collect information about the phone - to check for any problems and be able to help them further. Aida is absolutely amazing help here, but there is small problem...
      Some people are just not fluent with smartphones and instructing them how to find locally created file is a great pain for both sides;
      Answer for that - they are sending report as email to themselves. But right now the report is sent as email content, not .txt attachment.
      And some people are having hard time copying and creating .txt file from this. I know, you may think it's surprising, but trust me, we're encountering this problem on daily basis. Sometimes they are copying only part of the text; Sometimes they are copying without newline symbols;

      Option to send report as .txt attachment with email would be small and fast include, but would help hundreds of people.

      In the name of our whole team - thanks for consideration!
    • By sovasnight
      Information group devices too primitive. I was using this app for a long time but i have a need to display information for each camera on my device (sensor size , aperture, etc.). And i coud see this information about only 1 of 3 back and one front cameras.
      Please, add new feature: display more information about each camera on device, and additional information about supported camera2api functions.
      Device: Huawei P30 Lite.
      Android ver.10
      EMUI ver. 10.0.0.194
      P.S.
      Another applications for displaying HW information have detected each camera.
      P.S.S.
      Sorry for my broken english. And thx for this app.
       
    • By pimp1310
      hello,
       
      my native language is german, i hope my english is understandable.
       
      The Problem is, when i use my "aorus Graphic Engine" to control my 1080TI's leds, doesnt works anymore when i have aida64 in autostart.
       
      when i delete aida654 in my autostart the "Aorus graphics engine" works well.
      I tried to make a delayed start of aida64 but this didnt work.
       
       i need both programs, aida for my sensorpanel on the second screen, and aorus graphics engine to control my graphics card.
       
       
      any ideas ?
       
       
      THX
       
×
×
  • Create New...