I would disable the overlap feature and add an '~n' to the name of the file, with 'n' being the amount of time for overlap into the next cut.
For example
StationID1~3.mp3
In this case, Zara will overlap the audio based on the amount of seconds before the end of that audio file.
So, this station ID will go to the next event 3 seconds before it actually ends.
This is handy for music tracks that have several seconds of silence at the end and you want to customize the segue into the next event without having to rely on the global overlap setting.
If it is a dry liner, you could do the following.
Dryliner~0.mp3.
This way, any dry liners will play in their entirety without cutting off the end of that liner.
You could almost do pseudo voice tracking with this method. . say you wanted to back announce a song up to the post. . you could disable the global overlap and insert the amount of seconds you want before the vocals started in the song in the voice track file.
Hope this makes sense (and I hope I got it correct. lol).
-M
One thing I wanted to add:
You DON'T have to put the ".mp3" at the end of the file name. Just the tilde (~) and number will do, e.g.,
The Boys Of Summer~9
That number cues the system to
start monitoring when the audio gets low enough to fire the next event. But you also have to set the volume level at which the system will fire, too. This is under "End of Song Detection" on the Options window. I have the FM set at -4db, and the AM at -6. So if you have a song set to fire the next event at, say, ~17, but the song is deemed too loud based on the settings you gave it, it will wait until the audio level drops to where you set it. Conversely, if the song is lower than the setting you programmed, it will fire at the number. The number after the tilde (~) is only where the system starts monitoring the file.
