The answer to your question depends on exactly what your final script does; and Torben did say ‘such as a short silence element.’
Another way to indicate the place where a set of ad. spots ‘might be’ would be to add a DUMMY item, edited so that it has a specific Artist. Assuming you are using mAirListDB, the way I would tackle that is to open mAirListDB and do this:
[ol][li]Create a new virtual Folder for each possible ad. spot in an hour. Name each folder (for example) AdSpot1, AdSpot2, etc.[/li]
[li]Make sure AdSpot1 is the current selected (clicked) Folder, then click New Item, Dummy.[/li]
[li]In the Artists field on the Properties dialog of the new Dummy item, type AD SPOT 1,then click OK.[/li]
[li]Repeat the last two steps for each Folder you created in step 1. You should now have one Folder for each possible ad. spot in your hour, with a single DUMMY item in each Folder, each with Artists the same as the Folder name.[/li]
[li]Amend your Hour Template(s) to add Items for AdSpot1, AdSpot2, etc. at the right place in the hour. Make sure each of these Items is fixed and not optional.[/li][/ol]
When you generate Database Playlists from these Hour Templates, you will have DUMMY elements in each hour’s Playlist at each point where there could be an ad. break. Because there is only one Item in each Folder, the Mini Scheduler will always insert that specific Item when that Folder is in an Hour Template. (This technique is useful generally, to ‘force’ a specific Item into a Playlist. ;))
These Items can easily be found by a mAirList script later, and positively identified as an ‘ad. spot placeholder’ by its Artists (does the Artists of this DUMMY Item equal ‘AD SPOT something’?). So if you use DUMMY Items for anything else in your Playlist (like top of hour markers, for example), the script won’t replace ‘other’ DUMMY Items with an ad. spot.
You don’t have to use numbers (AD SPOT 1): anything in a sequence (A, B, C) would be fine. Or, if you don’t need to be so specific, you could use just one AD SPOT Item; but having a sequence means you could (for example) have ad. spots 2 and 4 of four per hour ‘populated’ and spots 1 and 3 empty. It would be much harder to do that without some kind of unique identifier per potential spot within the hour!
Finally, I’m fairly sure that mAirListScript can process Database Playlists directly (right, Torben?). If so, you could for example have a mAirList script which you run once a day at maybe 2300, to ‘insert’ the ads. for the following day directly into your Database Playlists.
Torben is right about using the times being a possible problem. Maybe your ‘pre-processing’ script could use some kind of ‘time block’ to work out which ad. set should go into which spot in an hour. So let’s say three spots per hour, ‘ideally’ at 10, 30, and 50. Any break with a start time from 00-20 (minutes) would be spot 1, 20-40 would be spot 2, and >40 would be spot 3. A system of that sort should work in most cases. Obviously, the closer you can ‘synchronise’ your ad. scheduling system so that all your ad. break files are generated with a start time close to your ‘ideal’ times of ad. breaks in mAirList, the better this system will work!
Hope that helps.
BFN
Cad