Welcome < Features < Background Recording

Background Recording

The Background Recording feature is a Background Task Sequencer. A Background Recorder can be configured to record a Radio Show or Network Feed for playback on an On-Air station. These background recordings can be played back On-Air after they are recorded or with a delayed start while they are recording. Background Recorder stations can also be used for other background tasks needed by On-Air stations such as, changing the fill category, changing the sequencer mode, or running a macro, thus removing the clutter from the normal stations log, and preventing the accidental deletion of critical control events. The background recorder uses a background sequencer to execute the tasks scheduled in the Recorder Clocks and Recorder Logs. The Background Recorder runs as a Service process in the Startup Manager and does not require an On-Air module. After a Background Recorder is created, configured and the service is started, the Recorder Logs and Recorder Clocks are then available in the Tools menu.

In this Topic: show/hideshow/hide

Recording Shows with Background Recorder

The following step-by-step instructions will assist in the setup of the Background Recording feature to record a Radio Show or Network Feed. This does not cover the wiring of the audio and logic to the Computer(s). For a Network Feed, the show's program clock will need to be obtained from the Network provider.

Preparing for a Background Recording

In this section: show/hideshow/hide

Step 1: Computer Audio Inputs Configuration

1. Click Computers from the Configuration menu
2. Select the computer to configure
3. Select the Audio Inputs tab for the computer
4. Ensure the Active is checked to make the audio input active for the computer.
5. Edit the Name if desired.
6. Add a Description for the Audio Input for the computer. (optional)
7. Click the Add audio input button.
   
8. Select the audio input to use from the list in Select Audio Input window.
9. Click OK to except the selection.
10. Double-click the Input Name field to change the name. (optional)
11. Add any additional Audio Inputs as needed.
12. Click Save button to save the changes.

Step 2: Computer GPIO Devices Configuration

1. Click the GPIO /Routes tab in Configuration | Computers
2. Click the Add New GPIO Device  button.
3. Ensure the Enabled is checked.
4. Select the Device Type. The GPIO devices are listed in alphabetic order and will default to the first device in the list.
5. If required select the number of devices connected from the Quantity drop-down menu.
6. Enter the Name of the GPIO Device.

   Tip: The Name will be carried over to the GPI (Inputs), GPO(Outputs) and Routes when they are created, so it is helpful to give the device a meaningful Name before creating the Inputs, Outputs and Routes.

7. Enter a Description for the GPIO device. (optional)
8. Optionally, enter a Description for the GPIO device.
9. Optionally, enter a GPI Hold Time in seconds for Zetta to wait before receiving an additional Input from each GPI of the device. The GPI Hold Time is per GPI. This means if there are two GPI for the same device, GPI 1 and GPI 2, and a command is received twice from GPI 1 during the specified hold time, Zetta will ignore the second command. However, if a command is received from GPI 1 and GPI 2 within the specified hold time Zetta will respond to both.
10. Optionally, enter the number of seconds to ignore a GPI event following a GPO event using the Ignore GPI after GPO for X seconds field. If an input is received with X seconds of an output event, then the input will be ignored.
11. Optionally, enter the number of seconds to not generate a GPO event following a GPI event using the Do not send GPO after GPI for X seconds field. If an output is received with X seconds of an input event, then output event will not be sent.
12. See the Device setting and the device manufacturers' manual for other specific device setting configuration.
13. Select the GPIs (Inputs) tab to configure the Inputs; Inputs will display with the Name, GPI and Trigger Event On or Name and Event Text data. These fields can be edited and configured as needed. 
14. Select the GPOs (Outputs) tab to configure the Outputs; Outputs will display with the Name, Bit Position and Event Duration or Name and Event Text. These fields can be edited and configured as needed. See the GPO Variables section of the Zetta Variables topic for Event Text variables that can be used.
15. Select the Routes tab to configure the Routes (sources) for the device. Not all GPIO devices listed support Routes so this tab may not be available.
16. Click Save button to save the GPIO device settings.

See the GPIO/Routes and GPIO/Route Devices topics for additional details.

Step 3: Background Recorder Configuration

1. In the Configuration Menu, click Background Recorders.
2. Select an existing Background Recorder of click the Add new station  to add a new. 
3. Ensure the Active (Required) is checked.
4. Enter a Name to identify the Background Recorder.
5. Enter a Description to describe the Background Recorder. (optional)
6. Select the Sequencer Computer from the drop-down to be the Background Recorder Sequencer that processes the Recorder Log.
7. Select the number of Future Days to Schedule of Logs.
8. Select the number of Past Days to Keep of Logs.
9. Click the Save  button to save the settings.

Step 4: Create Assets for Recording

A show can be recorded in segments, recording each segment as a separate asset. Optionally, the show can be recorded as one asset, capturing GPO, GPI, and Virtual Events. Typically, these assets will be created as Links so they can be scheduled using GSelector or Loaded using a Flat File Load.

At times there may be the need to record the audio to a File. This can be done by selecting File in the Record To field on the Record Control Event and entering a File Path using the variables in Zetta.

For these record examples we will set up Link assets.

1. In the Library Module select the Link tab
2. Click the Add New Media button
3. Give each Asset a Title.
4. If the asset is to be played while recording, select the Playback Method of Play Incoming File from the Extra tab. If not skip to step 6.
5. Set the Target Duration.
6. Click the Station Specific tab and make the Asset active for the playback stations.
7. Select a Category for the asset.
8. Save the Asset.
9. Repeat if recording the show in segments. An asset will be needed for each segment of the show.

See the Links topic for more details on the Links Metadata card.

Note: When a Play Incoming File asset is rerecorded, all cue points and virtual events, which are not locked, are cleared from the asset when recording starts.

Recording a Show in Segments for Playback

In this section: show/hideshow/hide

Step 1: Configure GPIO Event Command Mappings to Start and Stop a Background Recording

Configure the individual opto closures for Start recording and Stop recording. This Step can be skipped if using Timed recordings.

1. From the Configuration Menu, click System.
2. Click the Command Mappings tab
3. Click Add GPIO Event Mapping option from the Add new mapping drop-down button.
4. Enter a Name for the GPIO Mapping (default is New Mapping GPIO).
5. Input a Description for the GPIO Mapping (optional)
6. Set the GPIO Mapping Type to Standard (Default)
7. Using the Processed By drop-down select the computer that has the device installed and configured above.
8. In the Input Trigger Mapping (GPIs), click the Add new mapping button
9. Uncheck the Capture option.
10. Give the GPI a Name
11. Set the Context to Global.
12. Select the GPI Trigger name added to the GPIs (Inputs) created above when the GPIO device was added.
13. Add a Rejoin event using the Execute Command, Background.Record.Start
14. Select the Background Station created above.
15. Select the Audio Input created above.
16. Click the Add New Mapping button
17. Uncheck the Capture option.
18. Give the GPI a Name
19. Set the Context to Global.
20. Select the GPI Trigger name added to the GPIs (Inputs) created above when the GPIO device was added.
21. Add a Local Break event with the Execute Command, Background.Record.Stop
22. Select the Background Station created above.
23. Select the Audio Input created above to stop recording.
    
24. For more information on Execute Commands that can be used for Background Recorders in Zetta, see the Zetta Commands topic.

Step 2.1: Add a GPIO Record Control Event to a Recorder Clock

1. Open the Recorder Clocks Module from the Tools menu
2. Select the Background Recorder created above from the Station Select drop-down.
3. Select the Day of the week the Show is to be recorded.
4. If using the show's program clock, determine when the first segment will send a start opto. Select Hard Time.
5. Enter a time that is a minute and a half ahead of when the opto is to fire, such as 58:30 (provided there is no show in the previous hour that would end after that point).
6. Select the Audio Input created above.
7. Select the route to enable when the recording starts from the Enable Route on recording start drop-down.
8. Select the action to take when the recording stops from the Route state on recording stop drop-down.
9. Enter a Recording Length greater than the longest time that the first segment is expected to run. If the Record Length specified here is different than the Target Duration specified for the asset created, once the recording starts the Target Duration will be adjusted to match the Record Length specified.
10. Select the Start Type of GPIO since a start opto is expected from the source.
11. Select the Audio format to use. See the Audio Format section for additional information.
12. Select Asset as the Record To option.
13. Drag and Drop the Asset created above to the Asset field where it states Drop asset to assign.
14. Optionally, uncheck the Perform Marks Analysis option. This will be specific to this recording. This would typically be cleared for recordings where a silent spot/spot block is scheduled at the beginning or end of a show that is being recorded.
    
15. Drag and drop the Record Control Event into the clock position.
16. Repeat for each Segment of the show. Each successive segment should be a hard-timed GPIO recording. The start time should be at the midpoint of the previous spot block. For example, if segment 1 ends at :15:00 and is followed by a 4-minute spot block, segment 2 should be hard-timed at :17:00. This allows segment 1 to end up to 2 minutes late or segment 2 to start up to 2 minutes early without causing problems. This buffer time is dependent on the length of the local break. The length of these recordings should be greater than the longest time that each segment is expected to run. Some shows may require a 40-minute length, for the second segment out of three, but most shows have segments less than 30 minutes long.
17. Generate a Recorder Log if event was added to the Recorder Clock.

Step 2.2: Add a Timed Record Control Event to a Recorder Clock

1. Open the Recorder Clocks Module from the Tools menu
2. Select the Background Recorder created above from the Station Select drop-down.
3. Select the Day of the week the Show is to be recorded.
4. Using the show's program clock, determine when the first segment will send a start opto. Select Hard Time.
5. Enter the time the show is to start, such as 00:00.
6. Select the Audio Input created above.
7. Select the route to enable when the recording starts from the Enable Route on recording start drop-down.
8. Select the action to take when the recording stops from the Route state on recording stop drop-down.
9. Enter a Recording Length greater than the longest time that the first segment is expected to run. If the Record Length specified here is different than the Target Duration specified for the asset created, once the recording starts the Target Duration will be adjusted to match the Record Length specified.
10. Select the Start Type of Time.
11. Select the Audio format to use. See the Audio Format section for additional information.
12. Select Asset as the Record To option.
13. Drag and Drop the Asset created above to the Asset field where it states Drop asset to assign.
14. Optionally, uncheck the Perform Marks Analysis option. This will be specific to this recording. This would typically be cleared for recordings where a silent spot/spot block is scheduled at the end of a show that is being recorded.
    
15. Drag and drop the Record Control Event into the clock position.
16. Repeat for each Segment of the show. Each successive segment should be a hard-timed GPIO recording. The start time should be at the midpoint of the previous spot block. For example, if segment 1 ends at :15:00 and is followed by a 4-minute spot block, segment 2 should be hard-timed at :17:00. This allows segment 1 to end up to 2 minutes late or segment 2 to start up to 2 minutes early without causing problems. This buffer time is dependent on the length of the local break. The length of these recordings should be greater than the longest time that each segment is expected to run. Some shows may require a 40-minute length, for the second segment out of three, but most shows have segments less than 30 minutes long.
17. Generate a Recorder Log if event was added to the Recorder Clock.

Step 3: Playback of Show Recorded in Segments

Playing back these recordings is simple. If recording the show in segments, schedule the segments in the proper order with spot blocks in between. Add any missing elements like legal ID's and imaging, and load traffic. Set the Station to run in Auto mode for the length of the show. These shows can also be scheduled as Links when using GSelector Integration. If the Play Incoming File Playback Method was selected for the asset created, the asset can be played from any configured computer in a station Log, Hot Keys, Stacks or Metadata Card while it is recording.

Record Show, Capture Spot Blocks as Cue Points for Playback on another Station

In this section: show/hideshow/hide

Step 1: Configure Output Event Mapping so SpotBlockPlay is captured by the Recorder

1. From the Configuration Menu, click System.
2. Click the Command Mappings tab
3. Select the desired GPIO Command Mapping or create a new GPIO Mapping.
4. Select the Output Event Mappings tab
5. Add an Execute Command.
6. Give the command a Name.
7. Select the Output Event field for the command.
8. In the Properties for the Output Event select the Task Type Sequencer.SpotBlockPlay
9. Select the Station (01 WRCS-FM) that the Cue Point will be captured.
   
10. Save  the Command Mapping

Step 2: Add a Timed Record Control Event to Recorder Log/Clock to Capture SpotBlockPlay Output Event

1. Open the Recorder Clocks or Recorder Logs from the Tools menu
2. Select the Background Recorder created above from the Station Select drop-down.
3. Select the Day of the week or Date the Show is to be recorded.
4. Right-click the Hour of the Clock/Log.
5. From the resulting menu select Insert, then Control Event.
6. Select Record from the Insert Context Event consideration window.
   
7. In the New Record Properties window, enable the Hard-timed recording checkbox.
8. Enter the time the show/recording is to start, such as 59:59.
9. Select the Audio Input created above.
10. Enter a Recording Length. If the Record Length specified here is different than the Target Duration (Play Incoming File) specified for the asset created, once the recording starts the Target Duration will be adjusted to match the Record Length specified.
11. Select the Start Type of Time.
12. Select the Audio format to use. See the Audio Format section for additional information.
13. Select Asset as the Record To option.
14. Drag and Drop the Asset created above to the Asset field where it states Drop asset to assign.
15. Optionally, uncheck the Perform Marks Analysis option. This will be specific to this recording. This would typically be cleared for recordings where a silent spot/spot block is scheduled at the beginning or end of a show that is being recorded.
16. Check the Capture Station Output Events option. This will Capture the start of a Spot Block and create a Simulate Sequencer_SpotBlockPlay Cue Point with a Task Type of GPIO.SimulateOutputEvent with an Output Event details task type of Sequencer.SpotBlockPlay
17. Select the Capture Station (01 WRCS-FM).
    
18. Drag and drop the Record Control Event into the clock position.
19. Generate a Recorder Log if event was added to the Recorder Clock.
20. After the recording completes, confirm the spot block start events were captured by the recorder.
    
21. Note the Captured Cue points in the Audio graph of the Metadata Card. This is where the Spot Blocks played on the station that was recorded/captured. The Spot Blocks that played on the station had a Split Behavior of Master Silent, hence the regions of silence. Click the Edit  button to view the details of the captured cue point.
    

Step 3: Configure Output Event Mapping so SpotBlockPlay cue points trigger MoveUpAndPlayNextSpotBlock on Playback

1. From the Configuration Menu, click System.
2. Click the Command Mappings tab
3. Select the desired GPIO Command Mapping or create a new GPIO Mapping.
4. Select the Output Event Mappings tab
5. Add an Execute Command.
6. Give the command a Name.
7. Select the Output Event field for the command.
8. In the Properties for the Output Event select the Task Type Sequencer.SpotBlockPlay
9. Select the Station (02 WRCS-AM) that will play the Recording with Cue Points.
   
10. Select the Execute Command field.
11. In the Properties for the Execute Command select the Task Type Sequencer.MoveUpAndPlayNextSpotBlock 
12. Select the Station (02 WRCS-AM) that will play the Recording with cue points
    
13. Save  the Command Mapping.

Step 4: Schedule the Record Event with Captured Output Events and Corresponding Spot Blocks

The Recorded Event can be scheduled using GSelector or loaded using a Flat File Load. Any ETMs placed before the Spot Block for traffic load should be Reset ETMs. For this example, we will simply add the required events into the station Log. If the Play Incoming File Playback Method was selected for the asset created, the asset can be played from any configured computer in a station Log, Hot Keys, Stacks or Metadata Card while it is recording.

1. Open the Logs Module
2. Select the playback Station (02 WRCS-AM).
3. Select the Hour that the recorded asset will play.
4. Open the Library Module and select the Links tab
5. Locate the Asset created.
6. Drag and drop the asset into the desired hour of the log.
7. Right-click the hour. From the resulting menu select Insert, then Control Event.
8. Drag and Drop a Spot Block for each cue point, into the Log below the Recorded asset.
9. Optionally, drag and drop an ETM before each Spot Block. Set the ETM to Reset for the approximate time of the Spot Block.
10. Load Traffic or Drag and Drop the Spots into the Spot Blocks from the Library Module.
    
11. When the recorded event plays, the recorded audio will pause when the SpotBlockPlay is played, and the Next Spot Block will be fired.
    

    Important Note!

    At least one additional stream/output will be needed if the Station is to play back an Asset which will pause and execute future Spot Blocks during the paused state.

12. The recorded audio is also advanced to the point where the end of the original Spot Block was when recorded. The recorded audio will resume playing when the fired Spot Block is completed. If there is an event beyond the audio, it will transition to this event as it would any other event (based on the mode and chain type).

Record an External Source and Capture GPI Triggers for Playback with Spot Blocks

In this section: show/hideshow/hide

Step 1: Configure Network Operation for the Capture Station

1. In the Configuration Menu, click Stations.

2. Select the Station (01 WRCS-FM) to edit.
3. Click the Network Operation tab.
4. In the Available GPIs, select the available Spot Block Start and Spot Block End GPIs (Inputs) the station will use that were configured for the computer.
   
5. Click Save to save the settings. See the Network Operation topic for more details on the settings in this window.

Step 2: Configure Command Mappings to Capture GPI Triggers

1. From the Configuration Menu, click System.
2. Click the Command Mappings tab
3. Click Add GPIO Event Mapping option from the Add new mapping drop-down button.
4. Enter a Name for the GPIO Mapping (default is New Mapping GPIO).
5. Input a Description for the GPIO Mapping (optional)
6. Set the GPIO Mapping Type to Standard (Default)
7. Using the Processed By drop-down select the computer.
8. Click the Add New Mapping button.
9. In the Input Trigger Mappings tab, deselect the Active checkbox as we will be just capturing the GPI at this time.
10. Ensure Capture is checked.
11. Add a Name for the GPI
12. Set the Context to Global
13. Select the GPI trigger created when Configuring Computer GPIO Devices and added to the Network Operation tab for the Station being captured.
    
14. Click Save to save the settings.

Step 3: Add a Timed Record Control Event to a Recorder Log/Clock to Capture GPI Triggers

1. Open the Recorder Clocks or Recorder Logs from the Tools menu
2. Select the Background Recorder created above from the Station Select drop-down.
3. Select the Day of the week or Date the Show is to be recorded.
4. Right-click the Hour of the Clock/Log.
5. From the resulting menu select Insert, then Control Event.
6. Select Record from the Insert Context Event consideration window.
   
7. In the New Record Properties window, enable the Hard-timed recording checkbox.
8. Enter the time the show/recording is to start, such as 59:59.
9. Select the Audio Input created above.
10. Enter a Recording Length. If the Record Length specified here is different than the Target Duration (Play Incoming File) specified for the asset created, once the recording starts the Target Duration will be adjusted to match the Record Length specified.
11. Select the Start Type of Time.
12. Select the Audio format to use. See the Audio Format section for additional information.
13. Select Asset as the Record To option.
14. Drag and Drop the Asset created above to the Asset field where it states Drop asset to assign.
15. Optionally, uncheck the Perform Marks Analysis option. This will be specific to this recording. This would typically be cleared for recordings where a silent spot/spot block is scheduled at the beginning or end of a show that is being recorded.
16. Check the Capture Station GPI Triggers option.
17. Select the Capture Station (01 WRCS-FM).
    
18. Drag and drop the Record Control Event into the clock position.
19. Generate a Recorder Log if event was added to the Recorder Clock.
20. After the recording completes, confirm the GPI Triggers were captured by the recorder.
    
21. Note the captured Cue Points in the Audio graph of the Metadata Card. This is where the GPI Triggers were received on the station that was recorded/captured. The Spot Blocks that played on the station had a Split Behavior of Master Silent, hence the regions of silence. Click the Edit  button to view the details of the captured cue point.
    

Step 4: Configure Command Mappings so GPI triggers execute SyncToAndPlayNextSpotBlock.RemoveQueued and StopSpotBlock

1. From the Configuration Menu, click System.
2. Click the Command Mappings tab
3. Select the desired GPIO Command Mapping or create a new GPIO Mapping.
4. Select the Input Triggers Mappings tab
5. Click Add new Mapping .
6. Ensure Active is checked for this input.
7. Clear the Capture checkbox as we will not be capturing this input.
8. Give the command a Name.
9. Set the Context to Global if not set.
10. Select the GPI Trigger to execute Sequencer.SyncToAndPlayNextSpotBlock.RemoveQueued command.
11. Select the Execute Command field.
12. In the Properties window for the Execute Command select the Task Type, Sequencer.SyncToAndPlayNextSpotBlock.RemoveQueued
13. Select the Station (02 WRCS-AM) that is playing the Recording with the Cue Points.
14. Select Played as the Prior Event Status
    
15. Click Add new Mapping .
16. Ensure Active is checked for this input.
17. Clear the Capture checkbox as we will not be capturing this input.
18. Give the command a Name.
19. Set the Context to Global if not set.
20. Select the GPI Trigger to execute Sequencer.StopSpotBlock command.
21. Select the Execute Command field.
22. In the Properties window for the Execute Command select the Task Type, Sequencer.StopSpotBlock
23. Select the Station (02 WRCS-AM) that will play the Recording with the Cue Points.
    
24. Save  the Command Mapping.

Step 5: Schedule Record Event with Captured GPI Triggers and Corresponding Spot Blocks

The Recorded Event can be scheduled using GSelector or loaded using a Flat File Load. Any ETMs placed before the Spot Block for traffic load should be Reset ETMs. For this example, we will simply add the required events into the station Log. With the GPI Trigger method of capturing the start and end of a spot block the user is not limited to the Spot Block Length of the original show, meaning the user can add more or less spots to the spot block as needed. If there is not a captured GPI Trigger to stop the Spot Block, Zetta will use the length of the Spot Block from the recording as the duration of the spot block when the recording is played. If the Play Incoming File Playback Method was selected for the asset created, the asset can be played from any configured computer in a station Log, Hot Keys, Stacks or Metadata Card while it is recording.

1. Open the Logs Module
2. Select the playback Station (02 WRCS-AM).
3. Select the Hour that the recorded asset will play.
4. Open the Library Module and select the Links tab
5. Locate the Asset created.
6. Drag and drop the asset into the desired hour of the log.
7. Right-click the hour. From the resulting menu select Insert, then Control Event.
8. Drag and Drop a Spot Block for each cue point, into the Log below the Recorded asset.
9. Optionally, drag and drop an ETM before each Spot Block. Set the ETM to Reset for the approximate time of the Spot Block.
10. Load Traffic or drag and drop the Spots into the Spot Blocks from the Library Module.
    
11. When the recorded event plays, the recorded audio will pause when the Sequencer.SyncToAndPlayNextSpotBlock.RemoveQueued  GPI Trigger is played, and the Next Spot Block will be fired.
    

    Important Note!

    At least one additional stream/output will be needed if the Station is to play back an Asset which will pause and execute future Spot Blocks during the paused state.

12. The recorded audio is advanced to the next cue point where the Sequencer.StopSpotBlock GPI Trigger is located. The recorded audio will resume playing when the Spot Block is completed. If there is an event beyond the recorded audio, it will transition to this event as it would any other event (based on the mode and chain type).

Record a Radio Show Capturing Virtual Events for Playback

In this section: show/hideshow/hide

Step 1: Configure Log Event Settings for the Recorded Station

1. Click the Log Events Settings tab in Configuration | Stations
2. Select the Event Type to configure.
3. In the bottom setting pane for the event Type check the 'Capture asset type as virtual events in background recording' option.
   
4. Select the next Event Type to configure.
5. In the bottom setting pane for the event Type check the 'Capture asset type as virtual events in background recording' option.
6. Continue until all Event Types are configured.
7. For any event types to exclude clear the check for the 'Capture asset type as virtual events in background recording' option.
8. Click Save button to save the changes.

Step 2: Add a Timed Record Control Event to a Recorder Log/Clock to Capture Virtual Events

1. Open the Recorder Clocks or Recorder Logs from the Tools menu
2. Select the Background Recorder created above from the Station Select drop-down.
3. Select the Day of the week or Date the Show is to be recorded.
4. Right-click the Hour of the Clock/Log.
5. From the resulting menu select Insert, then Control Event.
6. Select Record from the Insert Context Event consideration window.
   
7. In the New Record Properties window, enable the Hard-timed recording checkbox.
8. Enter the time the show/recording is to start, such as 59:59.
9. Select the Audio Input created above.
10. Enter a Recording Length. If the Record Length specified here is different than the Target Duration (Play Incoming File) specified for the asset created, once the recording starts the Target Duration will be adjusted to match the Record Length specified.
11. Select the Start Type of Time.
12. Select the Audio format to use. See the Audio Format section for additional information.
13. Select Asset as the Record To option.
14. Drag and Drop the Asset created above to the Asset field where it states Drop asset to assign.
15. Optionally, uncheck the Perform Marks Analysis option. This will be specific to this recording. This would typically be cleared for recordings where a silent spot/spot block is scheduled at the beginning or end of a show that is being recorded.
16. Check the Capture Station Virtual Events option.
17. Select the Capture Station (01 WRCS-FM).
    
18. Drag and drop the Record Control Event into the clock position.
19. Generate a Recorder Log if event was added to the Recorder Clock.
20. After the recording completes, confirm the Virtual Events were captured by the recorder.
    
21. Note the captured Virtual Event marks in the Audio graph of the Metadata Card. This is where the Virtual Events were captured on the station that was recorded/captured. Click the Edit  button to view the details of the captured Virtual Event.
    

Step 3: Playback Recording with Captured Virtual Events

The Recorded Event can be scheduled using GSelector or loaded using a Flat File Load. If the Play Incoming File Playback Method was selected for the asset created, the asset can be played from any configured computer in a station Log, Hot Keys, Stacks or Metadata Card while it is recording.

1. Go to the Logs Settings tab in Station Configuration for the Station (02-WRCS-AM) that will be playing the Recording.
2. In the Logs Settings ensure Include Virtual Events in the Queue is checked.
   
3. Save  the any changes to the Station Configuration
4. Open the Logs Module
5. Select the playback Station (02 WRCS-AM).
6. Select the Hour that the recorded asset will play.
7. Open the Library Module and select the Links tab
8. Locate the Asset created.
9. Drag and drop the asset into the desired hour of the log.
10. Open the on-air window for the station (02 WRCS-AM) and make sure the virtual events option is turned on . You should see the virtual events following the recorded event with the virtual events markers. 
    
11. As each virtual event is played, it will be removed from the display.
    

Background On Demand Recording using Cue Points

On Demand recordings can be set up to record to File, Asset or FTP site to automatically record a News Bulletin to send to a Website as a Podcast. For this option, a Cue Point can be inserted at the start of the opening News Jingle to initiate the recording and then another Cue Point at the end of the closing News Jingle to complete the recording.

In this section: show/hideshow/hide

Step 1: Setup On Demand Recordings to a File

On Demand recordings can be set up to record to File, Asset or FTP site. In this example we will record to a File.

1. From the Configuration Menu, click System.
2. Click the On Demand Recording tab
3. Click the Add Recording button
4. Enter a unique Name for the recording
5. Select an Audio Input from the drop-down. The audio input selected should be an input that will be available at the required time. If the input is being shared with Voice Tracking or Quick Record, it is evident that no VT or QR can occur during an On Demand Background recording.
6. Select the route to enable when the recording starts from the Enable Route on recording start drop-down.
7. Select the action to take when the recording stops from the Route state on recording stop drop-down.
8. Insert a maximum Recording Length for the recording. Record Length must reflect the maximum expected length of the target event.
9. Choose an Audio Format from the drop-down of configured Audio Formats.
10. Select File from the Record To field.
11. Enter a Path to the location for Zetta to save the file when finished recording. The File path will need to be shared if it is to be accessible to all machines which will be accessing this directory. File Path must include the target file name and extension. The extension should match the Format defined.
    
12. Click Save to save the settings.

Step 2: Create a Background Insert/Auto Start Cue Point in the Intro

Cue Points can be used to add embedded cue markers at various points in an audio file to perform commands. Use the Marking Tool to insert a Cue Point into the Intro audio for the News.

1. Open the Library from the Modules Menu
2. Double-click the desired asset to edit
3. Select the Station or Cut in the left tab.
4. Click on the audio graph to set the Play marker at the point where the Recording should start.
5. Select the Cue Points tab
6. Select the Add new Cue Point button.
7. Select <Custom> from the drop-down.
8. Name the Cue Point
9. In the Execute Command column select the Task Type of Background.OnDemandRecording.Insert
10. In the Select the Background Recorder from the drop-down.
11. Select the On Demand Recording created.
12. Select Auto Start. The command invokes the background recorder to INSERT a blank audio file in the File Path specified (in the On Demand Configuration) and START (Auto Start enabled) recording the event.
    
13. Click OK to close the Edit Custom Cue Point window.
14. When finished editing the Metadata card click the Save button.

Step 3: Create a Background Stop Cue Point in the Outro

Use the Marking Tool to insert a Cue Point into the Outro audio for the News.

1. Open the Library from the Modules Menu
2. Double-click the desired asset to edit
3. Select the Station or Cut in the left tab.
4. Click on the waveform graph to set the Play marker at the point where the Recording should stop.
5. Select the Cue Points tab
6. Select the Add new Cue Point button.
7. Select Custom from the drop-down.
8. Name the Cue Point
9. In the Execute Command column select the Task Type of Background.OnDemandRecording.Stop
10. Select the Background Recorder from the drop-down.
11. Select the On Demand Recording created. The command stops the background recorder and saves the audio file to the specified File Path. The STOP cue point must occur before the Segue marker.
    
12. Click OK to close the Edit Custom Cue Point window.
13. When finished editing the Metadata card click the Save button.

Step 4: Setup Station log to play the Intro, Live Event and Outro

1. Open Logs from the Modules Menu
2. Open the Library from the Modules menu
3. Locate the Assets to add to the Log.
4. Drag and drop the Intro, News Live Event, and the Outro to the Station Log.
   

The Background record events will appear in the log as above, with a RED marker warning the user of the upcoming Cue Point to insert/auto start and stop the background recording.

Monitoring Background Record Events

Using the Background Recorder log from the Tools | Recorder Logs option the scheduled and on demand recordings can be monitored.

Editing the Marks of a Play Incoming Asset Recording

If the asset is configured up with the Play Incoming File Playback Method, then the audio of the asset can be viewed, played and marks added/changed while it is recording.

1. In the Library Module locate the asset being recorded.
2. Double-click the asset that is recording to open the Metadata card for the asset.
   
3. As the Audio is recording the audio can be played using the play button in the Marks Editor. Use the refresh button to refresh the waveform as the audio is being recorded. Any captured Cue Points will be shown as they occur in the Audio graph.
4. Use the Marks tab or right-click the audio graph to insert marks in the audio. If Perform Marks Analysis is checked and marks are added during the recording of the audio, Zetta will not insert the Trim In, Trim Out and Segue markers when the recording is finished. However, if the audio is untouched (no marks are added during the recording), Zetta will analyze and add the Trim In, Trim Out and Segue markers when the recording is finished.
5. Save the metadata card. This will refresh the Metadata card.
   
6. When the audio is finished recording the Target Duration will change to show the actual Runtime of the audio file. The Spot Blocks that played on the recorded station had a Split Behavior of Master Silent, hence the region of silence after the captured Output Event.
   

Troubleshooting GPIO Issues

After the recordings have been processed, review the log to ensure they were recorded properly. If there are problems, recent opto activity can be viewed in the Tools | GPIO History. Contact RCS Support for additional assistance.

Welcome < Features < Background Recording