The existing interface for adjusting sounds, through the use of the single control variable was rather awkward. In version 5 and beyond, I have added the provision to allow for separate variables to set volume, pan, and frequency settings for each sound. Their use is not mandatory. In fact you should only specify variables for the sounds you wish to use separate variables for, and only for the properties you wish to control separately for a given sound. In the sample configuration file in this archive, sounds 00,01, and 02 have separate volume variables specified. Sounds 01 and 03 have separate pan variables specified; and sounds 00 and 01 have separate frequency variables specified. While the previous interface for controlling sounds has not been changed in any way, the separate variables for volume, pan and frequency are evaluated after the legacy interface, so their values will override values set in that way. These extra LVars will not change whether the sound is playaing or not - they simply allow the xml programmer a much greater degree of flexibility when it comes to changing sound properties. These variables use the same range of values as does the old interface (-10000 to 10000 for pan, -10000 to 0 for volume, and whatever you want to experiment with for frequency.) With these LVars, you simply set them to the value you want, and the gauge will update the sound properties. You don't change the control variable. Doug Dawson contact@douglassdawson.ca Ottawa, Canada August 7, 2017