I had a quick look into it - please open up your volume mixer, and watch it while "testing" volume in the config for the alarm plugin.
This works here - therefore I'm not convinced that the volume setting change _causes_ this (maybe it triggered an error though).
There are serveral "dirty" sections in the alarm plugin code which cause exceptions here and some hardcoded stuff like paths etc...
This works here - therefore I'm not convinced that the volume setting change _causes_ this (maybe it triggered an error though).
There are serveral "dirty" sections in the alarm plugin code which cause exceptions here and some hardcoded stuff like paths etc...