1 Table of Content. IP Director version 5.6. Features description

Transcription

1 Date : 15-mai-09 Page: 1 File: 1 Table of Content 1 Table of Content Ingest...Erreur! Signet non défini. 2.1 Channel Explorer Introduction Features Support of ganged channels wysiwyg philosophy (What You See Is What You Get) User rights Limitations Ingest scheduler Introduction Features Limitations Recorder Panel Introduction Features Limitations Fill and Key ingest Introduction Workflows Fill and Key playlist management Playout Control Panel Introduction Modification of the Control Panel GUI Partial restore/partial backup Associate a control panel to a playlist panel Limitations Production playlist Introduction General playlist limitations of version Playlist panel GUI New functions... 22

2 Date : 15-mai-09 Page: 2 File: 3.3 IP Edit Introduction General Ip Edit Limitations Technical information Ip Edit panel GUI Player Browser Timeline Super Quick Start Guide Remote P Layout Features How To Content management Near line management Near line management LoRes management Features Limitations Metadata Management Introduction Features Limitations Bin management Introduction Features for Version Advanced Filters Introduction Quick search toolbar Filter tool bar Searches based on keywords Saved filters Miscelleanous IP Logger / Keyword grids Features Colours on keyword grids... 83

3 Date : 15-mai-09 Page: 3 File: Limitations Proxy management Introduction Features T/C and date management Introduction Features Lic ensing Options in XSecure Remarks Settings Introduction Overall philosophy Settings category...91 Define output GPI advance Technical improvements Remote installer Features Limitations Serial Link Redundancy

4 Date : 15-mai-09 Page: 4 File: 2 Introduction This document explains the main new features of compared to version Ingest 3.1 Channel Explorer Introduction The channel explorer is the chosen tool for browsing the channels of the XTs controlled by an IP Director workgroup. From the Channel explorer, the operator can organise his channels in ganged groups, open a control panel or a recorder panel. In the IP Director V5, the operator is also able to control ingest in a simple startstop VTR like workflow. Control of the XStream application is also managed through the channel explorer. An ingest can be started from the tree view by right clicking on a recorder but in order to easily control and monitor multiple ingests, new flat recorder views have been introduced. These flat recorder views are also ideal for an administrator to view his Hi-Lo recorder associations.

5 Date : 15-mai-09 Page: 5 File: Features Tree View The tree view has the following enhancements: Logical network view: the XTs can be organised in logical networks. If logical networks have been defined in the Remote installer, each XT appears under a Network node. Hi-Lo associations are displayed. If a LoRes recorder is associated to a HiRes recorder, it appears under that HiRes recorder new stream node: if an xml unit with streaming capabilities is defined on the network, a stream node is shown under each recorder. possibility to start/stop an ingest by right clicking on a recorder or a stream and choose start/stop ingest New flat recorder views This view is aimed at quick ingest workflows and are based on a start-stop mechanism.

6 Date : 15-mai-09 Page: 6 File: Ex: Hi-Lo view with recording in progress The flat rec. view offers a flat per channel view of the recording channels. Each line represents an ingest channel and the operator can choose which components of a channel are displayed. There can be up to four components for an ingest channel: - a Hi-Res recorder - a Hi-Res stream - a Lo-Res recorder - a Lo-Res stream The HiRes recorder is the "master" of the ingest channel. There is an ingest channel for each HiRes recorder and the name of the channel is the name given to the recorder in the Shift+F2 configuration screen of the multicam. Next to each line are a Start Recording and a Stop Recording button. Starting an ingest on a channel is as simple as pushing the start button next to that channel. To start multiple ingests at once, just select multiple lines and press start on one of the start buttons. Starting an ingest on a recorder starts a growing clip on that recorder. If a recorder is not started when the user presses the start button, it is automatically started. When an ingest is started, feedback is given to the operator in two ways: - the start button becomes Red dot on a red background to show a recording in progress

7 Date : 15-mai-09 Page: 7 File: - the name of the asset being recorded is put between brackets behind each component Stream control The IP Director is capable of remotely controlling the Streaming applications (XSTream, XT Access) to stream content from record trains onto an IT storage or directly to an NLE (Avid TM, FCP, CE). When streaming to an IT storage that is part of the managed IP Director near line directories, the IP Director users will be able to browse this stream through the software player Support of ganged channels Linked ingests can be started by ganging two or more channels and then pressing start on one of the channels (or right click start ingest in tree view). An ingest is started on each of the channels of the ganged group. Stopping one of the ingests will also automatically stop all the others. The T/C of ganged ingests will be identical and frame accurate wysiwyg philosophy (What You See Is What You Get) The flat rec. views work on a What You See Is What You Get philosophy. This means that ingests are started on the components that are displayed. An ingest can for example be started only on the XT recorder, or only on a stream, or on both. All the components of an ingest are put in the same asset since they represent the same A/V material. In order to keep the coherence of the asset (same T/C In and T/C Out for all asset items), when an ingest is stopped, all the components of the ingest are stopped.

8 Date : 15-mai-09 Page: 8 File: One exception to this is that when Hi and Lo Res recorders are associated, an ingest is always started/stopped on both at the same time. Ex: stream only view User rights Right to start/stop an ingest on a channel is linked to the right to create a clip and send to a target Limitations 1. One ingest of each type at a time on a channel: since the ingest works in a start-stop sequence, once an ingest is started, the start button is disabled. The first ingest has to be stopped before starting a new one. It is, however, possible to start an ingest on the recorder and then start another ingest on the stream linked to that recorder. 2. Only two logical networks are allowed: one HiRes network and one LoRes network. It is the user's responsibility to ensure that all the machines on one of his logical networks are in the same SDTI network. If that is not the case, some operations like SDTI copies will not be work. 3.2 Ingest scheduler Introduction Workflow 1 : Scheduled event or News agencies feed Feeds must be ingested on XT following a predefined planning. A football match will start at 20:00 and will end at 22:05

9 Date : 15-mai-09 Page: 9 File: A Reuter s feed will be broadcasted between 11:00 and 11:15 The Media manager wants to be sure that the recording will be automatically protected and wants to automatically send a stream file to the post-production. These jobs can be defined before the ingest in the ingest scheduler. IP Director will automatically create a clip and/or a stream file when the ingest is planned to start Workflow 2 : Planning application A planning application determines which feed must be recorded and at what time. This planning is exported into an XML file and imported (automatically or manually) in the Ingest Scheduler. An IP Director administrator will see which ingest has been planned through the ingest scheduler interface Workflow 3 : Multiple feeds control A Media manager wants to have a global overview and a global control of its recording channels. He wants to have the opportunity to start an ingest at any time (XT or stream) or plan ingests in the future even if the recorder is offline Features XT and Stream control The Ingest Scheduler has been designed to control ingests on XT recorders (HiRes or Lores) and to control streams of these recorders to files. The recorders and streams are grouped by logical entity. The channels recording the same video content are grouped together (HiRes recorders, LoRes recorders, HiRes streams, LoRes streams) Graphical interface The ingest scheduler provides a timeline view of each recorder and stream controlled by IP Director

10 Date : 15-mai-09 Page: 10 File: Each ingest created through the Ingest Scheduler is graphically represented on the corresponding recorder and can be managed through this interface. The ingest block are also colour-coded to directly show their statuses (Scheduled, Recording, Recorded, Failed) Drag&Drop operations An ingest can be created on any recorder/stream by a drag&drop operation. Any ingest block can also be extended, reduced, moved or copied by drag&drop. This provide an intuitive graphical interface to quickly create the ingest schedule One Shot, Repeat, Repeat every Ingest can be created in 3 different ways : - One Shot ingest : an ingest with defined start and stop date and time occurring one time. - Repeat ingest : Multiple ingests with defined start and stop time occurring every defined day of week (every week day between 11:00 and 11:15)

11 Date : 15-mai-09 Page: 11 File: - Repeat Every ingests : Multiple ingest with the same duration occurring every period of time (15 minutes every hour, ). This schedule type can also be defined to split an ingest into several clips or stream files (i.e. 4 hours ingest sliced into 4 1 hour files, ) Ingest statuses and reporting The Ingest Scheduler displays also global information on the recorders managed by IP Director (recording status, remaining capacity) and on the streams launched through IP Director (Recording status, latency, remaining capacity on the target storage) Each ingest is displayed with a coloured block (Blue = scheduled; Orange = Recording; Green = Recorded; Red = Failed) A grey block means that a stream is scheduled without corresponding growing clip on the XT.

12 Date : 15-mai-09 Page: 12 File: Logsheets associations When an ingest block is created it can be associated to a new or an existing logsheet as protect media. This functionality permits to associate a protect media to a logsheet before the ingest and the logging Import Export Schedules can be exported for reporting or synchronisation purpose Schedules can also be imported from a third-party application. The import-export format is XML or CSV Ingest Scheduler user rights A user can control the ingests on a recorder without having to be admin. A right on a HiRes recorder gives the right to schedule ingest on the HiRes recorder, the Lores Recorder, the HiRes stream and the LoRes stream Layout management The selected recorder and the display options are saved in the layouts. A layout can be recalled to recover a saved ingest scheduler display Limitations The ingest blocks are created only on the displayed channels (WYSIWYG) No way to hide a HiRes recorder 3.3 Recorder Panel Introduction Traditionally, the recorder panel has been used for monitoring the status of the recorders and start/stop recording. The new recorder panel has been redesigned and also has the added feature of being able to do clips Features Possibility to change the recorder Like in the control panel, the operator can click on the recorder name and choose which recorder the panel is linked to.

13 Date : 15-mai-09 Page: 13 File: Possibility to make clips The operator now has the possibility to make clips directly from the recorder panel, without the need for a control panel Limitations 1. No growing clips from the recorder panel: the sequence for creating a clip in the recorder panel is Mark In, Mark Out, Save. The save button is only enabled when an In and an Out have been marked. There is no possibility of making growing clips.

14 Date : 15-mai-09 Page: 14 File: 3.4 Fill and Key ingest Introduction The IP Director version 5 will manage the simultaneous ingest of fill and keys either from SDI inputs or via the importation (restore) of 2 graphical files Workflows Workflow 1 : SDI ingest of fill and key clips on the same recorder channel. Pre-requisite : Coniguration : - the fill and key clips are located on tape (but could be played out directly from the graphical device). - The SDI output of the VTR is ingested on 1 SDI input of the XT - [optional]the user table is set on VITC or HANC VITC. In this case, the VITC of the fill clip must corresponds to the VITC of the key on the tape. Description : Manuel SDI ingest of fill and key clips on the same recorder channel 1. the operator loads the tape and press play on the VTR. 2. The fill and key clips are ingested separately. 3. [optional]the operator selects the user table (VITC) from the control panel 4. The operator browse the train, find the IN and OUT point of the fill clip. 5. The operator creates the clip, define it as a fill clip 6. [optional]the operator restripes the T/C 7. The operator creates the key clip the same way 8. The operator manually associates the key clip to the fill clip using the database explorer. Reasons for implementation : This workflow is very simple to ingest fill and key clips located on the same tape. They will then be ingested separately but on the same ingest channel of the XT. If the VITC is used, it will help the operator finding the first frame of the fill and key clips and will avoid mistakes. It is not always easy to find the first frame because the images are not easy to differentiate, so you re never sure that you get the perfect sync between the fill and the key, and the operator needs to redo the whole process. It would be perfect if the XT could be used as a real keyer based on the key Workflow 2 : VTR ingest of fill and key clips (on the same recorder channel). In this workflow, the operator uses the autoedit or batch digitize function and the VTR engine to ingest the fill and the key clips.

15 Date : 15-mai-09 Page: 15 File: Pre-requisite : Configuration : - The fill and key clips are located on tape. - The SDI output of the VTR is ingested on 1 SDI input of the XT - The VITC is used : o On the VTR : generated on the SDI output o On the XT : VITC or HANC VITC is stored in the user T/C table. Description : VTR ingest of fill and key clips on the same recorder channel (auto-edit) 1. the operator loads the tape in the VTR. 2. The operator defines the IN and OUT point in the VTR interface as well as the clip information. He can define if the clip is the fill or the key. 3. The operator presses the Autoedit button. 4. The system prerolls the tape, records and creates the clip on the XT. The user T/C table is used as the T/C reference. 5. The operator ingest the key clip the same way 6. The operator manually associates the key clip to the fill clip using the database explorer. Pre-requisite : Configuration : - The fill and key clips are located on tape. - The SDI output of the VTR is ingested on 1 SDI input of the XT - The VITC is used : o On the VTR : generated on the SDI output o On the XT : VITC or HANC VITC is stored in the user T/C table. Description : VTR ingest of fill and key clips on the same recorder channel (batch digitize) 1. the operator loads the tape in the VTR. 2. The operator imports or creates the batch list containing the clip information. Clip fill or key information can be defined at this stage. 3. The operator presses the Batch digitize button 4. The Key and fill clips are created. 5. The operator manually associates the key clip to the fill clip using the database explorer Workflow 3 : SDI ingest of fill and key clips simultaneously on 2 recorder channels In this workflow, the fill and key clips are ingested at the same time on 2 recorder channels. Pre-requisite :

16 Date : 15-mai-09 Page: 16 File: Configuration : - Graphical device The output of the GFX device is connected to the router (fill and key), and in turn to 2 inputs of an XT (for baseband recording) - XT : o 2 SDI inputs, 1 or 2 SDI output or gige player. o Timecode : LTC is used as ingest time reference VITC or HANC VITC can be configured to be recorded in the user T/C table, in order the system uses this timecode to define the T/C associated to the shortin of the clip. Description : SDI ingest of fill and key clips simultaneously on 2 recorder channels 1. The operator gangs 2 recorders in fill and key mode from the channel explorer 2. The operator plays the clips synchronously out of the GFX device 3. From the gige player or from a player channel of his XT, he selects the T/C table 4. The operator browses the train (fill or key), find the IN and OUT point of the clip. 5. The operator creates the clip and eventually adds metadata 6. The system automatically defines the correct type for the clip (fill or key) as it knows on which recorder channel it has been created. 7. The system automatically creates the corresponding fill or key clip on the fill or key recorder channel. LTC is used as the time reference to find the corresponding field on the other recording channel. Depending on the user s selection, the T/C associated to the shortin of the clip will be taken from the LTC or the user T/C table 8. The system automatically links the 2 clips as fill and key Workflo w 4 : Graphical file ingest through a restore process (using XFile or XTAccess) Ingest of still pictures (automated process) 1. the graphical file is available on an IT based storage. Typically the file is a TGA (with alpha channel for the key). 2. Configuration in MXC, the operator setups a. the software in automatic import mode, b. defines the duration of the file which will be created. c. creates a post process to generate the file restored to an XT. 3. The MXC polls that directory and create the fill file. 4. The MXC sends an XML file to the XFile or the XT Access to restore the fill file on the XT. 5. The MXC creates the key file (using the alpha channel in the TGA file) 6. The MXC sends an XML file to the XFile or the XT Access to restore the key file on the XT. The fill and the key files are available on the XT but not linked as fill and key. 7. The operator associates the fill and the key files manually in the IP Director interface. Limitations : o o for files with alpha channel, only uncompressed TGA files are supported The TGA file cannot be selected from the IP Director interface.

17 Date : 15-mai-09 Page: 17 File: Ingest of animated sequences The difference from the workflow above is the fact that the animation is composed of one tga file per frame which are all dropped in the same directory. 1. the graphical file is available on an IT based storage. Typically the file is a suite of TGA files (with alpha channel for the key), one file per frame. 2. In MXC, the operator setups a post process to generate the file restore to an XT. 3. In MXC, the operator selects the file corresponding to the first frame of the animation and start the process. 4. MXC creates the animated fill file (decoding all tga files available in the directory). The duration of the file corresponds to the number of files available in the directory in frame. 5. The MXC sends an XML file to the XFile or the XT Access to restore the fill file on the XT. 6. The MXC creates the key file (using the alpha channel in the TGA file) 7. The MXC sends an XML file to the XFile or the XT Access to restore the key file on the XT. 8. The MXC sends an XML file (with the metadata) to the IP Director in order he can automatically link the 2 files as fill and keys. Limitations : o o for files with alpha channel, only uncompressed TGA files are supported The TGA file cannot be selected from the IP Director interface Workflow 5 : Backup and Restore fill and keys Pre-requisite : A fill and a key clip are created and linked Description : Backup and restore fill and key clips 1. the operator backups fill and key clips (can be done from the remoted, or the IP Director or from the XFile interface) 2. the system (XFile or XTAccess) backups the clips (and keep the link between the 2 clips) 3. The operator restore the fill and key clips on an XT (can be done from the IP Director or the XFile interface) 4. The system (XFile or XTAccess) restores the clips 5. The clips are available on the XT and are linked. 6. The clips are available in the IP Director interface and are linked. Reasons for implementation : Want to keep the association when restoring the clips Fill and Key playlist management Create fill and key playlists When the operator creates a new playlist, if he specifies the playlist is fill, the key playlist is automatically created as well.

18 Date : 15-mai-09 Page: 18 File: Manually associate 2 playlists as fill and key The operator can manually associate 2 playlist by drag and dropping the fill playlist on the key playlist and holding the shift+ctrl key at the same time Open/Preload a fill or key playlist When 2 channels are ganged as fill and key, when the operator preload a fill playlist on the fill channel, the corresponding key playlist is automatically loaded on the key channel Insert elements (clips, growing clips, train) in a fill or key playlist. When the operator insert a fill clip into the fill playlist, the corresponding key clip is automatically inserted at the same position in the key playlist. If the clip dropped is not linked to a key clip of if the clip is not a fill clip, a black or white clip (depending on a setting) of the same duration is inserted at the same position in the key playlist Modify elements in a fill or key playlist When the operator modifies (trim) a fill element, the corresponding key element in the key playlist is trimmed the same way Move elements within a fill or key playlist When the operator moves an element in the fill playlist, the corresponding key element is moved at the same position in the key playlist Remove elements from a fill or key playlist When the operator removes an element from a fill playlist, the corresponding element is also removed in the key playlist. 4 Playout 4.1 Control Panel Introduction The control panel, software player and playlist control panel have now a common interface.

19 Date : 15-mai-09 Page: 19 File: All features described in the document will be available for IPD release 5.5, except the postponed features Modification of the Control Panel GUI Basically, it has the same behaviour as in version 4 except the following : o o o o o o lock button is located on the left of the channel name on-air button has been removed (the background of the name flashes RED when on-air) Element type icon located on the left of the clip name (in order to know which type of element is loaded on the channel : hi-res clip, lo-res clip, playlist element, train, growing clip, file) New T/C control (possibility to select if date and table used must be displayed or not) New Append button : append the element loaded on the channel in the default playlist. Indication of ganged PGMs: two ganged PDMs appear with the same color of the title bar.

20 Date : 15-mai-09 Page: 20 File: Partial restore/partial backup In case a file is loaded on the software player, the operator can perform a partial restore the following way : 1. define a new IN 2. define a new OUT 3. right click and select Restore to XT, then select the XT. In case a clip is loaded on a control panel, the operator can perform a partial backup (or Send To) the following way : 1. define a new IN 2. define a new OUT 3. right click and select Send to, then select the target Any target can be selected (AVID, FCP, Directory, ) Associate a control panel to a playlist panel. When a playlist element is drag and dropped on a control panel, the panel is automatically associated to the playlist panel from which the element comes from. The title bar of the playlist panel and the control panel turns blue to show the association (same as for ganged PGMs) The background of the channel name is also in the same colout. This allows modifying (trimming) a playlist element on an edit channel Limitations The control panel, software player and playlist edit control panel have been merged into one interface but the system will NOT automatically adapt the interface depending on which element is loaded on the channel. For example, if a file is drag and dropped onto a control panel (channel), the software player interface will not automatically be displayed in order to preload the file but an error message will be displayed.

21 Date : 15-mai-09 Page: 21 File: 4.2 Production playlist Introduction There will be no more playlist editor in version 5. The playlist editor will be separated into 3 windows : Playlist panel, Database explorer and Control panel. Several playlist panel can be tiled vertically next to each other to allow the control of several playlist side by side. The playlist panels can be called via a Fx shortcut like any other control panels. Remove some limitations of version 4 : o o Playlist can be created immediately from the playlist tree in the DB explorer. It will no more be necessary to pass by a bin to create a new playlist. Playlist can be created online immediately; no more need to create an offline playlist first General playlist limitations of version 5 1. No redundancy 2. No A/B Roll management 3. No playlist browsing in the software player 4. No Split-Audio management in playlist, use IP Edit 5. No files in playlist, only clips. It means that you cannot create playlist from files on the nearline storage Playlist panel GUI Here is how the new playlist panel will look like :

22 Date : 15-mai-09 Page: 22 File: The panel can be resized vertically and horizontally New functions The playlist panel will have exactly the same functions as the playlist tab of the playlist editor of version 4, plus the following functions : partial loop A loop column will be added to the grid to display partial loops.

23 Date : 15-mai-09 Page: 23 File: If only one clip must be looped : Limitation : only one loop level managed, no nested loop. Two types of loop are available : - infinite loop - counter loop jump on time The operator can define if an element must be started at a predefined time (whatever the element loaded). This function is only available in playlist mode. The start on time function available in previous IP Director release is still available. Difference between jump on time and start on time. Jump on time : the playlist will jump on the element at the predefined time whatever the element currently loaded. Start on time : the element must be loaded in order it starts at the predefined time GOTO ELEMENT When the operator clicks on the GOTO to element button (located on the right of the skip button), the system jumps on the selected playlist element. In case multiple elements were selected, the first one of the selection must be considered.

24 Date : 15-mai-09 Page: 24 File: If the selected element is inside the loop currently being played : the operation is performed, the counter loop is not reset. The mode defined on the button should be taken into account (ASAP or on SHORT OUT). A chain is performed if the system is in transmission mode, a preload is done if the system is in edit mode. The button is available in transmission mode as well as in edit mode. The operational mode is written below the button ASAP or OUT depending on the mode. The GOTO ELEMENT function can be used to exit a partial loop at anytime Goto Element Timecode When the operator clicks on the GOTO element timecode button (the one below the loop button), the goto element timecode zone is displayed or hidden depending if it was already displayed or not. When the operator validates a Timecode in the zone, the system performs a goto TC inside the selected playlist element Macro commands and tag management It is now possible to apply macro commands on playlist elements. The possible macro commands can insert a tag (GPI, audio swap, HIDE or MUTE) as well as modifying a transition (still/start mode, effect, default transition). The macro commands are defined in the playlist settings category. Refer to the settings specifications for more information Apply a macro command To Apply a macro command, just press the INSERT key on the keyboard followed by the macro command number. (i.e : INSERT 2) View tag information From the playlist interface.

25 Date : 15-mai-09 Page: 25 File: Click on a tag icon in the tags column of the playlist. The system displays the related tag information. From that window, it is possible to edit/remove/goto that tag. Moving the mouse to another tag when the window is opened, will automatically display the information related to that tag. From the control panel. When a playlist element is d&d on a control panel for edition, its tags are displayed on top of the jog bar at the position where the tag will be triggered. The numbers indicates the tag number. If no number is displayed, it means that several tags will be triggered at that position. The operator can click on a tag icon to display the tag information window (same as in the playlist interface) Edit a tag Click on a tag icon (either in the playlist interface or in the control panel), then select EDIT from the tag information window.

26 Date : 15-mai-09 Page: 26 File: Goto tag Click on a tag icon (either in the playlist interface or in the control panel), then select GOTO from the tag information window. Double click on a tag icon from the control panel, will automatically go to the tag position Remove a tag Click on a tag icon (either in the playlist interface or in the control panel), then select REMOVE from the tag information window LOCK ON AIR POSITION The lock on-air position button (located on the left of the AuxClip zone) is used to keep the on-air position always visible at the same position in the playlist. When the operator clicks on the button, the lock on-air position mode is activated/de-activated. When activated, the on-air element is always displayed at the position where it was when the operator clicked on the button (position X) if there is enough elements after the on-air element to completely fill up the grid. Otherwise, the on-air position will follow the elements until the end of the playlist is reached. In case the playlist is in loop, when it loops, the on-air position follows the playlist and jumps on the first position, then moves to position X and stays at that position until there is not enough element after the on-air element to fill up the grid. The mode is automatically reset when : - the operator scrolls in the playlist (using the scroll bar or the mouse wheel or when he uses the up and down arrows in the list and make it scroll) - When a clip, a train, a timeline or a growing clip is loaded on the channel (in other words, when the playlist is unloaded) as run log Definition : An as run log is a file which logs what has been effectively played on a channel and when. The as run log will than have a format such as an EDL. Assumptions :

27 Date : 15-mai-09 Page: 27 File: The As Run Log is a characteristic of a channel (pgm/prv mode is considered to be one channel, A/B is considered to be 2 channels). The As Run Log file will have a limited size, when the size is reached a new file is created. A new file is created everytime the operator starts the as run log. All types of elements (clips, playlist, train, growing clips) must be considered in the as run log. Use case : 1. The operator loads an element (playlist, clip, timeline, ) on a play-out channel 2. the operator starts the as run log of that channel 3. the XT logs all elements which are effectively played on the channel. A new entry in the log is created every time the on-air element changes. Limitation : Timeline are not considered in the as run log Manage control track The operator will have the possibility to define a control track for the playlist. A control track is the possibility to manage a continuous output timecode when the playlist is played out. This T/C track will be available on the VITC output of the channel. The start T/C of the track can be defined by the operator. When the operator selects Regenerate T/C Output from the playlist menu, the Continuous T/C track window is opened.

28 Date : 15-mai-09 Page: 28 File: Limitation and constraints : - If the playlist includes still/start modes (stop on last frame, stop on first frame, ), these modes are not taken into account and automatic transitions are considered. - The control track does not take the element speed into account, 100% speed is considered Manage LTC and USER T/C table LTC and USER T/C information of playlist element will be displayed in the playlist grid Post Roll Possibility to define a post roll for every break in the playlist. The post roll is the ability to playout a element a certain time after its defined shortout point. The play-out countdown is based on the shortout anyway, telling the producer when he has to start the effect on the switcher to pass to the next element. Post roll mode must be activated/de-activated by the operator, the post-roll duration is customizable via a contextual menu :

29 Date : 15-mai-09 Page: 29 File: Activate Post-Roll De-activate Post-Roll Activate Post-Roll (next transition only) s00 XXsXX 03s00 05s00 Customize Post-Roll duration Thumbnails Thumbnails will be created automatically for every playlist element. The thumbnail will be created based on the ShortIN +/- offset, of the element. Offset can be defined in the settings End Cue Possibility to send a GPI OUT several seconds (customizable) before the next break in the playlist. Used by TVB to trigger a countdown UNDO Possibility to undo basic operations : - Insert an element (clip, growing clip, train) or a group of elements - Insert LIVE or DELAY - Insert a Linked clip - Replace by a linked clip - Insert a comment - Edit a comment - Move an element (playlist element, comment or group) in the playlist - Remove an element or a group of elements - Skip Element - Trim Element - Define partial loop - Unloop (a partial loop)

30 Date : 15-mai-09 Page: 30 File: - Group - Ungroup - Define jump on time - Modify transition (vid effect, vid effect dur, audio effect, audio effect dur, split audio) - Modify Still/Start mode - Set Speed Manage varid Manage varid for playlist and playlist elements Import playlist automatically Possibility to drop an EDL (XML) in a watch folder and import it automatically in the IP Director Add metadata to playlist Possibility to add a tapeid, keywords and additional metadata (from metadata profile) to playlist. The New Playlist window and Edit playlist window are updated accordingly.

31 Date : 15-mai-09 Page: 31 File: Convert to timeline Convert a playlist to a timeline is available via the playlist contextual menu or simply by d&d in the IP Edit.

32 Date : 15-mai-09 Page: 32 File: AS WILL RUN LOG Dump playlist elements in a file When a playlist is played out, dump the next elements to be played out in a text file. This file can be parsed by a 3 rd party application to know what will be played out next. Typically useful to populate web site. 4.3 IP Edit Introduction Ip Edit is dedicated editing module inside the Ip Director framework that use XT2 server with Multicam 10. It requires a dedicated licence. (See Sales for pricing) The Ip Edit main features are: 1 video track, up to 4 audio tracks Video player preview on VGA, Video recorder (Timeline) preview on external video monitor Fast and intuitive editing functions (Insert, overwrite, roll, trim, delete) with drag and drop and keyboard shortcuts Replace mode for advanced graphics editing (Gfx is incrusted externally on the video mixer) Voice Over (done externally through the audio mixer) 8 GPI Outputs can be linked to clips, transition effects and boundary marks (for replace) Intelligent Browser (automatic search by T/C) Video dissolve/wipe, Audio dissolve Clip/Track Audio volume automation Cue and play timeline on Control Panel and Remote D Local and distant clip and trains can be used (XNet). Undo / Redo on editing 7 configurations available new v5.6 Slow motion in timeline new v5.6

33 Date : 15-mai-09 Page: 33 File: Multi-camera angle selection and replace in timeline/player new v5.6 Full convert playlist to timeline new v5.6 Full VITC Support new v5.6 VITC Legacy/User clip support new v5.6 Copy Timeline optimisation new v5.6 Purge Management and Timeline Deletion (Delete Timeline, Delete Timeline and clip) new v5.6 Snap to Out (Snap to tail) Replace OSD Countdown new v5.6 Manual mode for Replace Mute Audio Tracks new v5.6 Remove timeline marks after edit new v5.6 New edition of GPI (select tracks) + move using drag and drop or arrow keys new v5.6 Now line as mark in or mark out in timeline new v5.6 Keep boundary marks on player new v5.6 Move clip gpi (lasso + drag, minus/plus keys or CTRL+ minus/plus keys) new v5.6 Add clip gpi at now line position new v5.6 Renaming elements in timeline new v5.6 Now line follow timeline when playing new v5.6 Display audio volume when moving line new v5.6 Macro Command new v5.6 Blocked parralel mode security new v5.6 Automatic Unlock Timeline mode when exiting Ip Edit new v5.6 Move selected elements with plus/minus x frames new v5.6 Trim with plus/minus x frames new v5.6

34 Date : 15-mai-09 Page: 34 File: General Ip Edit Limitations Minimum clip size = 10 Frames No audio mix-down internally on the XT It requires an external audio mixer for mix down to stereo or other formats. No real-time edit redundancy No simultaneous editing on a timeline panel and a remote D No software player support for timeline Ip Edit can not work with nearline storage or XL2 proxy server materials. Frame based editing only (even in Progressive format, no field editing) No XT server native flatten process of timeline (need replace) No support for playing timeline in playlist No conversion from timeline to playlist No Add GPI to slomo clips except replace Technical information An Ip Edit panel requires 2 PGM outputs to run. We usually call the 2 PGM a Timeline Engine. Timeline engine can be PGM1/2 or PGM3/4 new v5.6 PGM 1 and 3 is the timeline output channel when PGM 2 and 4 is the player channel. Every audio channel is automatically routed to both PGM when using player or timeline. AVH board is required to preview player channel on VGA. External video monitor is required to preview the Timeline. Timeline Available Configuration: AVCFG 4 channel audio records 1 track 4 mono new v5.6

35 Date : 15-mai-09 Page: 35 File: 4 tracks mono new v5.6 2 tracks stereo AVCFG 8 channel audio records 1 track 8 mono new v5.6 2 tracks 4 mono new v5.6 4 tracks stereo 1 track 6 mono + 1 track stereo new v Ip Edit panel GUI Ip Edit Panel has 3 main zones:

36 Date : 15-mai-09 Page: 36 File: Player The Player allows the editor to load local or distant clip, growing clip or train to create some element that will be added to the timeline. See Browser Browser allows the editor to list and filter the content of the Ip Director database like a normal Database Explorer but it has a dedicated filter tools called Multi camera Timecode Filtering. See Timeline The timeline is where the editor creates, manipulate and organize its sequence using the different editing features. See 7 In case of 2 VGA screen connected to the Ip Director Host station, the Ip Edit panel can be used on the left (main) or right (secondary) VGA Activation Philosophy As the Ip Edit require 2 PGM to play timeline with transition effects and also 2 PGM to ensure Slip, Slide and Trim operations, the 2 PGM of the Ip Edit needs to be switched in different mode. There is a notion of activation linked to the player or timeline. When the player or the timeline is activated, a white frame is display around the player or timeline. This activation frame also used to route the keyboard shortcuts and shuttle pro to the current activated zone.

37 Date : 15-mai-09 Page: 37 File: Player Features The player can browse and play local or distant clip, growing clip or train. To load an element in the player, the editor can drag and drop it from a database explorer, a control panel, the Ip Edit Browser or double click in the Ip Edit Browser. Overwrite, Insert and Match Frame Edit new v5.6 button are different ways to add A/V element to the timeline.

38 Date : 15-mai-09 Page: 38 File: Source Track selection allows the editor to select which part of the A/V element he wants to add in the timeline Common wor kflow Insert Select source tracks, Mark In, Mark Out, Insert Clip is inserted at the now line position in the timeline. Explanation: This function inserts the new clip on the timeline, while displacing the following clips if there is some. Everything that is on the right the now line will be moved of the length of the clip added Overwrite Select source tracks, Mark In, Mark Out, Overwrite Clip is overwrite at the now line position in the timeline. Explanation: This function doesn't move the other clips that are on the right of now line, contrary to the insert function Point Edit Define boundary marks in the timeline, select source tracks, Mark In, Overwrite Clip is overwrite at the boundary marks position Explanation: Let's say that you had to change the camera angle in a part of your sequence between Mark In and Mark Out. We only set an in point and no outpoint to the clip in the player assumes that it is not of great importance where the action in that clip will end Point Edit new v5.6 Define boundary marks in the timeline and player. Clip is added to the timeline with Fit to fill and automatic pseed change calculation Match Frame Edit new v5.6

39 Date : 15-mai-09 Page: 39 File: Place the now line over the clip you want to replace in your timeline, load the new clip or train you want to use into the player, move the player to the desired image (no in or out marks required), click the Match Frame Edit button. It replaces the old shot in your Sequence without ever using in or out marks. Explanation: The Match Frame Edit button uses the existing in and out marks of any given shot in your timeline to determine its duration. Simply but you do not have to actually mark and in or an out point in the player to use it Slow (and fast) Motion new v5.6 4 Point Edit (Fit to fill) Extend Slow Select and set speed SLSM 3x and 2x support Limitations You can create new clip available from everybody in the Ip Director network (using the save button) but not update an existing one. You can t preview more than one stream at a time. No real time multi camera preview and no support for ganged channels too. No trim center for slow/fast motion element in timeline

40 Date : 15-mai-09 Page: 40 File: Browser Features The browser has mainly the same features as a common database explorer but misses the Auto-Play, Assign and print mode. It has a dedicated Multi Camera Filtering Mode that allows the editor to search for in the entire database for different clip, growing clip and train that contain the same Date and timecode as the actual image display in player or actual image at the now line position in the timeline Common workflow The editor activates the Multi Camera Filtering mode using the dedicated button. He selects either player mode or timeline mode. If the editor selects the player mode, every time he pause the player, the date and T/C of the picture are pushed inside the dedicated filter. If the editor presses refresh in the browser, the makes a filter on this information.

41 Date : 15-mai-09 Page: 41 File: The editor can double click or drag and drop listed element inside the player and the element goes automatically to the same T/C. If the editor selects the timeline mode, every time he pause the timeline, the date and T/C of the picture are pushed inside the dedicated filter. If the editor presses refresh in the browser, the makes a filter on this information. The user can double click or drag and drop listed element inside the player and the element goes automatically to the same T/C, than the editor can make a 3 point edit or a replace to change camera angle in the timeline. The Multi camera filter can be used simultaneously with the normal Quick text Search, Column filters and saved filters tools Limitations Only maximum 4 audio tracks for an entire XT No Auto-Play mode No Assign mode No Print mode No keyboard shortcuts Timeline Editing Features Insert Overwrite Match Frame Edit Cut

42 Date : 15-mai-09 Page: 42 File: Trim Extend Slip Slide Delete Match Frame Move All these operations can be done using button, drag and drop, shuttle pro or keyboard shortcuts. Keyboard shortcuts will be user definable but default layouts are based on a well known editing product GPI 4 GPI Outputs (Relay) are available. 4 additional GPI Outputs (TTL) could be used as well (to be confirmed) They can be set to make: High Pulse Low Pulse Level High Level Low In addition to use Pulse, the editor can define a GPI with a level high and some frames after, the same GPI with a level low. In that way, Ip Edit supports all the triggering cases of third party devices. 3 types of GPI are available inside the Ip Edit: GPI linked to clips Editors will be able to add GPI linked to video or audio clip.

43 Date : 15-mai-09 Page: 43 File: When the clips that have GPI are moved in the timeline, their corresponding GPI are moved as well. The editor right clicks somewhere in the T/C Track of the timeline and select Add GPI, then define a GPI number and type GPI linked to video transition Editors can link GPI to the start and end of transition effect allowing the Ip Edit to trig an external graphics device that can overlap a fancy animated graphics (RTD) over a wipe transition GPI linked to boundary marks for replace Editors can link GPI to mark in and mark out in the timeline to trig external device like audio mixer (for voiceover) or downstream keyer (for graphics or characters inside the video)

44 Date : 15-mai-09 Page: 44 File: An offset can be define to ensure graphics fade in and fade out to be replaced. A external device latency compensation is also available to manage to ensure frame accurate replace editing Transitions Effects Ip Edit support video transition effects like: Dissolve Wipe Left Right Wipe Right Left Wipe Up Down Wipe Down Up Ip Edit support mix audio transition Every audio cuts point is µmix allows smooth audio transition even in cut/cut Transition effects can be edited individually on any timeline track. Transition can be before cut, centered or after cut.

45 Date : 15-mai-09 Page: 45 File: In contrary of play-list, adding effect doesn t change the overall timeline duration. It virtually extend clips like in any other NLE. Add Transition effect: Place the now line near the desired transition, select the desired tracks, click on the Add Transition Effect button Delete Transition effect: Place the now line near the desired transition, select the desired tracks, click on the Remove Transition Effect button Replace Replace process allows replacing partial video and audio tracks using an recorder on the local XT. Video replace

46 Date : 15-mai-09 Page: 46 File: User set a mark in and marks out in the timeline, select video track. User clicks on replace button or press SHIFT + Spacebar. The replace process makes a preroll and than play the timeline till the mark out is reach, than play a post roll. A new clip is created and replaces the video selection between mark in and mark out. Audio replace (voice over) User set a mark in (and marks out) in the timeline, select audio track. User clicks on replace button or press SHIFT + Spacebar. The replace process makes a preroll and than play the timeline till the mark out is reach or manual stop, than play a post roll. A new clip is created and replaces the audio selection between mark in and mark out. Replace settings window allows to define pre-roll, post-roll, GPI and audio matrix to make automatic swap for the new clip.

47 Date : 15-mai-09 Page: 47 File: Replace in progress: Timeline Management Create timeline Delete timeline Clear timeline Close timeline Convert play-list to timeline Create an on-line copy Copy clips (short or long) Publish timeline Audio Volume automation Clip audio volume inside an audio track can be automated using key frames. The user presses a dedicated button to zoom an audio track entering the volume automation mode. User can add some key frame by double clicking in the volume line than move them according to the level in db they want. The overall volume of the audio track can be increase or decrease by step of 0,1 db or 1db.

48 Date : 15-mai-09 Page: 48 File: The global range of volume automation is user definable with a maximum of +18db and minimum of -122db. Every key frame is linked to the clips and follows them in case of move. Several key frames can be changed in one time between mark in and mark out Swap / Mute Swap and mute can be added to whole clip(s) or to any position in an audio track. User can select some clips, right click and apply swap mute to one or more whole clip(s). User can presses a dedicated button to zoom an audio track entering the swap/mute mode. The user can use mark in and mark out to define swap/mute between these boundary marks.

49 Date : 15-mai-09 Page: 49 File: Super Quick Start Guide 1. Open Ip Edit Editor clicks on Ip Edit main button. 2. Assign Timeline Engine Editor right clicks on the bottom left zone and selects its timeline engine PGM. 3. Assign Recorder for (replace) Editor right clicks on the second bottom left zone and selects its recorder for replace.

50 Date : 15-mai-09 Page: 50 File: 4. Create a Timeline Editor right clicks on the grey bar in the timeline and select Create Timeline. Editor enters a Timeline name and a configuration. 5. Add clips Editor loads a clip or a train in the player by drag and drop from the browser or external database explorer. Editor defines boundary marks in the player. Editors press V (insert) or B (overwrite) keys to add the clip at the now line position in the timeline or simply drag and drop from the player to the timeline. 6. Extend clip

51 Date : 15-mai-09 Page: 51 File: Editor place a mark out in the timeline and press extend. 7. Trim clip Editor enters the trim mode by lassoing the transition or press U key with the now line near the desired transition. Editor drags and drops the transition to change it. Editor can change the trim mode by click on both side of the transition. 8. Cut clip Editor place the now line at the desired cut position, select the tracks and apply a cut by pressing Add Edit button (Cut).

52 Date : 15-mai-09 Page: 52 File: 9. Add transition effect Editor place the now line at the desired transition, clicks on the Add FX transition button (yellow) and enter its effects settings. 10. Making a replace Editor place a mark in and mark out, select the track he want to replace than press CTRL + Spacebar or Replace button (Rec).

53 Date : 15-mai-09 Page: 53 File: 4.4 Remote P Layout Hardware

54 Date : 15-mai-09 Page: 54 File: Software (Remote Control Manager) Features 1. Remote P is supposed to be used by AP and Playout operator that control one or more production playlists. 2. Nevertheless, any group of button can be assigned to PGM, even if they are associated with production playlist. 3. Each button (except pause) can be manually customized (using Remote Control Manager) and the button layout is saved with the layout. 4. functions available per group. 5. Direct access simultaneous control up to 4 PGM channels with visual feedback. 6. Color LED on button. 7. Each could be group of ganged channels. 8. Button functions : Play Play Var Previous Next Skip

55 Date : 15-mai-09 Page: 55 File: Go to Mark In Go to Mark Out Recue Preview Transition Fast Forward Fast Rewind Return Snap E/E Loop On Air How To Assign Channel to group of buttons The operator opens Remote Control Manager in the main Tools menu in the Ip Director. The user drag and drop a PGM channel from the channel explorer inside one of the 4 group box

56 Date : 15-mai-09 Page: 56 File: Customize buttons User right clicks on any of the button graphical display (upper or lower) A contextual menu with all the functions is display. User select the button function in the list 5 Content management 5.1 Near line management Near line management Near line management is the possibility for the IP Director user to browse A/V material that is not located on the XT server but on an IT storage on a network. It will allow the IP Director user to not only control the backup of a clip but also to browse the backed up clip and to perform restore operations when needed. Here are a couple of examples of workflows targeted by the near line management of the IP Director. Workflow 1 : 1. ingest material on the XT[2] server

57 Date : 15-mai-09 Page: 57 File: 2. make some logsheets and clips 3. backup all/some of the clips and clear the clips on the XT[2] to make some space 4. the users can still browse through all the A/V material and send it to all IP Director targets (including NLE s). The user doesn't even have to know whether the clip is on an XT[2] server or on his near line. Workflow 2 : 1. clips from previous productions are put on an XFile drive and taken to the production setup 2. the XFile drive is added to the near line directories of the IP Director 3. the operator can browse his files in the IP Director and restore the content that he needs for his production 4. he can start playing a clip from the IP Director interface as soon as the restore has started LoRes management With the rise of Hi Definition and the need for more and more people to browse A/V content, it is more and more often needed to provide proxy browsing. IPD can manage two different types of LoRes/proxy browsing: XL[2] LoRes When the proxy browsing is needed in real time, at the same time as HiRes content availability, then the LoRes can be ingested on EVS XL[2] servers. Each XL[2] record channel is linked to an XT[2] HiRes channel. The LoRes is immediately ready to be browsed. Using XL[2] also means the users benefit from the loop recording capability for the HiRes and LoRes. This is the preferred solution for big events like the Olympics. File LoRes When the LoRes does not need to be available straight away, a file proxy can be generated by transcoding selected clips. The IPD user can then browse the proxy file.

58 Date : 15-mai-09 Page: 58 File: When streaming material to a Near Line storage, XT Access also has the capability to do on the fly transcoding. In this case, the LoRes is generated at the same time as the HiRes file Features The new clip entity In order to incorporate the notions of near line and proxy browsing, the notion of an IP Director clip has changed slightly. The clip is now a logical entity that refers to a given A/V material. This A/V material can be in different formats (HiRes, LoRes) and on different physical supports (XT Server, near line storage). Each representation of the same A/V material is called a clip element. A clip element points to the physical resource behind the clip (XT clips and/or files). The figure below shows that a clip can be expanded to show its clip elements. An clip has a T/C In, a T/C out and a set of metadata associated to it (name, keywords, rating, user fields, etc). All this is common to all the clip elements. The interface will handle all the complexity behind the new clip entity. For example, if a user drags and drops a clip on a software player and a file element is present, it is that file element that will be loaded. If the clip has a LoRes and a HiRes version, it is the LoRes version that will be loaded in the software player. If the user changes the keywords of the XT clip (from the VGA for example), it is the keywords for the whole clip that are changed. To accommodate this new concept of multiple essences in one clip, the clips in the DB explorer can be expanded into clip elements. Thanks to this new concept, the user can transparently browse content on his XT server and on his near line storage. Since file browsing is not possible on a PGM from the XT[2] server, a new software player has been introduced to the interface. Using this software player, the operator can preview content from both worlds in the same interface.

59 Date : 15-mai-09 Page: 59 File: Near Line Configuration The IP Director will not manage A/V material anywhere on the network. Directories that need to be managed by the IP Director and visible in the interface must be configured in the remote installer. Each directory is defined by its name and its path. The name given to the near line directory in the remote installer is the name that the user will see in the file tree in the interface. Once a directory is configured in the remote installer, the IP Director will continuously scan this path, looking for new files or files being deleted. When a new file is found, the IP Director parses its metadata and updates its list of clips automatically in the DB explorer. The metadata can be in the mxf header of the file (for EVS MXF files) or in a descriptive xml file that has the same name as the A/V file. The descriptive xml file will be in the documented EVS Metadata format Proxy configuration When using XL[2] LoRes, the association between XL[2] channels and XT[2] channels is made in the remote installer IP Drive and XFile drives One of the interesting features of the near line management is to be able to review the content of multiple XFile drives with the powerful search and browsing tools that the IP Director offers. To this purpose, a new service will be available. It will automatically detect the appearance of a new drive or the ejection of a drive. It will report these drives to the IP Director, and the drives will be included in the files tree automatically. The service can be installed on any machine on which we want to detect drives dynamically. This means that the user will be able to browse through several XFile removable drives without having to update his near line configuration in the remote installer. When a drive is removed, the clips present on the drives are removed from the interface.

60 Date : 15-mai-09 Page: 60 File: There is, however, an option in the DB explorer to see the content of these offline drives. When the option is activated, the offline clips appear greyed out in the DB explorer. This allows the operator to see on which drive the clip is located. He can then retrieve the drive and plug it in. The clip is then ready to be browsed New tree arrangement Near line Node In the DB explorer, below the list of XT servers, there is a Near Line node. Under the Near Line node is the list of near line directories defined in the remote installer

61 Date : 15-mai-09 Page: 61 File: or detected by IP Drive. From this interface, the user has the possibility to browse the directories or create new ones. He doesn't, however, have the possibility of deleting or moving directories around. These operations must be done by a media manager with specific user rights. Hi-Lo configurations When XL[2] servers are configured in the setup, the presence of these servers is completely transparent to the user. This means that even a LoRes browser will always see the HiRes tree, will select his recorders based on HiRes recorder names and clip position with the HiRes LSM ID of the clip. This decision of "hiding" the LoRes network comes from experience acquired during the Olympic games on mixed setups where people got very confused. The LoRes is there for browsing purposes, to save bandwidth. The operators don't need to know about the LoRes XL[2] network. Media managers will have the possibility to see the LoRes tree by setting a "media manager view" user right. Clip Elements plugin The only tree standard operators will be able to see will be the Clips tree where clips entities are shown. To see clip elements in that view, the operator has to expand the clip.

62 Date : 15-mai-09 Page: 62 File: Media managers will be given access to the clip elements tree. This tree has the same nodes as the "Clips" tree but it shows individual clip elements (XT Clips or file clips). Media Files plugin This view is available for users with media manager rights. It is the physical view of the A/V files. In this view, the administrator can move and delete files and directories (hence deleting all references to the deleted file(s)). In media files view, expanding the file will show all the clips that point to this file Easier purge of clip elements Since the clip elements view is only available to media managers, we need a tool to easily purge a series of clip elements of the same type without purging the whole clips. Example: I have a series of clip with each a HiRes and a LoRes clip element. I want to purge all my HiRes clip elements. There is a new option available that lets the operator select what type of element he wants to clear. To delete all HiRes clip elements in a series of clips: - select the clips - right click - in the contextual menu, choose the "Delete selected clip elements" - in the popup window, check HiRes XT clip

63 Date : 15-mai-09 Page: 63 File: Software player/media viewer The software player allows the operator to browse content located in files but also content directly from the XT[2] server through the new GigE connection of the server. The software player can be chosen as a source for the control panel, in the same way as a normal PGM. Once a near line clip is loaded on the player, the user can make sub clips in the same way as in a normal control panel. Since streams are managed by the IP Director, an clip pointing to a stream can be loaded on the software player and used in a similar way than a growing clip on an XT server. The software player can be associated to a DB explorer or an IP Logger in the same way as a PGM.

64 Date : 15-mai-09 Page: 64 File: Backup/restore of clips An XT clip can be backed up to a near line directory by simple drag & drop on that directory or by doing a backup to near line. When the file starts to be backed up, a file clip element will appear if the cip is expanded. In the same way, a clip that only has a file element can be restored to an XT server by drag & drop to the XT server. The user can drag & drop on the root of the XT (restore to default page) or to a specific page. The user can also choose the restore option available in the clip contextual menu. The IP Director supports full and partial back up and restore Send to target The user will be able to do a send to target without being concerned about what type of element is in his clip. The IP Director will decide whether to do a backup of an XT clip or a partial copy/re-wrap of a file. (i.e : if the operator sends an clip to an AVID or FCP target, the system will first consider to send the XT clip present in the clip. If no XT clip is present in the clip, the file will be considered and sent to the NLE system).

65 Date : 15-mai-09 Page: 65 File: Supported file formats and codecs The IP Director will support all the codecs supported natively on the XT[2] server. Supported file formats for near line management will be EVS MXF, OP1A MXF and QT movie. QT Ref is not supported by the software player, so QT ref files will not be available for near line browsing. Users can still "Send To" a QT Ref file that will be used by another application (FCP for example). When using EVS MXF files, metadata can be retrieved from the MXF header itself or from a descriptive xml file. When using other wrappers, metadata will come from the descriptive xml file. Here is a table of supported file formats and codecs: SD HD MJPEG MPEG2 I- MJPEG IMX MJPEG std DNxHD Pro Res EVS Frame EVS MXF X X X X X X X OP1A MXF X QT mov X X X X X Please note that since there is no software decoding of Apple ProRes 422, this codec is supported on the near line storage but there is no software preview. For LoRes browsing, supported formats are Mpeg1, Mpeg2, XDCam proxy and P2 proxy Limitations In Version 5, there are a number of limitations to be aware of: 2. A playlist can only contain XT clips: this means drag & drop of an clip that only points to a file onto a playlist will fail. The clip must first be restored to an XT server and then put in the playlist. What will be allowed, however is the drag & drop of a clip containing an XT Clip into a playlist. The system will automatically consider the XT Clip inside the clip and will insert it in the playlist. 3. A playlist cannot be previewed in the software player. An XT playlist cannot be previewed in through the GigE capability of the software player. In order to preview a playlist, the operator must use an XT Channel.

66 Date : 15-mai-09 Page: 66 File: 4. The system will not automatically switch from the software player to a channel in a control panel. If the operator browses his XT clips/playlists in SDI through a control panel PGM, he will need a second control panel associated to the OCX to preview his files. Drag & dropping a clip that only contains a file element on a control panel associated to a PGM will do nothing. However, if the browser can browse the XT through the GigE, then he will be able to browse XT clips AND near line clips with the software player (but no XT playlists). 5. The sound monitoring of the AVH comes directly out of the AVH while the sound of the software player comes through the windows sound card. It is possible to connect a cable (provided with your IP Director workstation) from the output of the AVH into the audio line in of the motherboard. The audio monitoring of the AVH or the software player can then be done from the audio output of the motherboard. 6. The XFile publish function (publish near line clips on the SDTI) will NOT be managed in the IP Director. Instead, the user browses through his near line files, chooses the material he needs, and restores them. As soon as the restore starts, the clip can be played or put in a playlist. 7. Only one software browser can be open in the IP Director interface at a given time. This means no reviewing x different camera angles on x ganged software browsers at the same time. 8. At import: management of EVS MXF or EVS XML files with multiple clips only the first clip is imported. 9. At export: the xml file is generated at backup time. There is no update of the xml file to add sub clips added in the IPDirector interfaces or to update the data of the main clip (clip name, etc). This is only relevant in the event a drive is ported from one IPD setup to another in that case, only the original backed up clip is retrieved on the second setup. All updates and/or subclips are lost. 5.2 Metadata Management Introduction Indexation of the A/V content is playing an increasingly important role.

67 Date : 15-mai-09 Page: 67 File: In order to make the metadata content richer and more flexible, user defined profiles have been introduced to all elements (logsheets, clips, playlists, timelines) in the IP Director. A new user interface has also been added to help the administrator with the management of his profiles Features Profiles A profile is a list of User Fields. Each user field is defined by its header, type and value. There are five possible User Field types: - text (64 chars) - memo (512 chars) - number - date - T/C Each User Field is represented by a column in the DB explorer. The header of the user field is the name of the column. By default, the columns from the current profile are loaded in the DB Explorer. Since the profile columns are integrated in the DB explorer, the operator can use all the search tools for searching through the profile columns. The same profile can be user for any element type Entering metadata When an operator creates a new element (logsheet, clip, playlist, timeline), there is a metadata section to be filled in. If the user has the rights to do so, he can choose which profile to use for the element, otherwise, he gets the default profile specified by the administrator. Once the profile is chosen, the operator enters values specific to the element for the user fields.

68 Date : 15-mai-09 Page: 68 File: Profiles and values are saved between the creation of two elements, in the same way as the automatic keywords of the logsheet Profile management user interface There is a new graphical interface for managing profiles. In this interface, the media manager can create/update/delete a profile. When updating a profile, user fields can be added, removed, updated or re-ordered by drag & drop.

69 Date : 15-mai-09 Page: 69 File: User rights on profiles Users can either have the ability to choose their profile or be forced to use the default profiles defined by the administrator. If a user cannot choose his profiles, it means that the profile is imposed by an administrator. Each time the user logs on, the default profiles are loaded for him. The access to the profile management interface is also tied to a user right

70 Date : 15-mai-09 Page: 70 File: Limitations 10. Profiles are a flat structure: there is no possibility to build trees with user fields "under" other user fields. A profile is a set of user fields that can be ordered in a predefined way. 5.3 Bin management Introduction IP Director bins have always been a useful tool to help with the organisation of clips and playlists. Now, an operator can also put a timeline in a bin but more importantly, post process operations can be defined, making the bins and bin rules an integral part of the workflow Features for Version Bin rules The bins rules are now divided in two sections: - the filter condition: clips are automatically put in the bin if they satisfy the condition - post process: operation that is done to all elements dropped into the bin Filter condition This filter is applied at element creation and each time an element is updated. At bin rule creation, the user can also choose to apply the bin rule to existing elements. The filter condition can be defined by applying a filter and then saving it as a bin rule. The filter condition can include all the same possibilities as the normal filters.

71 Date : 15-mai-09 Page: 71 File: Post process The user can now set a post process for all elements on a bin. The post process is applied to all elements falling into the bin, whether they have been dropped manually or because of a bin rule. Post process options depend on the type of element: Assets/clips: o o o protect send to backup to near line Playlist: o send consolidated playlist to Timeline:

72 Date : 15-mai-09 Page: 72 File: o no post process for timelines Ordering of elements in bins There is now the possibility to order elements in a bin by drag & drop. The bin must be sorted on the position column Publish bins When a bin is published, all the elements in the bin are published. Any element put in the bin afterwards will be automatically published as well. When a bin is unpublished, only the bin is unpublished, not its clips. 5.4 Advanced Filters Introduction The IP Director version 5 will offer more and more possibilities in terms of metadata, it becomes mandatory to have powerfull search tools to retrieve the elements as quickly as possible. In terms of filters, the main improvements of version 5 are : - free text search improved with wild cards and the possibility to define AND and OR operators between words. - the possibility to search on individual metadata (even the ones coming from metadata profiles) - the possibility to search on individual columns, the search is done in the column header itself, it just take one additional line in the interface of the Database explorer. Doing so we free all the space the different filters took above the list in previous IP Director version. - the possibility to save filters in the database explorer and apply them - the possibility to combine the free text search with a selection in the XT tree and with filters applied on individual columns Quick search toolbar The quick text search and quick TC search are directly available from the top of the DB Explorer grid. They are always visible so there is no need to activate the filters to use the quick text or quick TC search.

73 Date : 15-mai-09 Page: 73 File: Quick text search The quick text search works on a full text search engine. The quick text search engine has 3 elements (from left to right) : - a combo box to enter the text string, the combo remembers the last 10 strings entered. - a help button which provide explanations on how to use the free text search - a de-apply button which de-applies the text search from the applied filters Rules for the full text search field : Yellow card : search for whole word yellow "logical and" card, even if in two different fields (columns) (ex: yellow in name, card in keywords). Equivalent to the following condition : Yellow AND card. (i.e : Clip name = The Yellow Man, clip keywords : Red Card ). The element must be found in the result as it has yellow and card in 2 different fields) Yellow card : search for yellow "logical or" card, even if in two different fields (ex: yellow in keyword, card in name). Equivalent to the following condition Yellow OR card. yellow card : Searches for exact matches of "yellow card". Within quotes, every characters are considered as charaters and not operators or wildcards. Equivalent to the condition : yellow card card* : search for card at the beginning of a word. Equivalent to the condition : card *

74 Date : 15-mai-09 Page: 74 File: *card* : Search for all words including card. Equivalent to the condition * card * Example : if the operator types : hello world toto* tutu it is equivalent to the condition hello world OR ( toto * AND tutu ) For all above rules, the search is done within a field considering each word separately, the following rule only applies considering the whole field =card : search for a whole field matching card. So for example, if a field contains yellow card, the =card condition won t return any result Quick TC search The quick TC search allows the user to search for clips including the TC entered in the quick TC search control. The user can enter a TC or a TC + date. When in the log plugin, the quick TC search performs a search within a range (+- 10s by default). The quick TC Search is not displayed by default but can be displayed by clicking arrow on the icon and selecting Display timecode search from the menu Filter tool bar When clicking on the icon, the header of the columns in the database explorer changes to the following view in order to allow searching on individual columns. The type of search which can be performed in each column depends on the type of the column. The different possibilities are : - free text search (columns like name, description, etc )

75 Date : 15-mai-09 Page: 75 File: The possibilies are the same as the ones available in the free text search in the tool bar. See paragraph above for more information. - keywords (keywords and participant columns). See below for more information. - predefined values (combo box style) (columns like type, level, etc ) - date (columns like creation date, etc ) When clicking in the date column, the following window is displayed allowing to search based on date : The window includes on the second line from left to right : - a calendar - the predefined last X values (last hour, today, last 2 days, etc) - the logical operators (AND, OR, FROM TO) - timecode (columns like T/C IN, T/C OUT, etc )

76 Date : 15-mai-09 Page: 76 File: - numeric value - send to status (Status column) The send to filter will be improved as well, it will be possible to search for clips sent to a specific target, or clips not sent to any target. There is also a tab for near line directories The operator just have to tick the check box in the cell corresponding to its search. Multiple cells can be selected at the same time. - Recorder (Source name column).

77 Date : 15-mai-09 Page: 77 File: The operator can make a search on assets (clips) created on specific recorders. A window will appear with the XT tree and their recorders. The operator just have to select the recorders he wants. - clip element type (Clip Elements column) The operator will also have the possibility to search for assets which have or don t have asset items. Refine search result by combining searches in different columns. It is possible to define search criteria in different columns. A logical AND will then be applied between the different filters. This will allow restricting the result of the search. The filters applied can be reset by clicking on the icon. Limitation : With this method based on column filters, it will only be possible to search on visible columns Searches based on keywords In previous IP Director releases, to search on keywords, the operator had to open either a keyword grid or a dictionary. This method will still be available in version 5, but we will add the possibility to select keywords from one single window. In this window, the operator can select keywords from keyword grid, dictionaries and from the keyword list. Logical operators AND, OR, NOT can be used in the search to add more possibilies.

78 Date : 15-mai-09 Page: 78 File: When the operator clicks on the keyword grid combo box (in the text), the keyword grid combo box background is highlighted and the last keyword grid selected is automatically displayed in the keyword zone. The combo box remembers the last 20 keyword grids opened. The operator can open another keyword grid using the open keyword grid button located on the right of the combo box. When the operator clicks on the dictionary combo box (in the text), the dictionary combo box background is highlighted and the last dictionary selected is automatically displayed in the keyword zone. The tree should be displayed the same way as it was the last time. The combo box remembers the last 20 dictionaries opened. The operator can open another dictionary using the open keyword grid button located on the right of the combo box. When the operator clicks on the keyword list text box : - the keyword list is displayed in the keyword zone (ordered alphabetically) - the keyword which is alphabetically the closest to the string entered in the text box is selected. If no string entered, the first one is selected.

79 Date : 15-mai-09 Page: 79 File: Saved filters It will be possible to save filters and apply them at a later time inside the database explorer. The interactivity will be slightly different than in version 4 : 1. Define the filter in the database explorer (selection in the XT tree combined with a free text search and maybe a column filter), then click on the arrow near the magnify lens icon. 2. The filter menu is displayed 3. Select Save filter. 4. Give it a name and press OK. 5. The new filter will be displayed in the saved filter list below the tree of the database explorer. This filter can then be applied later on. Same interactivity as in version 4 (playlist editor saved filters section). 6 Miscelleanous 6.1 IP Logger / Keyword grids Features Protect Media Improvements 1. Possibility to create several Protect Media on one recorder: there is a new option in the log contextual menu that allows the operator to protect selected logs only.

80 Date : 15-mai-09 Page: 80 File: 2. Possibility to choose on which relevant recorder to create a Protect Media (Protect All Media and Protect Selected Logs options) 3. View protect Media coverage: this is a new screen that shows the Protect Media coverage for all the recorders.

81 Date : 15-mai-09 Page: 81 File: 4. The operator can define a prefix to be applied to his protect media in the settings. This setting is a user setting. By default, the prefix is PM T/C Offset management 3 different types of T/C offsets 1. at logsheet or clips import: the clips and the logsheet have been done on two different setups with a T/C offset between the two. When the logsheet and the clips a re-united on the same setup, the user can apply an offset on all the logs to synchronise the logsheet and the clips. 2. automatic log export: when defining a directory for automatic log export in the remote installer, an offset can be specified. This could be, for example that the two setups are in different time zones. 3. delay at log entry: if the operator is slow or he is logging on a delayed feed, he can define to apply an offset at log entry. This offset is defined in a user setting. The offset is applied to the T/C when the user creates the log Activate/De Activate logsheets A logsheet can be de-activated. When a logsheet is de-activated, its automatic associations are not re-calculated. It is, however, possible to browse all its logs as usual. This operation is for saving processor time on setups with many logsheet. Deactivating logsheets when they are completed will improve the performance of the system Thumbnails on logs A thumbnail is automatically generated on the preview recorder. If needed, the operator can manually re-generate the thumbnail on a relevant recorder of his choice.

82 Date : 15-mai-09 Page: 82 File: There is also an option to re-generate all thumbnails for a logsheet Automatic import/export IP Director setups can be configured to automatically export logs in real time to 3 rd parties or other IP Director setups. Combined with the possibility to automatically import logs in real time, this combination means two IP Director setups on two different databases can exchange log information in real time. Any update made on one setup will be propagated to the other setup. The diagram above shows an example of this type of log exchange workflow, as used in Beijing by the BBC: 1. BOB exports the logs the BBC Beijing setup 2. BBC Beijing exports its logs to the BBC London setup 3. BBC London do their own logging and export the logs back to BBC Beijing

83 Date : 15-mai-09 Page: 83 File: Colours on logs The operator can choose in the new/edit log window from five different colours to highlight each log. The log will then be highlighted in the selected colour in the IP Logger grid and the DB Explorer grid. The operator can search on the colours in the DB Explorer Colours on keyword grids The operator can now set custom background and foreground colours for keywords in a keyword grid. The user can select multiple keywords and apply the colour settings to the whole selection at once.

84 Date : 15-mai-09 Page: 84 File: Limitations 1. No T/C offset at automatic Log Import: since we can import logs coming from different sources and the fact that it is impossible to detect where the log is coming from, we cannot apply a Timecode offset at log import. 2. View Protect Media coverage window: this is a static window, there is no possibility to create/erase a protect media from this window. 6.2 Proxy management Introduction The IP Director version 5 will be able to manage XL[2] based proxy. Once the proxy is configured in the remote installer, everything will be completely transparent for the operator. He will browse on the proxy and the operations will be passed on the HiRes Features Configuration The configuration of the proxy XT[2] is done in the remote installer. The XLs must be on a separate SDTI network than the HiRes XTs.

85 Date : 15-mai-09 Page: 85 File: In the XT networks tab, the user must define HiRes and LoRes networks. Once this is done, the administrator can associate LoRes channels to the corresponding HiRes channels in the Lo-Res management tab Hi Lo in the channel explorer In the channel explorer, a user with Hi-Lo visibility can see the Hi-Lo associations: - in the tree view, the LoRes recorder appears under the HiRes recorder it is associated to - in the flat views, the LoRes recorder appears on the same line as the HiRes recorder it is associated to Hi Lo management Hi-Lo associations are managed through the new clip entity (see Near Line mgt for an explanation of the new clip logical entity). Every time a clip is created on the Hi or the Lo res, the corresponding clip is automatically created on the associated channel. The two XT clips will be in the same clip entity. If the clip is deleted/updated, both XT clips are deleted/updated.

86 Date : 15-mai-09 Page: 86 File: If one of the two clips is updated, the whole clip entity is updated, meaning both XT clips are updated. Depending on user rights, if one the XT clips is deleted, the whole entity is deleted or only the clip. For example, if a LoRes browser deletes a LoRes clip, it is the whole clip that is deleted. 6.3 T/C and date management Introduction Multicam 9 (and higher) manages 2 timecode tables per recorder/clip : LTC and USER (not only one timecode table per server) IP Director 5 will take these modifications into account and will provide the two timecodes in its interfaces Features Timecode tables and date integration in the timecode control IP Director uses a new timecode control displaying the timecode, the date and/or the timecode table it comes from. You will be able to specify the date associated to the timecode where you want to go. You are also able to specify the timecode table you want to use as reference.

87 Date : 15-mai-09 Page: 87 File: LTC timecode is displayed in white USER timecode is displayed in yellow The control can be configured to show/hide the date or the TC table Primary TC table management When the timecode table is changed on the recorder panel, it automatically becomes the primary timecode of the controlled recorder. More generally a TC Table change is reflected in the Multicam configuration (for trains and clips) Timecode searches The DB explorer searches have been extended to permit searches on Timecode, Date in the LTC table, the USER table or both. You can also search on the primary timecode. 6.4 Licensing Options in XSecure Option Name Description

88 Date : 15-mai-09 Page: 88 File: IP Engine This option includes : - the Database engine of the IP Director (don t be confused with the SQL server licence and workstation licence which is separated) - user s right manager (user manager) - remote installer - services (IP Routing, Synchro DB, IP Scheduler, XML engine, ) One and only one IP Engine license is requested per setup. IP Access Give an access to all main applications of the IP Director (typically the one available in the old base package) : - Database explorer - Control panel (with clip-list, gang management, etc) - Recorder panel - Channel explorer - Ingest VTR panel One IP Access license is requested per workstation. IP Media Viewer Allow using the software player for gige browsing and file preview in the IP Director interface. This license is requested on all workstations using the software player and comes in addition of the IP Access licence. IP Playlist Licence allowing the Access to the IP Playlist application with advanced playlist functions. This license is requested on all workstations using the IP Playlist module and comes in addition of the IP Access licence. IP Edit License allowing the access to the IP Edit application.

89 Date : 15-mai-09 Page: 89 File: This license is requested on all workstations using the IP Edit module and comes in addition of the IP Access licence. IP Ingest Scheduler License allowing the access to the IP Ingest Scheduler application. This license is requested on all workstations using the IP Ingest Scheduler module and comes in addition of the IP Access licence. IP Logger License allowing the access to the IP Logger application. This license is requested on all workstations using the IP Logger module and comes in addition of the IP Access licence Remarks 1. If some IP Director are to be used for connecting purposes only (RS Connections to XT servers, routing, synchro DB or IP Scheduler management, no IP Director interfaces used), only the hardware is quoted (4800 ), no additional licence must be added. 2. There is no IP Browser licence anymore, it is included in the IP Access licence. 3. IP Engine licence has to be installed on the database server. Upgrading the licences from a previous version of IP Director : In case your setup does not have a separate database server, the IP Director will consider the base package licence on the workstation where the database is run. If the base package is installed on this workstation, the system will not need an IP Engine licence to start. In case your setup does have a separate database server, the IP Director will search for an IP Engine code installed on your database server to run. If the IP Engine code is not installed, the system will not start. 6.5 Settings Introduction new v5.6

90 Date : 15-mai-09 Page: 90 File: Previous Ip Director settings window was organised in tabs and the way the settings were organised amongst the tabs was not correct. It was then rather difficult to quickly find a setting when we don t know in which tab it is. There was a need to add some more settings and macro functions (related to the playlist and the IP Edit) and the GPI configuration must be completely reviewed. It was then a good opportunity to review the way settings are organised and provide a more user friendly interface to the operator Overall philosophy The window is now organized in 3 different zones: - A title zone (on top): indicating the category and sub-category selected in the tree - The category tree (on left): with all the settings categories and sub categories - The settings zone (on right): with all the settings related to the selected category or sub category in the tree.

91 Date : 15-mai-09 Page: 91 File: Settings category General Display XT Structure Display File Directory Structure Select copy/move behaviour Action taken for idle channels Key default output colour Select the default output colour on the key channel when a clip with no associated key is loaded on the fill channel Language Auto Name Clip new v5.6 Clip Name - Format String This string is used to auto name clips when the a ingest/new clip window is not display Clip Name Prefix - Format String This string is used to when the ingest/new clip window is not display. It acts as a prefix. Clip Name - Counter Value This counter allows can be used in the auto name and prefix values. File new v5.6 Clip File Name - Format String Format string to use when creating clip files (backup, send to ). Stream File Name - Format String Format string to use when creating stream files. Playlist File Name - Format String Format string to use when creating consolidated playlists files.

92 Date : 15-mai-09 Page: 92 File: Image File Name - Format String Format string to use when capturing image in control panel Clip General Open save clip window Guardbands Default clip duration Create clips on all sync recorders Automatic clip creation on logs Default clip ID display mode new v5.6 The clip ID mode defines what is the main ID used by the operator in the interface Take Default Effect type Default effect duration Playlist General Insert mode in playlist Default preroll duration Start on time security warning Default transition Default speed for elements Default A/V effect parameters Default still and start mode Audio swap Predefined audio swap configurations

93 Date : 15-mai-09 Page: 93 File: Macro commands new v5.6 Tags in the playlist are heavily used in production playlist and in previous IPDirector releases, the interactivity defined to insert tags on a playlist element is not efficient and rather complex. The operator needs a quick and efficient way to insert a tag at a certain position inside a playlist element. The idea is to provide shortcuts for predefined tag configurations. The macro action includes the following values: - GPI OUT - Mute ON - Mute OFF - Hide ON - Hide OFF - Audio Swap : this item should not be present if no audio swap configuration is defined in the audio swap category. - Effect - Still / Start mode - Default transition

94 Date : 15-mai-09 Page: 94 File: The controls in the window : - 10 macro commands can be configured (from 0 to 9). - For each macro command, the user specifies which action (and its parameters) is related to the corresponding macro

95 Date : 15-mai-09 Page: 95 File: command. The parameters can be displayed over 2 lines or over 1 line (vertically centered in this case). Auxiliary track OSD new v5.6 OSD settings give the Ip Director the Airbox OSD style because most of our customers are accustomed to them OSD Mode Clip Information Display current on-air timecode Display remaining time Control Panel Speeds Play clips automatically Last clips created list Ingest scheduler new v5.6 General Ingest Information display Select which information to display in the ingest blocks. Warning message when stopping an ingest Warning message is shown each time the user stops an ingest. Auto name assets If checked, the new ingest window is NOT displayed when an ingest is created and the asset will automatically be named using the format string defined in the clip creation tab. Remaining Capacity Display remaining capacity as Remaining capacity calculation

96 Date : 15-mai-09 Page: 96 File: Define if you would like to consider the scheduled ingests in the remaining capacity calculation or not. Capacity warning threshold Define the remaining capacity threshold below which the remaining capacity information should turn red in the interface. Advanced Track size Define what should be the height (in pixels) of the tracks displayed in the interface. Minimum mouse move Define the minimum mouse move threshold below which the drag and drop operations are not considered Ip Edit General Clip Information display Transition effects Volume automation range Control track initial timecode Macro command new v5.6 Tags in the timeline are heavily used and today the interactivity defined to insert them on a timeline element is not efficient and rather complex. The idea is to provide shortcuts for predefined tag configurations. The macro action includes the following values: - Effects - GPI - Replace settings Replace

97 Date : 15-mai-09 Page: 97 File: Pre-Roll GPI s Delay compensation Audio group track mute new v5.6 Selected audio group tracks that will be muted during the replace process (between boundary marks) Audio swap input matrix Ip Logger Apply a T/C Offset new v5.6 Enter the offset (in ms) between the actual timecode of the log and the timecode at which the log is created. Protect Media Prefix new v5.6 Enter the string to use for prefixing the name of a Protect Media. A space defined as the last character of the prefix will be taken into account. Warning message Input GPI s new v5.6 Define input GPI actions, channels trigger mode and delay Output GPI s new v5.6 Define output GPI advance Image Capture Default path for images Capture image on all ganged recorders

98 Date : 15-mai-09 Page: 98 File: 7 Technical improvements 7.1 Remote installer Features Read Only mode There is a new read only mode that allows an administrator to view the configuration and monitor all the services. The advantage is that multiple remote installers can be open in read only mode. Switching between read-only and write mode requires to logout and log in again Service monitoring The IP Director services can be monitored from the remote installer. Any service from any machine can be monitored from one remote installer. The monitoring interface is new. It is common to all the services. Amongst other usefull information, it is possible to see which machine manages which XT or directory. The monitoring shows important information from the IPD services in one screen

99 Date : 15-mai-09 Page: 99 File: XT Networks This tab allows the user to divide his XTs in logical XT networks. A network can either be HiRes or LoRes. In V5, it will only be possible to define one LoRes network and one HiRes network Thumbnails The operator can define up to four directories for four different types of grab: - thumbnails for logs - thumbnails for clips - thumbnails for playlist elements - image grab from the remote installer Targets configuration All targets configuration has been grouped under one Targets tab. This tab has a view for each target type and an "all" view showing all targets in the workgroup.

100 Date : 15-mai-09 Page: 100 File: Send to targets are defined into two main categories: - send A/V material: for these targets, the A/V material is physically copied from the XT server onto an IT storage (file on shared drive), an Avid TM, a Final Cup Pro, a Clean Edit (with reference in the CE DB) or an XT on another network. - Reference A/V material: for this target, an xml file is place on a shared drive. This xml file references a clip or a playlist for direct access on the XT server. Currently, this is use to reference to a CE, but it could reference clips to another application. Targets supports Avid MXF OPAtom and AVI formats

101 Date : 15-mai-09 Page: 101 File: IP Logger Export The operator can define the directories to which logs will be exported in real time. If the operator ticks the "automatically export all logsheet to 3 rd party directories", all logsheet are exported. If not, the operator creating the logsheet can choose to export or not. If the two setups are not running on the same T/C (not in the same time zone for example), the logs can be sent with a T/C offset. As well as exporting logs, the IP director can also be set to import logs from another setup (through the IP Scheduler). This allows two setups to synchronise their logsheets, with some logging allowed on both sides. The image below shows an example of log export/import workflow:

102 Date : 15-mai-09 Page: 102 File: BOB Bejing 2.1 BOB to BBC Bejing 2.2 BBC Bejing to BBC London BBC Ops Bejing BBC London 2.3 BBC London to BBC Bejing Near Line configuration Near line configuration is very quick and easy. In the Near Line tab, just enter the list of directories that need to be managed by the IP director. The IP Director will manage all sub-directories of a near line directory. The near line directory will appear under the file root and is identified by the name given to it in the remote installer.

103 Date : 15-mai-09 Page: 103 File: The nearline configuration includes the storage type (Windows or Other), the user and password used by the services to manage the nearline Hi Lo configuration XT[2] Lores is configured in two stages. 1. In the XT Networks tab, define a HiRes logical network and a LoRes logical network. Place the relevant machines in each network (including XFiles). 2. In the LoRes tab, drag & drop the LoRes recorders on the HiRes recorders that they are linked to. Before configuring the LoRes, all the machines and services must be started in order to detect all the machines, then stopped for the configuration process Database configuration 1. The remote installer detects automatically if the database has a wrong version number 2. The remote installer can update a database in one step applying all the missing update script in the same batch.

104 Date : 15-mai-09 Page: 104 File: Miscellanious 1. The master synchro DB and IP Scheduler appear in dark green. 2. The local computer is identified by a house on the right. 3. A description can be added to the IPD computername to identify the station role more easily 4. The management of the XFile jobs has been moved from the IP Scheduler to the synchro DB Limitations 1. There is still only one opening of the Remote Installer in Edit mode at a time. 7.2 Serial Link Redundancy Previous IP Director versions it was not possible to manage the redundancy of the connections between the XNet and the IP Director network : it was not possible to connect 2 IP Director workstations on the same XT servers. This is now addressed in IP Director version 5.