Simian 2.3 Now Available with Support for Windows XP, 7, 8/8.1, and 10 on 32bit or 64bit platforms!
April 25, 2018
Multi-Segment Recording for Time-Shifting Satellite Programming with Spot Replacement
IntroductionIf you’d like to record long form satellite programming and be able to replace spots, this document is for you. The following instructions will walk you through creating a cart which contains multiple RECORD macros with progressing file names, which will then be placed into a trigger set. The cart will be run any time your satellite programming provider sends you a trigger for the start of a segment. It is also required that your satellite programming provider provide a trigger for the end of a segment, or a local break. This end of segment trigger will be used to stop the current recording.
Using this technique, Simian will create multiple audio files which can be placed into your program log for later playback. You can also place your local spots, IDs, Liners, Jingles, etc. between each recorded file for spot replacement!
Building the CartThe first task is to build a cart which contains multiple RECORD macros (as shown in Figure 1). Each RECORD macro will have a slightly different file name specified and each line in the cart will be set with a Manual cue type. When this cart is run, it will start the first RECORD macro with the file name specified. The next time the cart is run, it will start the next RECORD macro, with the next file name, and so on. What will be created at the end of your long form recording is a set of consecutive files which you will play one after the other in your program log.
Figure 1: Multi-segment record cart. Each RECORD macro will start a new audio file with a consecutively different file name.
Building the Trigger SetThe next step is to add the cart created in the previous step, along with a RECORD STOP,1 macro to stop each record, into a trigger set. For this example, Trigger 3 is the trigger our satellite provider has given us to signal the start of segment/return from break, and Trigger 5 is the trigger they’ve proved for start of break/end of segment. The triggers you will use will depend on what your satellite provider provides.
Figure 2 shows the trigger set created with our example “ROB&TOMAS_RECORD.KRT” cart added to Trigger 3 so that the start of segment/end of break signal will start the corresponding RECORD macro. We’ve also added a RECORD STOP macro to Trigger 5 so that when our satellite provider gives the signal for start of break/end of segment, the recording will stop.
Figure 2: Trigger set with the cart containing RECORD macros is added to Trigger 3, the RECORD STOP macro has been added to Trigger 5.
Adding to the Scheduled EventsNow that we’ve built our Cart and our Trigger set, we need to add them to our Scheduled Events. We need to add the Trigger set to our Scheduled Events so that our segmented record will start at the correct time, stop at the correct time, and get ready to do the whole process the next day.
In addition to enabling our Trigger set to start our records, we also need to turn off the Trigger set at the end of our segmented record, and we need to re-set our cart so that the next day when we start the segmented record again, the cart will start at the top.
Again, in our example shown in Figure 3, a few minutes after 1:00pm the RESETCART macro is added to reset the next-to-play marker back to the top of the cart.
Figure 3: Scheduled Events set shown with the LOADTRIGGERS, LOADTRIGGERS NONE, and RESETCART macros entered appropriately
Playing back what’s recordedNow that all the segments have been recorded, we need to place the segments into the program log. Figure 4 shows an example log with our pre-recorded segments with spots in between each segment.
Figure 4: Example program log with the pre-recorded segments added and highlighted in green.y
Repeating the processEach day the segmented record process is run, it will overwrite the recorded segments that were recorded the previous day. This makes it very easy to add the segments to your program log since the segments will always have the same name regardless of what day they were recorded.
NOTE: Your trigger numbers will change depending on what triggers your satellite provider provides you with, so you will have to adapt your trigger set to fit your needs. The examples above assume that the 1st record deck in Simian is going to be used. It is possible to use the 2nd record deck instead, simply substitute a 2 for the deck number in the RECORD macros shown in the examples above.
BSI Technical Support:
Click Here to go to
the BSI Support Center
© 2006-2018 Broadcast Software International. All rights reserved.
909 International Way, Springfield, OR 97477 USA