REQUEST NEW FEATURE - Date in the Custom Gauge

[BHSY]

2 minutes ago, COSTAJUNIOR said:

The project is turning out great! But with that many states, isn't the save process getting heavier or taking longer than usual?

When I import and export my old sensor panel skin that contains many states and sensors using the latest AIDA64 Beta version, the saving time is normal (fast).

In the older version, the time to save my file is around 1 min 30s. I'm not sure if it has something to do with my newly upgraded memory RAM. I'm using 64GB CL30 6000 MHz. My older RAM is 32GB CL 40, so that it's a big difference in response time.

Also, if you're still worried about saving time, I advise you to use a smaller image size. For example, save all 100 images using only the clock hand and the base as part of the background image. See screenshot below.

[Fiery]

1 hour ago, COSTAJUNIOR said:

The project is turning out great! But with that many states, isn't the save process getting heavier or taking longer than usual?

The total number of sensor slots are over 3000 (!) by now, so adding 10 more doesn't really affect overall performance of the rendering engine or the configuration window behavior.

[COSTAJUNIOR]

1 hour ago, BHSY said:

When I import and export my old sensor panel skin that contains many states and sensors using the latest AIDA64 Beta version, the saving time is normal (fast).

In the older version, the time to save my file is around 1 min 30s. I'm not sure if it has something to do with my newly upgraded memory RAM. I'm using 64GB CL30 6000 MHz. My older RAM is 32GB CL 40, so that it's a big difference in response time.

Also, if you're still worried about saving time, I advise you to use a smaller image size. For example, save all 100 images using only the clock hand and the base as part of the background image. See screenshot below.

Interesting comparison! The difference between 32GB CL40 and 64GB CL30 is definitely significant, especially for tasks that involve reading and writing large files — so it makes sense that the save time improved with the new RAM.

I also agree with the tip about optimizing images: the smaller and fewer the unique files in the skin, the faster the saving process will be. Using a common base as the background and separating only the dynamic elements (like the clock hand) is a great practice to maintain performance. Smart move! 😉

[Fiery]

@Surjeet @BHSY @JariKoi @COSTAJUNIOR @rinaldop @Garageman

Here's the next update with the following new sensor items implemented

• hour (1-12)
• hour (0-23)
• minute
• second

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

[Surjeet]

1 hour ago, Fiery said:

@Surjeet @BHSY @JariKoi @COSTAJUNIOR @rinaldop @Garageman

Here's the next update with the following new sensor items implemented

• hour (1-12)
• hour (0-23)
• minute
• second

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

WoW, 

Its PERFECT and FLAWLESS!!

Now, we will see next generation level of sensor panels 🔥

Thank you! 🙏

[BHSY]

25 minutes ago, Surjeet said:

WoW, 

Its PERFECT and FLAWLESS!!

Now, we will see next generation level of sensor panels 🔥

Thank you! 🙏

@Fiery@Surjeet How many images must I use for hours, minutes and seconds? Also, what are the min/max values used for each of them? I can't seem to get it to work unless I use the old time gauges using 4 sensors for hours (180 images), and 15 sensors for minutes (60 images). This method is closer to accuracy.

I can get the seconds to work using 61 images; the min/max value is 0 and 61, but sometimes it skips a second.

Thanks.

[Fiery]

1 hour ago, Surjeet said:

WoW, 

Its PERFECT and FLAWLESS!!

Now, we will see next generation level of sensor panels 🔥

Thank you! 🙏

Thank you!

[Fiery]

15 minutes ago, BHSY said:

@Fiery@Surjeet How many images must I use for hours, minutes and seconds? Also, what are the min/max values used for each of them? I can't seem to get it to work unless I use the old time gauges using 4 sensors for hours (180 images), and 15 sensors for minutes (60 images). This method is closer to accuracy.

I can get the seconds to work using 61 images; the min/max value is 0 and 61, but sometimes it skips a second.

Thanks.

For the new items the ranges are:

•     hour (1-12): 1 to 12
•     hour (0-23): 0 to 23
•     minute: 0 to 59
•     second: 0 to 59

 

[COSTAJUNIOR]

3 hours ago, Fiery said:

@Surjeet @BHSY @JariKoi @COSTAJUNIOR @rinaldop @Garageman

Here's the next update with the following new sensor items implemented

• hour (1-12)
• hour (0-23)
• minute
• second

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

Awesome! Excellent update — these new hour, minute, and second sensors will open up more possibilities for real-time visuals. Thank you so much for this! I’m already imagining tons of ideas 😎👏 Let’s test it out!

[BHSY]

2 hours ago, Fiery said:

For the new items the ranges are:

•     hour (1-12): 1 to 12
•     hour (0-23): 0 to 23
•     minute: 0 to 59
•     second: 0 to 59

 

Thanks. I got it.🙏

I try playing with the states, and it depends on where I start. Either I start at 12:00 or 1:00.

For the hours, I might use the old time gauges that use 4 sensors and 180 images. Almost accurate.

Tomorrow, I will try testing using more images on the new hours gauge type.

hours (1-12): states 0-11 (12 images) - starts from 1.00 - 12.00
hours (0-23): states 0-23 (48 images) - starts from 12.00 and ends at 11.00. 24 images (day) + 24 images (night)

The best part is I can now show seconds Hands on my clock, and it moves the same as the Windows 11 clock seconds.💪And I only need 1 sensor for minutes. Awesome! 😃

minutes: states 0-60 (61 images) - start from 12.00 to 12.00
second: states 0-60 (61 images) - start from 12.00 to 12.00

Thank you!

Edited Sunday at 05:44 PM by BHSY

[BHSY]

2 hours ago, Fiery said:

For the new items the ranges are:

•     hour (1-12): 1 to 12
•     hour (0-23): 0 to 23
•     minute: 0 to 59
•     second: 0 to 59

 

I forgot to mention that the new time gauge did not show the default values when I selected it. Can you show the default value? Thanks. 

[Fiery]

9 minutes ago, BHSY said:

I forgot to mention that the new time gauge did not show the default values when I selected it. Can you show the default value? Thanks. 

Yes, we missed to implement that.  It will be done in the next beta update.

[Surjeet]

16 hours ago, BHSY said:

@Fiery@Surjeet How many images must I use for hours, minutes and seconds? Also, what are the min/max values used for each of them? I can't seem to get it to work unless I use the old time gauges using 4 sensors for hours (180 images), and 15 sensors for minutes (60 images). This method is closer to accuracy.

I can get the seconds to work using 61 images; the min/max value is 0 and 61, but sometimes it skips a second.

Thanks.

I simply checked the numbers for now.  Hour, Minute came perfect and seconds were increasing perfectly.

I will test it with images very soon. However, please feel free to share the BEST and the correct way to use and utilize it when you tested it. It will be of great help! Thank you!

[BHSY]

I finally completed a functional clock and date sensor gauge. 

For the hour gauge, I used the 'Time' gauge type (86399), which will show the hour hand moving. The process of creating hours hand using 5 sensors, 240 images for AM and 240 images for PM is too complex and difficult for me to explain. I used Excel spreadsheets to calculate the min/max values. Click the screenshot below and click the zoom icon to view the Excel spreadsheet image.

To me, I'll use the 'Hour (1-12)' and 'Hour (0-23)' for digital time, for example, 12:00, 17:00, 13:00, etc.

For the minute's hand, I used 61 images (_00.png to _60.png), from 12.00 to 12.00, and the min/max value is 0 and 60.

For the seconds, I used 61 images (_00.png to _60.png), from 12.00 to 12.00, and the min/max value is 0 and 60. 

  

@Fiery 

The minutes and seconds sync very well with my OS time. However, for the second, some of them will skip a second, even using 'Simple Sensor Item'. For example, from 24s it jumps to 26s, skipping 25s. Please watch the above video. Is there any way to improve the seconds without skipping? It's ok if there's nothing that can be done about it. I'm quite satisfied with how the new time and date gauges work.

AIDA64 is the best customization sensor panel. 

Thank you to you and your team for making this possible. Well done!🥰💖

 

 

Edited 19 hours ago by BHSY

[Fiery]

1 hour ago, BHSY said:

I finally completed a functional clock and date sensor gauge. 

For the hour gauge, I used the 'Time' gauge type (86399), which will show the hour hand moving. The process of creating hours hand using 5 sensors, 240 images for AM and 240 images for PM is too complex and difficult for me to explain. I used Excel spreadsheets to calculate the min/max values. Click the screenshot below and click the zoom icon to view the Excel spreadsheet image.

To me, I'll use the 'Hour (1-12)' and 'Hour (0-23)' for digital time, for example, 12:00, 17:00, 13:00, etc.

For the minute's hand, I used 61 images (_00.png to _60.png), from 12.00 to 12.00, and the min/max value is 0 and 60.

For the seconds, I used 61 images (_00.png to _60.png), from 12.00 to 12.00, and the min/max value is 0 and 60. 

  

 

@Fiery 

The minutes and seconds sync very well with my OS time. However, for the second, some of them will skip a second, even using 'Simple Sensor Item'. For example, from 24s it jumps to 26s, skipping 25s. Please watch the above video. Is there any way to improve the seconds without skipping? It's ok if there's nothing that can be done about it. I'm quite satisfied with how the new time and date gauges work.

AIDA64 is the best customization sensor panel. 

Thank you to you and your team for making this possible. Well done!🥰💖

 

 

Wow what a layout 🤘 😍 

As for second skipping, try to lower the SensorPanel update rate to 500 milliseconds or even 200 ms.  If it doesn't help, then it means either the collection/measurement of sensor items takes too long, or rendering your exquisitely complex SensorPanel layout takes too long.

[BHSY]

7 minutes ago, Fiery said:

Wow what a layout 🤘 😍 

Thank you for your compliment.🙏

7 minutes ago, Fiery said:

As for second skipping, try to lower the SensorPanel update rate to 500 milliseconds or even 200 ms.  If it doesn't help, then it means either the collection/measurement of sensor items takes too long, or rendering your exquisitely complex SensorPanel layout takes too long.

I lower the SensorPanel update rate to 500 ms or 200 ms, and it helps. Thank you so much🙏. Now, everything looks perfect.👌😊.