I would like to know a bit more about the mechanism by which the audio files are transferred to/ from the DMA to/from the Alerter agent.
When you add an audio file to playback with an alarm, is that file uploaded to the DMA?
Is it then downloaded only when the file is needed to play for an alert?
Are all files transferred from DMA to Alerter upon login?
Are the files zipped and unzipped in the transfer process?
Does Alerter effectively close each wave file after it is played, or is it somehow held in a cache for future playback, such that an unplanned shutdown of Alerter could cause wave file corruption by not properly closing the audio file?
Hi Michael,
When you change something to the settings (e.g. adding an audio file), the settings are first saved locally and afterwards send to the server. When you open SLAlerter it will check if it has the latest settings stored locally. If not they will be loaded from the server including all the sound files. This means that SLAlerter has downloaded all the sound files before the first alarm entered SLAlerter.
When SLAlerter needs to play one of the sound files, it is played with Windows Media Player. As soon as the sound has been played, the file is released again, so nothing is kept in memory in SLAlerter. In case SLAlerter closes unexpectedly the sound file should not get corrupted.
Hi Michael,
If a change in the settings is detected all the audio files will be re-downloaded.
Michaël,
Thank you for the information. If it detects a change in setting will it re-download all of the audio files, or only the ones that have changed?