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 3 Current »

A Playlist includes all references to the files that are part of it, so it can be useful to save them for later use. This can be done using the “TOA XML” format or as a “CSV/TXT” file.

The rundown (all Playlists of all days) is automatically saved, every time something has been added/removed or changed. This means that there is no need (and also no such function) to save the rundown itself.

Saving A Playlist

Drag & Drop

  1. Select the “Playlist” tab in the Library.

  2. Drag and Drop the Playlist from the Calendar View or the Workbench into the Playlists tab of the Library.

  3. Enter a name for the Playlist.

  4. Save it to the Playlists repository folder (defined by your system administrator) or to another location.

Using the 'Save As' Command

  1. Select the Playlist.

  2. Go to the “File” menu.

  3. Select “Save Playlist As…”

  4. Enter a name for the Playlist.

  5. Save it to the Playlists repository folder (defined by your system administrator) or to another location.

Using the Inspector

  1. Select the Playlist.

  2. Go to the Inspector.

  3. Click on the “Save Playlist As…” button In the lower-right corner.

  4. Enter a name for the Playlist.

  5. Save it to the Playlists repository folder (defined by your system administrator) or to another location.

Saved Playlists are usually located at the path specified as the Playlists Repository (the default path is: ~/Documents/Playlists). It is possible to transfer saved Playlists to other machines and reuse them there. Doing so, ensure that the Just Out engine has access to all the files which are used in those specific Playlists.

Reusing A Playlist

Depending on the “Automatically Refresh dropped Playlists” setting in the Just Control Settings, importing a Playlist can take some time. We recommend deactivating the setting and doing the refresh manually using the Refresh Playlist function instead.

You can add a previously saved Playlist to the rundown. Drag the Playlist from the Library

  • … into an existing Playlist in the Calendar View: This will add the content at the end of that Playlist.

  • …into an existing Playlist in the Workbench or the Timeline: This allows you to precisely define where the content of the Playlist is being dropped.

  • …into an existing Playlist in the Workbench or the Timeline while holding the “Command” key: This splits the Playlist at the desired dropping position and generates a new Playlist in between the two parts.

  • …into an empty area of the Calendar View or the Timeline: This will add the content at the position the Playlist is dropped.

Dropping Playlists into the Calendar View using Modifier Keys

  • Hold down the “Control” key to ignore the position (time) the Playlist is dropped and make the Playlist automatically chained.

  • Hold down the “Option” key to make the Playlist remember the time it was scheduled originally.

  • Hold down the “Command” key to make the Playlist remember the date and time it was scheduled originally. This is especially helpful in case the Playlist has been made offline using a copy of just:play on another system.

Trying to add a Playlist using one of the modifier keys to a time when there is already a Playlist scheduled will reject the dropped Playlist.

Invalid Merging

  • It is not possible to drop a Playlist between two elements in the Video track if there is a Graphics element playing at that position. 

  • It is not possible to add Playlists to the rundown whose drop point is in the past. This would change the current Playout and will therefore be rejected. A warning will be shown instead.

  • In addition to save single Playlists, it is also possible to save and reuse all playlists of a certain day. Please refer to Chapter 8.2 Import/Export of a Full Day Rundown (v.5.x) for more information.

  • You can also save Playlists in plain text (CSV) format. This is useful in case a third-party system needs the rundown information before the Playout happens and therefore the usage of the “As-Run Log” file is not possible.

  • No labels