Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Before proceeding you must stop the channel by deactivating the checkbox in front of it. Stopping the channel will also stop the Just Out engine and therefore the final output.

Redundancy, backup & misc.

Redundancy (optional):

  • Full (2N): The Primary and Redundant engine are running all the time, so for every Primary engine you need a Redundant engine.

  • Flexible (N+1): A single Redundant engine is shared between several Channels. If the Primary engine for any given Channel stops sending heartbeats to Just Connect then the floating Redundant engine will be started for the Channel. In this scenario only one Redundant engine is available and it will be allocated on a first-come-first-served basis, so if a second Primary engine fails, no Redundant engine would be available.

Backup Channel:

You can define a backup folder for the Channel file which can be used to restore the Channel on another machine. Do not select an internal disk as the backup volume but an external/network connected volume so in case the internal disk fails only the original Channel file is lost and not the backup. Most customers are using an USB flash drive as backup location, so it can be moved to another machine in case the main machine fails.

EAS Alerts:

Some broadcast stations must be able to add Audio- and Graphics-based emergency alerts to their broadcast signal using an emergency alert system. The DASDEC Digital Alert System can receive such a signal and pass it over to Just Connect which uses Just Out to add the Audio and Graphics information to the output signal.

  1. Activate the checkbox in front of EAS Alerts.

  2. Click the Configure button to open the EAS configuration window (a warning will be shown in case an Audio or FX Layer is missing).

  • Ports: The EAS device uses two network ports, one for Message and one for Data.

  • Data repository: The folder where the Graphics template is stored that will be used for the EAS Text Message.

  • FX Layer (text): The EAS option activates one additional FX Layer which needs to be configured like described in chapter 13.8 Adding & Removing Layers from a Channel. Once available, select the available FX Layer to be used for EAS Messages here.

  • Template filename: Enter the name of the Graphics template which is stored in the data repository defined previously.

  • Audio Layer: Choose one of the available audio Layers which should be used for the EAS audio file, provided by the EAS device.

  • Master volume during audio: Sets the volume of the master output while an emergency audio file is on air.

    • 0 means no audio.

    • 100 means full audio output.

    • The volume of the EAS Audio Alert is always 100% and cannot be changed.

  • Debugging

    • Backup alerts: Enabling this saves the incoming alerts for reference or for a later use.

    • Verbose logging: Enable this in case you are asked to do so by a ToolsOnAir employee. This saves additional informations which are useful in situations where the alerts are not played out correctly.

  • The FX Layer and the Audio Layer which have been selected to be used for emergency alerts are not visible in the user interface and therefore cannot be used for any other content.

  • With composition:builder v4 or higher it possible to generate EAS Alerts which match the look of your broadcast station. ToolsOnAir can provide a generic emergency alert Graphics template or customise the template. Please → contact us if you are interested.

DASDEC Settings:

The setup shown here is a guideline on how the configuration can be done. Depending on the DASDEC device and the firmware installed the user interface of the device and therefore also the configuration itself can be different.

Encoder Settings:

Setup Settings:

EBU-STL & SRT Sidecars:

just:out supports the insertion of subtitles coming from a EBU-STL & SRT subtitle sidecar file, into the VANC data of the outgoing SDI signal. Click on Configure to open the Sidecar Configuration window which allows you to define, how EBU-STL and SRT sidecar files will be inserted into the SDI signal.

Timing and Syncing

  • Timing Model: This option allows you to define how the rundown is handled after pressing the Jump to Next button while a Live Event with an overtime is on air.

    • Reschedule All: Moves all items for the skipped/extended time, incl. timed playlists.

    • Join In Progress: Keeps the remaining rundown unchanged by jumping into the rundown

  • Timecode Offset: This option allows you to define an offset which will be applied to the reference time. This allows you to change the time used internally in case the broadcast should happen earlier or later than the current time. The change will be reflected in the interfaces also.

  • Re-sync Engines: The time Just Out starts, it grabs the current time from the NTP of the local Mac. From that on it syncs to the clock of the output device. Because the clock of the Video device usually drifts over time from the reference time, they must be resynced on regular intervals. We allow a resync at the end of each Playlist. Here you can define if this should be possible at all and how many frames should be resynced as a maximum. We restrict this to avoid unforeseeable behaviors in case the reference time is lost or drifts for several minutes or even hours.

  • Restart on Drift: This option allows you to define a maximum offset of the Master ↔ Reference time. Once this offset has been reached, Just Out will be restarted automatically. Such a drift can come from an unstable Live Input signal, the natural drift of the Channels timecode compared to the real time but also every time the time is changed for one hour, because DST is (de)activated. We recommend to activate this function and to set it to 5 seconds.

  • Restart on Connects: This allows you to define the number of times Just Out reconnects to Just Connect within one minute, before Just Out is restarted automatically. Such a reconnect can happen in case the Video device used for playout is in trouble but also a network issue can cause this. We recommend to activate this function and to set it to 3 re-connects.

  • No labels