HOME | DD

TGonZ0 In reply to ??? [2016-04-14 15:14:33 +0000 UTC]

Thanks, glad you like them.

👍: 0 ⏩: 0

FailBail In reply to ??? [2016-03-26 00:44:33 +0000 UTC]

Hey, great skin!

I notice there's no place to monitor case fans, would this be easy to add myself or might you be able to add it in the future?

Otherwise keep up the great work!

👍: 0 ⏩: 1

TGonZ0 In reply to FailBail [2016-04-14 15:13:54 +0000 UTC]

Thanks.  I'll look into more fans.  Not sure how I will do it yet.  Maybe a new meter.  We'll see.

👍: 0 ⏩: 0

TGonZ0 In reply to DarkDarwin [2016-04-14 15:12:18 +0000 UTC]

Thanks for the nice comments.  I also wanted simple clean meters and decided to just make what I wanted.

👍: 0 ⏩: 0

AzzaNancazza In reply to ??? [2015-12-18 10:25:34 +0000 UTC]

Great skin! Just finished getting it all set up, and am very happy.

Quick question (read: request) - is it possible to add in another volume meter w/mute option for microphone?

👍: 0 ⏩: 1

TGonZ0 In reply to AzzaNancazza [2015-12-22 15:34:45 +0000 UTC]

Thanks, I'm glad you like it.  For now, there is not a good way to control the mic from Rainmeter.  I've looked around a bit, and have not found anything yet.  If a plugin is created that can control the mic, I can look into it then.

👍: 0 ⏩: 2

Exper1mental In reply to TGonZ0 [2016-02-19 06:38:04 +0000 UTC]

If your interested you actually should be able to control the mic with Rainmeter using either AutoHotKey (AHK) scripts or NirCmd.

Here's a simple AHK script someone posted on GitHub that toggles muting/unmuting the mic:
github.com/PProvost/AutoHotKey…

You should be able to use the AHK SoundGet command to return the mic volume and the SoundSet command to change the mic volume.

If AHK doesn't work NirCmd is probably your best shot with it's changesysvolume , setsysvolume and mutesysvolume commands.

Bear in mind that in instances where multiple mics are being used the end-user will most-likely need to be able select which mic to control, further complicating things. Controlling the mic probably isn't worth all the effect needed to integrate control with Rainmeter but I thought I'd toss this out there anyway.

Side note
You may want to update the version of the HWiNFO plugin you include with the skin, I've the old one may not run correctly in some instances on Rainmeter 3.3

👍: 0 ⏩: 0

AzzaNancazza In reply to TGonZ0 [2015-12-24 11:29:26 +0000 UTC]

Oh ok, no worries - thanks for looking into it anyways

👍: 0 ⏩: 0

TGonZ0 In reply to Emperorr [2015-12-04 03:44:46 +0000 UTC]

Hi Emperorr,  Well, now it has everything.  lol.  I added more GPU meters so you can have up to 4 running, each with their own settings window.  Enjoy.

👍: 0 ⏩: 1

Emperorr In reply to TGonZ0 [2015-12-21 12:36:57 +0000 UTC]

That was QUICK!

You're the man dude, love the meters!

👍: 0 ⏩: 0

TGonZ0 In reply to Emperorr [2015-12-02 17:53:06 +0000 UTC]

Thanks.  I did write most of the GPU skin with GPU0 in most all the variables and measure/meter names, but not all.  So, I should be able to fix that, and add a 2nd GPU skin without a huge effort.  I'll look into that real soon.

👍: 0 ⏩: 0

TGonZ0 In reply to Rubez2525 [2015-10-08 18:44:07 +0000 UTC]

Hi, I'm not sure I completely understand your question.  Did you create more Disk meters above H, and are now trying to add Temps to the Meters above H?  And you would like to add Drive temps above H to the Diskconfig.ini skin?  If so, it's not easy. Sorry.  I can probably clean up that skin, so it is easier to add more Disk temps.  What is the highest Drive letter you are using?

Let me know what you mean, and I'm sure we can work it out.

👍: 0 ⏩: 1

Rubez2525 In reply to TGonZ0 [2015-10-09 01:49:16 +0000 UTC]

Yes, that is pretty much what I mean. Adding the drive meters themselves are easy with the way you have it set up, but adding the temperatures to them through "Disk HWiNFO Settings" window (aka diskconfig.ini) is hard since it is still only C-H in the settings. I have disks B and W. I do see the fields like [measureInputCdriveTempEntry], etc. But I am not sure if copying and pasting and changing the letters will add them in nor do I know exactly all the things that need to be added to get the temp to work for added disks.

It may be too much to ask: But I suggest just simply including every letter in the alphabet by default. They could be organized into a single DiskMeter folder and have each one labeled something like [insert letter]diskmeter.ini. Obviously, I don't know how much work that would be for you or if it would break with the way you have it set up, but at least that system should work with anyone's hard drive setup.

On the topic of disks: This is a very minor issue/bug, but whenever there is no read/write values on the histogram, the maximum values (ones on the right) display "2" instead of "O B" like on the current read/write values (ones on the left). This is actually seen on your preview here with the idle disks. I just thought I mention it if you are still looking for bug reports.

👍: 0 ⏩: 1

TGonZ0 In reply to Rubez2525 [2015-10-09 02:44:38 +0000 UTC]

To make it a bit easier to add other drive letters, I am changing the Disk Settings skin and putting the code that creates each line into it's own file, and then including that.  It should be much easier to copy a the file to a new letter and add another include line.  Then do change the drive letter in that new file.  I'm still thinking about some other ideas though.

I like the idea of using variants for additional drive letters, but I am also thinking of trying to add a field to just type the drive letter you want for each Disk meter.  I'm not sure how each of these ideas will look and work in practice, but I think I can do something different to make them more configurable and still easy to setup.  I've tried really hard to make these as easy to configure as I can.

In the Disk Histograms, the number on the right is the max value of the Histogram at that moment.  Rainmeter is designed so that Histograms always display a minimum of 0-2.  So the max value will never be below 2.  That's just how Rainmeter works.  So when there is no activity (all values are 0) then the max possible value of the histogram display will still be 2.


You can add the Temps for your B and W drives yourself, manually, without using the Disk Settings skin if you wish.  You will have to edit 2 settings files for variables.

1.  edit  Rainmeter\skins\SimplePerMeters\resources \HWiNFO.inc  file
Scroll to the bottom, and copy the 3 variables from another drive, change the drive letter in the new variables, and set the parameters for each.

2.  edit  Rainmeter\skins\SimplePerMeters\resources \globalsettings.inc  file
Find the C:driveTempOnOff=0  settings, copy it and change the driver letter to your new drives.
0 = On
1 = Off

With those changes the Temps should show up on a refresh of the skin.
This manual method should be easier than you trying to edit the Disk Settings skin.  And you will have temps until I can work out a better way.

Hope that helps for now. 

👍: 0 ⏩: 1

Rubez2525 In reply to TGonZ0 [2015-10-09 03:01:16 +0000 UTC]

Ok cool. By the way, I did mod in a fix that does mask the "2" on the histogram. I just made a simple IF statement:

  if HistMax == 2 then
    HistMax = 0
  end

I just glued it into FindMaxHistValue.lua right before "return HistMax". So there is at least a way to cover it up.

👍: 0 ⏩: 1

TGonZ0 In reply to Rubez2525 [2015-10-09 04:05:31 +0000 UTC]

You can make that change for yourself if you like.  
But the smallest Max value of 2 is correct, the histogram height represents 0-2 for data values when all data points are 0.  The number on the Left is the current new data value, where the number on the right is what the histogram max is set to from auto scaling, smallest value being 2.

I have decided to go with a text field to type in the drive letter you want for each of the 6 drive meters.  That way you can have any 6 drive letters you like.  I have it working on my system, but I still have to clean up some code a bit, and test it out a bit more.

keep an eye out for a new version soon.

👍: 0 ⏩: 1

Rubez2525 In reply to TGonZ0 [2015-10-09 18:45:42 +0000 UTC]

Ok, neat. I will look out for it. For the change to the histogram: I think it would be more accurate to display the actual max read/write values shown on the histogram rather than the smallest scale on the histogram allowable by Rainmeter. I don't know, that is just my reasoning for changing it. As long as you are aware of it and it is not a bug, then that is fine.

👍: 0 ⏩: 1

TGonZ0 In reply to Rubez2525 [2015-10-09 20:45:24 +0000 UTC]

I'll try to explain the numbers I put on the histograms, there is no bug, it is all working properly.

The value on the Left side is the data value that was just added to the histogram.  This number on the left should be constantly changing as the incoming data changes.  I think this is what you are looking for.  Examples:
R 0 B = Read zero Bytes
R 96 kB = Read 98,304 Bytes
W 237 kB = Write 242,688 Bytes

I am using the Auto-Scale feature of the Histogram meter.  When the Auto-Scale is used, the histogram will change the range of data values being displayed based on the largest data value in the current Histogram display.

So, it would be a scale of 0-2 when all data is 0 (idle disk).  Number in the right of the histogram is 2.  The Number on the left will be R 0 B.

When disk activity happens and a Read of say 14530 bytes/sec occurs, (number on left will be "R 14 kB" for one second) the Histogram will change the scale to display data ranging from 0 - 16384, or 0 - 16k.  Then the number in the right of the histogram is 16k, and will remain 16k until the data value of 14530 slowly slides off to the left and disappears from the histogram.  At that time, a new max will be calculated for the number on the right.

I hope that helps.

👍: 0 ⏩: 1

Rubez2525 In reply to TGonZ0 [2015-10-09 23:02:00 +0000 UTC]

I know how it works.

👍: 0 ⏩: 0

MarcusCorbacho In reply to voodoo-curse [2015-09-20 21:25:31 +0000 UTC]

i.imgur.com/Eu6hqhV.png

These are my Configurations. Unfortunately the AMD sensors not match the NVIDIA, but is ok. On % just select the D3D Usage because is on % on HwInfo...

PS. Keep working on the these. Excellent !

👍: 0 ⏩: 2

voodoo-curse In reply to MarcusCorbacho [2015-09-24 20:43:25 +0000 UTC]

That certainly gets closer to an accurate reading, thanks

👍: 0 ⏩: 0

TGonZ0 In reply to MarcusCorbacho [2015-09-21 00:42:02 +0000 UTC]

If you could show me the details from HWiNFO and GPU-Z for the AMD GPU, I would like to understand what info is available.  Maybe I can make a change to help the AMD display the Memory better.
Here is an example of my system of what I would like to see from your system.  And tell me how much memory your GPU has.  Thanks.

i.imgur.com/hnZUnw5.jpg

(I use "GPU Memory Usage, %" and "GPU Memory Allocated, MB")

👍: 0 ⏩: 1

MarcusCorbacho In reply to TGonZ0 [2015-09-21 10:14:33 +0000 UTC]

i.imgur.com/CG2UYbU.png

Here it is.

👍: 0 ⏩: 0

TGonZ0 In reply to voodoo-curse [2015-09-13 01:46:43 +0000 UTC]

Yeah, getting the correct sensors can sometimes be a bit tricky.  I'll explain as best I can, what I'm using with my GeForce GTX970.    I see you have a R7, but hopefully you have equivalent entries to choose from.

I calculate the Max installed Memory on the card based on the Mem Used in MB and the Mem Used in %.  As you see, if these are not correct, it will not calculate correctly.

On my card, I see 2 entries for getting the % used.
GPU Memory Usage (%)   <-- I use this one.
GPU D3D Usage (%)

As I understand these 2 settings, the D3D is always less because it only shows what GPU memory is allocated for D3D operations.  Where the GPU Memory Usage show all GPU memory allocated as a %.  Use the GPU Memory Usage (%) for the GPU0 MemUsePercent.


Next for the MB sensor I see 3 possible entries.
GPU Memory Allocated (MB)      <-- I use this one.
GPU D3D Memory Dedicated (MB)
GPU D3D Memory Dynamic (MB)

Again, the D3D are only showing a smaller usage of only what the D3D is using.  The GPU Memory Allocated show the total about used in MB.  Use the GPU Memory Allocated for the GPU0 MemUseMB.

So, as best I can tell, you do not use any of the D3D sensors.
Hopefully your ATI/AMD R7 has similar sensor entries as mine does to choose from.

Hope that helps.

👍: 0 ⏩: 1

voodoo-curse In reply to TGonZ0 [2015-09-24 20:42:58 +0000 UTC]

I see. Unfortunately my card does not have a "GPU Memory Allocated" sensor value.

I plan to replace it with an Nvidia card soon anyway, so hopefully this is only a temporary issue.

👍: 0 ⏩: 1

TGonZ0 In reply to voodoo-curse [2015-09-24 20:59:30 +0000 UTC]

If you have a AMD graphics card, get the new version 2.0.7 above.  I put some settings for AMD cards in the GPU settings.  It's not going to show the full memory allocated, but it will be as close as we can get.  AMD does not provide the full mem allocated in it's API.  
With the new version, you just type in your cards max memory, and then use the D3D Dedicated memory.  That will be close enough.

👍: 0 ⏩: 1

voodoo-curse In reply to TGonZ0 [2015-09-27 19:18:53 +0000 UTC]

So, funny story.... I just decided to get an Nvidia card today anyway. But I'm sure there are plenty of people who can still enjoy the new functionality. Thank you for your responses and support!

👍: 0 ⏩: 0

TGonZ0 In reply to MarcusCorbacho [2015-09-08 18:11:40 +0000 UTC]

Hi MarcusCorbacho.  Your English is good enough, I do understand your question.
You would like to dim the blue of the meter behind the RPM so you can read it better.
That is easy to do.  I can add that to a future release.  But you can make the change now your self if you like.

Find and edit the file below in notepad or whatever text editor you like.  This files is small, so it will be easy.
Make 2 changes so the 2nd section in that files looks the same as below.
Change W=50 to W=45, and then add the SolidColor=0,0,0,100 to the bottom.
Save and then refresh the CPUmem meter.
If you would like the background of the RPM text a little darker, increase the 100 to maybe 150.  But 100 should be good enough to make it more readable.

.....\My Documents\Rainmeter\Skins\SimplePerfMeters\@ Resources\CPUmemFan.inc


[meterCPU0MBFanRpm]
Meter=String
MeasureName=measureCPU0MBFanRpm
MeterStyle=styleLeftTextSmall
X=[MeterCPUHistogram]
Y[MeterCPUHistogram:Y] + [MeterCPUHistogram:H] - [meterCPU0MBFanRpm:H])
W=45
H=12
Text=%1 rpm
TransformationMatrix=#meterScaleCPU #;0;0;#meterScaleCPU #;#meterScaleCPU #;#meterScaleCPU #
DynamicVariables=1
Hidden=#FanOnOffSelect #
SolidColor=0,0,0,100



Let me know how that goes.

👍: 0 ⏩: 1

MarcusCorbacho In reply to TGonZ0 [2015-09-08 20:35:51 +0000 UTC]

Humm, was not really that...
In fact is te reduce the lenght of blue histrogram...
On default The blue histrogram starts on below of "z" from "MHz" and it ends after "C" of "CPU" e.g.
My sugestion is, it is possible to blue histogram starts below of "z" from "MHz" and it ends before the "e" from "usage"

So that the blue lines doesn´t pass below of the RPM
I tried editing but no sucess !

👍: 0 ⏩: 1

TGonZ0 In reply to MarcusCorbacho [2015-09-08 22:14:54 +0000 UTC]

Oh I see, you wanted to push the text to be above the blue histogram meter, so the blue meter can be seen easier, no text on the blue.  That could be done, but would make the meter a bit taller.  I meant the CPU usage histogram to be something you just glance at briefly to see if the CPUs have been very busy or if they have been idle for the last couple of minutes.  I put the text over the histogram because they are associated to the CPU, and so it would not be a large meter.  The Fan rpm was a recent request, and I did not see a better place to put it.

One possible arrangement would be all the text to the left, and push the histogram to the right.
I'll think about some ideas on this.  My goal was neat, clean, and simple meters.

👍: 0 ⏩: 1

MarcusCorbacho In reply to TGonZ0 [2015-09-09 11:15:57 +0000 UTC]

And if just re-alocate to another position the info of RPM ?
Leave the Blue bars as it is...
And put the CPU rpm between CPU % in use and pages/sec

👍: 0 ⏩: 1

TGonZ0 In reply to MarcusCorbacho [2015-09-11 03:23:10 +0000 UTC]

That may be a better look.  I've been testing a couple of different configurations.  
Make this change to move the rpm to the top center.  See if that looks better for you.

Change the X= and Y= in this file, to what I have below:
.....\My Documents\Rainmeter\Skins\SimplePerfMeters\@ Resources\CPUmemFan.inc

X= ([MeterCPUHistogram: X] + 60)
Y=[MeterCPUHistogram:Y]

Save and refresh the CPUmem skin.
Let me know what you think.

There is only one X= and one Y= in the file.  So it should be easy.

IMPORTANT:  there is no space between the colon( : ) and X above.
I put the space there because it was making a emoticon.  When you type this in, do not put a space between the : X.

👍: 0 ⏩: 1

MarcusCorbacho In reply to TGonZ0 [2015-09-11 12:45:21 +0000 UTC]

That was what i was thinking !!!!
Now that rocks !
Yes ! You did it !

👍: 0 ⏩: 0

sascha62 In reply to ??? [2015-09-02 19:35:47 +0000 UTC]

This skin is great. I use it with transparent bachground color - it's amazing.
Only one question: How I could change (CLOCK ) the English name of the day to German?

👍: 0 ⏩: 1

TGonZ0 In reply to sascha62 [2015-09-04 04:00:34 +0000 UTC]

I'm glad you like it.  I had not looked into any Locale customizations.  This started as meters for myself, but I have added many features to it as requests have come it.  I'm not planning on doing a full language selection for all the meters, but I do see a Locale setting for the Date/Time function I am using in Rainmeter.  So, it is possible to display the Day and Month in other languages.  "FormatLocale=Local" is suppose to use whatever your Windows is set to for Language Locale.  And "FormatLocale=de-DE" should set it to German if Local does not work.

I will probably add this into the next version, but until then, you can edit the Clock.ini file, look for these 2 sections and add the FormatLocale=Local to them as shown.  Save and Refresh the Clock skin and you should be good.  If "Local" does not work, try "de-DE".

[measureMonth]
Measure=Time
Format=%b
FormatLocale=Local


[measureDay]
Measure=Time
Format=%a
FormatLocale=Local


I hope that helps.

👍: 0 ⏩: 1

sascha62 In reply to TGonZ0 [2015-09-04 09:30:00 +0000 UTC]

Hi TGonZo,
thanks a lot - it's working!

👍: 0 ⏩: 0

yojakeo In reply to yojakeo [2015-08-31 04:30:18 +0000 UTC]

BUT thing is. The HWiNFO part of the pack won't work.
I've looked the the comments.
I tried copying the HWiNFO.dll into a plugin folder (I didn't have a plugin folder. so I made one)
and I checked the Sensor ID and and Entry ID.
Some help please?

I'm running Windows 8.1 Pro if that helps.

👍: 0 ⏩: 1

TGonZ0 In reply to yojakeo [2015-09-04 04:13:56 +0000 UTC]

Thanks for the nice comments on my skin.  I have not used this on Windows 8, only on Windows 7, but I would think Rainmeter should behave the same.  If Rainmeter is installed correctly, then "C:\Program Files\Rainmeter\plugins" folder should exist and should have about 22 dll files in it from the install.  If it is not there, then your Rainmeter may be installed in a different location, or you may need to re-install Rainmeter.  Either way, once you find the plugins folder with the other dll files, I would try to copy the HWiNFO.dll file to that location with the other dlls, and try it again.

Those are the only suggestions I have.  If you continue to have problems with it, I would recommend posting questions to  www.hwinfo.com/forum/   and to  rainmeter.net/forum/  for more help.  I'm sure someone at one of those forums would be able to provide more help.  Good luck.

👍: 0 ⏩: 1

userforusing In reply to TGonZ0 [2015-09-04 16:14:52 +0000 UTC]

It should work on 8.1. I'm running it on Windows 10 with no problems. My Rainmeter is portable. HWInfo had to be installed to work though (at least I couldn't get it working with the portable version of HWI)

👍: 0 ⏩: 0

TGonZ0 In reply to kbuis [2015-08-29 05:20:18 +0000 UTC]

I think you need to change all the ID codes in the GPU settings skin to use the GPU you would like to view.

Click the Icon (next to the yellow text) in the GPU settings skin, and that will open the HWiNFO Shared Memory Viewer program, and that will show you the HEX id codes for everything that HWiNFO is collecting data on.

Find the GPU you want to monitor in the Shared Memory Viewer, and change all the HEX IDs in the GPU settings skin.
Make sure you change the Sensor ID as well as the Entry ID for each line.
That should get it to view the GPU you would like.

Hope that helps.

👍: 0 ⏩: 0

TGonZ0 In reply to MarcusCorbacho [2015-08-23 18:31:38 +0000 UTC]

Hi,
Thanks.  I'll look at adding that in on the next version.

👍: 0 ⏩: 0