One of Zetta’s most unique features is the Background Recorder. Many users take its workflows literally, which is fine, as a way to record something in the background. However, did you know that the Background Recorder, or BGR, can be interpreted as its own station with clocks and logs? In this video, Jeff Zigler, RCS Senior Sales Engineer, joined us in breaking down many of the ways you can utilize Zetta’s Background Recorder and maximize its efficiency.
Starting with the setup and configuration. Users first must identify the recording sources via Configuration | Computer | Record Devices. After defining the recording inputs, assign a task that the Background Record, or BGR, can execute via Configuration | background Recorders. Users can have multiple Background Recorders or a single Background Recorder that can execute multiple tasks. If you’re looking to record to a single file, under Configuration | System | On Demand Recordings, users can record to a file outside of Zetta, an FTP site or select an internal asset and drag it into the defined area to have the BGR continue to overwrite that specific asset.
After defining and configuring the Background Recorder, users have access to the Recorder Clocks and Recorder Logs, located under Tools | Recorder Clocks or Recorder Logs. Think of the Recorder Clocks as a repeating 24/7 grid, broken down by the hour. Whereas the Recorder Logs represent Thursday 10/8/20. Let’s say that it’s a holiday and you don’t need the BGR to execute its workflow. We wouldn’t want to delete the workflow from the Recorder Clocks because that means the next time the day is scheduled, we lose that workflow. Instead, we should go to the Recorder Logs and remove the workflow due to the single holiday. Users can work within this window similar to Zetta’s Clocks or Logs. Right Click, insert a Control Event and then you can insert and manipulate Execute Commands, Macros and more. Jeff even used the example of a station that configured their Background Recorder to execute a task in which a GPO triggered the front doors to unlock at exactly 5:45am to let the morning show talent into the building and then at 6:00am, the BGR would lock the doors. Users can trigger individual recordings like curating a “Best of Morning Show,” or free up resources by executing tasks normally done by the File Server. Users submitted their own examples of playing back live recorded News or creating a macro, assigning it to a Hot Key and then firing it via Zetta2GO. Remember, macros are essentially combined functions that can be triggered as one. And with the Background Recorder’s Recorder Clocks and Recorder Logs, users have full control on scheduling or executing workflows. Treat the Recorder Clocks and Recorder Logs like you would a station’s Log module. There’s lots of ways you can maximize your workflows by combining the Recorder Clocks with everyday tasks.
Next, we continued with more user examples. Within the Metadata module, there is a section for Playback Method and the option Play Incoming File. If you have an ongoing recording and you want to essentially treat the Background Recorder as a DVR, you could begin a recording and then using the Play Incoming File Playback Method, start to the play the recorded element while it continues to record. There’s also ways to utilize Zetta’s TCP/UDP/GPIOs alongside the BGR to change routes, Hot Spare and more.
With fall upon us, we’re working on some unique topics to cover for upcoming RCS Lives, including Zetta Site Replication vs. Z-Casting, Zetta 5.20.1, GSelector 4.9.0 and its new unique Clock breakdowns. Make sure you follow us on www.Facebook.com/RCSSoundSoftware to RSVP for these free upcoming events and if you have questions you want answered, let us know and we’ll cover them every Thursday at 11am ET.
