RainMaster wrote: ↑July 26th, 2021, 12:20 am
Hi! I started making my first skin the other day because I wanted an easy single-click method for muting/unmuting my microphone. So far I have everything working like a charm by using SoundVolumeViewer to mute and unmute the mic, however I want the state the mic was in on reboot/shutdown to be remembered by the skin. It seems the way to do this is either by using SoundVolumeViewer to get the current state of the mic when the skin starts up, or perhaps PowerShell even, and set the image accordingly. I'm not quite sure how to actually go about this though.
Any help is greatly appreciated. Since I'm still learning I don't quite know how to pass the output of a program to Rainmeter and set the image accordingly, or if I can/need to define multiple Measures to process the output. I got this far mostly by looking at examples and working backwards from there. (My name is what I hope to become, not what I am
There you go - this works for me, a bit slow, but it does. Didn't test it after a restart and I can't guarantee it will work flawlessly since there are a lot of things that happen at restart and the order in which they do or how busy is the PC at that time could have an impact on functionality, but hopefully it will work well:
Code: Select all
OnRefreshAction=[!CommandMeasure MeasureGetMicMute "Run"]
Information=Toggles microphone between muted/unmuted
License=Creative Commons Attribution - Non - Commercial - Share Alike 3.0
Parameter=#@#Addons\SoundVolumeView.exe /Switch "Realtek High Definition Audio\Device\Microphone\Capture"
FinishAction=[!CommandMeasure MeasureGetMicMute "Run"]
Parameter=#@#Addons\SoundVolumeView.exe /stab "" | #@#Addons\GetNir.exe "Muted" "Command-LineFriendlyID='Realtek High Definition Audio\Device\Microphone\Capture'"
FinishAction=[!SetOption MeterMicButton ImageName "[MeasureGetMicMute]"][!UpdateMeter MeterMicButton][!Redraw]
LeftMouseUpAction=[!CommandMeasure MeasureSetMicMute "Run"]
I shuffled some things in your original code, corrected a single thing, and added some things for proper distribution of the skin, if it'll be the case. So:
is not a valid option, and it's not a valid option there, therefore I removed it
- shortened the skin update to 1 second since it doesn't harm anything in this case if you let it that way
- removed setting the variables since I had another idea, see below
- made 2 RunCommand measures, one to get and one to set the mic mute status (the latter is your original one for the most part)
- since setting some variables in itself means nothing when it comes to the success of a command (e.g. the command could fail or be delayed so the variable could yield an inaccurate value), I thought it was better to actually get the mic mute status somewhat similarly with how you set it (reference here
towards the middle of the page, section "Get sound level information from command line"), especially since this was also needed to get that status after a restart, thus the "get" measure
- the "get" measure will not only run at skin refresh, but also after the "set" measure (through its FinishAction), to make sure the status was set properly
- I manipulated the string result of the "get" measure through some simple regular expression Substitute
, so it can be used to set the image name in the meter as well
- I added the SoundVolumeView and GetNir tools into an appropriate folder in the @Resources folder of your skin, so that it will work even if you think of distributing such a skin (e.g. the other users might not have these tools installed, or they might not be located where you installed or copied them in the case of your system)
- remembering the value of a variable after a skin refresh could have been much easier with the help of !WriteKeyValue bang
, which writes variable values to the desired file (e.g. [!WriteKeyValue Variables MicOn #MicOff#][!WriteKeyValue Variables MicOff #MicOn#]
or something along those lines), but then, if you somehow unloaded the skin before setting the mic mute status to a different value, the remembered value would be incorrect since it would be based on the last value it has while the skin was still active
- the key to getting the mic mute status was to use another NirSoft tool to pass the output of the SoundVolumeView (which is to the exit status
of the program) to STDOUT
with the help of GetNir, because RunCommand also gets its value from STDOUT after running its program + parameters
- the Program option
can be omitted from a RunCommand measure in most cases by putting everything into the Parameter option (one exception from this is PowerShell, by the way)
Other than that, that's a very good attempt for your first skin after such a brief adaptation period - very few mistakes, well done!
If you continue this way, you'll be on route to become what you hope to be...
P.S. Getting this done using PowerShell would have been a bit trickier, if possible that is.
You do not have the required permissions to view the files attached to this post.