I have an audio visualizer based on radian_vibrance_visualizer_1.3 skin.
This skin uses Lua to generate the .ini files for the visualizer lines.
I have tweaked it a bit to suite my skin but one thing I can not get it to work.
The line length of the visualizer is related to the volume .
The line length can be set with the "amplifier" variable
When I change the volume (which I measure) I want the variable "Amplifier" to increase or decrease so I have more or less the same line length independent of the volume
I see the variable "Amplifier" change when I change the volume in the log file within Rainmeter so that part is working
I think somehow I must call the Vibrance Lua script when "Amplifier" variable changes to generate NEW .ini files with the changed "Amplifier" variable when I change the volume but I do not know how.
Here is the skin file:
Vibranci_.rmskin
All help is appreciated
You do not have the required permissions to view the files attached to this post.
But when I now change the volume the "sensitivity" variable value written to the VibranceVariables.inc file is always one instance to low or to high (late) depending if I go Up or Down in volume.
In rainmeter logging all is fine and working but the written variable is wrong.
JamX wrote: ↑January 13th, 2021, 10:09 pm
I have changed part of the code to:
There is a mistake in the above IfConditions. For instance IfCondition is true ONLY when [MeasureVolume] is exactly 100, because you've used equality: IfCondition= ((MeasureVolume = 100) && (MeasureVolume >80)). Replace all those equalities in the first condition of all IfCondition options (at least from 1 to 5), like this: IfCondition= ((MeasureVolume <= 100) && (MeasureVolume > 80)).
Not sure this fixes the issue, but it has to be done.
JamX wrote: ↑January 14th, 2021, 5:45 pm
Strange that with the option where I use !SetVariable it is not working properly.
Make sure you've added a DynamicVariables=1 option to the measure / meter where you've used the Sensitivity variable (when working with the !SetVariable bang).
JamX wrote: ↑January 14th, 2021, 6:42 pm
With the latest (working) code I delete it because there it is not needed.
Yep, it's not, however I'd think more times before using that solution, because it refreshes the skin every time you're changing the volume and such an approach has to be treated sceptical: https://forum.rainmeter.net/viewtopic.php?f=5&t=22739&p=119966&p119966#p119966
Please post the whole and actual code of your skin, to can take a look, even if it has been posted before, because you've update it, if I'm not mistaken, so I'd like to have the entire code.
balala wrote: ↑January 14th, 2021, 7:06 pm
Yep, it's not, however I'd think more times before using that solution, because it refreshes the skin every time you're changing the volume and such an approach has to be treated sceptical: https://forum.rainmeter.net/viewtopic.php?f=5&t=22739&p=119966&p119966#p119966
Please post the whole and actual code of your skin, to can take a look, even if it has been posted before, because you've update it, if I'm not mistaken, so I'd like to have the entire code.
I need the !Refresh bang because the Lua scrips needs to be "refreshed" to generate new Lines.inc file for new sensitivity variable setting.
I have not found an other way to call the lua scrips after the volume/sensitivity changes.