Myriad STS: Why is there a source and destination location for Log files?

Myriad STS: Why is there a source and destination location for Log...

Peter Jarrett
Peter Jarrett
Forum Sage
Forum Sage (413K reputation)Forum Sage (413K reputation)Forum Sage (413K reputation)Forum Sage (413K reputation)Forum Sage (413K reputation)Forum Sage (413K reputation)Forum Sage (413K reputation)Forum Sage (413K reputation)Forum Sage (413K reputation)

Group: Broadcast Radio
Posts: 1.8K, Visits: 3.7K
While Myriad STS is running, it keeps the log file open so it can read and write to it as nescessary. This is to stop the file from being changed by the advert scheduling system while STS is in the middle or playing or otherwise manipulating the file.
Because of this, there has to be a mechanism to allow new or updated files to be copied into the system to be used. To achieve this, STS periodically checks the "source" location for new files and then copies them to the "destination" location which is where it actually runs from.
The log transfer process is relatively simple - whenever STS isn't actively playing an advert break it periodically checks the source folder looking for the file with the same filename as the "current" log file it's running from.
If it finds that the "source" file has changed since the last time it looked (i.e. been regenerated from your traffic system, or even just opened and "saved" in notepad which changes the lastmodified date) then it closes the file in the destination location, deletes it, copies the file from the source to the destination and then re-opens it. How often this check is done is configured by the "Check for new log files every X seconds" in the Log File Settings window.
STS only changes to a different log file in 3 situations:
  • When the last advert break in the current file is played, STS automatically looks for the "next" log file in the destination location. If it finds it it then loads it up. If it can't find it, it checks for it in the source location and if it finds one it copies it to the destination and then loads it up.
  • If Myriad instructs STS to cue up an advert break for a different day than the current log file, STS closes the current file and repeats the above cycle for the day it's been told to play. This is so a presenter can theoretically drag an advert break from tomorrow into the end of today
  • If you are using the "Automatic reload" options then when the clock ticks over to a new day and the reload option fires, it automatically loads the appropriate day.
Note: in most situations, Myriad users should never use the reload options as Myriad effectively tells STS when a log should be loaded and we've seen a fair few problems in the past where STS and Myriad have a falling out becuase STS decides it needs to reload the file and cue up a different break. The Log reloading options are more useful for situations where STS is being fired by hardware or serial commands. This is because if a command never reaches STS or is corrupted, it can lead to STS falling out of sync with a remote playout system and playing the wrong breaks when triggered.

Peter Jarrett, Technical Director
Broadcast Radio Ltd.

Bill Bailey: No win, no fee, no basis in reality. Just a room above a minicab office in Acton and a steady stream of greedy simpletons whose delusion is only matched by their clumsiness


Reading This Topic

Existing Account
Email Address:


Select a Forum....

Broadcast Radio Forums