Whenever you work with your 3Play system, you provide certain information about the production environment:

  • What broadcast standard is used in your locale? Is it PAL, common in Europe among other places, or perhaps NTSC, standard throughout North American regions?
  • Are your cameras or other live sources HD, SD or a mixture of both?
  • How are cameras connected (are you using component or SDI connections, or a combination of several types)?

As you continue, you may make other adjustments relevant to your current production requirements:

  • You might calibrate your cameras individually using the Proc Amp settings in the Input Configuration panels.
  • Perhaps you will also use Display Proc Amps to adjust output color characteristics.
  • What are your output device connection preferences? For example, will you send video from Channel A to a local reference monitor using component cabling, or perhaps another connection type? Will you connect a downstream switcher to Channel B using HD-SDI? What external audio connections and adjustments are required?
  • You might create PLAY LIST pages of clips and other content, along with pages full of recorded events in the CLIP LIST.

The list of adjustments, activities and assets involved in a specific production goes on, but the main point to grasp here is that the session entails of all of the above, collectively. Assuming you do not deliberately delete the session, all of your media and all of your settings are ready for immediate recall.

When you re-open an existing session, it’s just as if you were continuing an earlier event. Thus, if you return to the same venue another day under basically similar conditions, you can opt to simply re-open your prior session and be virtually ready to go. (Professional wisdom, of course, calls for testing everything before actually beginning the event.)

Naturally, you can store multiple sessions and load any session freely. This greatly simplifies business models that involve regular trips to several venues, a number of similar consecutive events, or different users with their own specific needs.

Section 5.1

For more information please download the entire document at
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Article is closed for comments.