SGI Media Server™ for Broadcast User’s Guide Version VST 2.2.
CONTRIBUTORS Written by Ken Jones Illustrated by Chris Wengelski and Chrystie Danzer Production by Karen Jacobson Engineering contributions by Peter Allen, Achuith Bhandarkar, Sebastian Brings, Philippe Churlet, Sandeep Gupte, Ray Festa, Ardene Kannely, Marlon Leon, Jim Montine, Mark Negovan, Matthew Rehrer, Chris Shapter, Richard Stein, and Parkson Wong Other contributions by Danielle McGurk and Brian Payton COPYRIGHT © 2003–2005 Silicon Graphics, Inc.
New Features in This Guide Changes to this guide include the following: • Added support for SGI InfiniteStorage RM610 disk systems to the following: - Section “Other Publications” on page xxiii - Chapter 1, “Overview of the SGI Media Server” - Chapter 2, “System Setup” 007-4403-003 • Added play and record support for the DVCAM and DV (16-bit/48 Khz only) compression types throughout the guide.
Record of Revision Version Description 001 December 2003 Original publication. 007-4403-003 002 August 2004 Updated for the release of VST 2.2. 003 January 2005 Updated for the release of VST 2.2.1.
Contents Contents Figures . 1. 007-4403-003 . . . . . . . . . . . . . . . . . . . . . . . . . xv Tables . . . . . . . . . . What This Manual Contains . . . . Who Should Read This Document . . Related Documentation . . . . . Release Notes . . . . . . . Online VST Man Pages . . . . Program/Utility Files . . . Command/Control Summaries Other Publications . . . . . Obtaining Publications . . . . . Conventions . . . . . . . . Reader Comments . . . . . . . . . . . . . . . . . . . .
Contents Hardware Overview . . . The System Unit . . . Disk Storage . . . . External Devices . . . Internal Devices . . . Video Device Control . . Supported SMPTE Standards . 2. viii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Setup . . . . . . . . . . . . . . . . . . . Power Requirements . . . . . . . . . . . . . . . . .
Contents 3. 007-4403-003 System Configuration . . . . . . . . . . . . Configuration Files . . . . . . . . . . . . . Configuring Device Interfaces . . . . . . . . . . Configuring Audio and Video Devices in Your System . . Setting Device Parameters . . . . . . . . . . Configuring System Defaults. . . . . . . . . . . Configuring Video Compression . . . . . . . . . Configuring Audio Support . . . . . . . . . . . Input . . . . . . . . . . . . . . . . Output . . . . . . . . . . . . . . . .
Contents x Configuring the SGI Media Server to Control Other Devices . . protocol . . . . . . . . . . . . . . . . connection . . . . . . . . . . . . . . . serial_port . . . . . . . . . . . . . . . speed . . . . . . . . . . . . . . . . . parity . . . . . . . . . . . . . . . . Configuring the VTR Daemon (vtrd) . . . . . . . . Mapping Physical Ports to Logical Port Names. . . . . . Configuring for 625/50 Systems . . . . . . . . . . Tuning the SGI Media Server (Setting the Maximum DMA Size) . . . . . . . . .
Contents Adding Clips to the SGI Media Server . . . Transferring Clips to the SGI Media Server Proxy Transfers . . . . . . . . MPEG-2 Index File Transfer . . . . . Clip Alignment . . . . . . . . Degree of Alignment . . . . . Minor Alignment. . . . . . . Major Alignment . . . . . . . Notifying the SGI Media Server . . . . Transferring a Clip Segment . . . . . . Overriding Clip Segment Transfer . . . . Removing Clips . . . . . . . . . MXF Record and Playout . . . . . . . . . . . . . . . . . . . . . . . . .
Contents xii Configuring the SGI Media Server for Control by VDCP . . . . . . . . . . . VDCP Commands . . . . . . . . . . . . . . . . . . . . . Using the Harris Automation ADC100 Automation Controller with the SGI Media Server Using House Timecode Readers with the SGI Media Server . . . . . . . . . . RS-232 and RS-422 Cabling . . . . . . . . . . . . . . . . . . . . 93 . 94 . 96 . 98 . 99 8. Troubleshooting . . . . . . . 625/50 Clips Do Not Play . . . . . Adding a Clip Takes Excessively Long .
Contents Monitoring Unit State . . . . . . Monitoring the System . . . . . Status . . . . . . . . . Monitoring. . . . . . . . Statistics . . . . . . . . STLS—List Statistics . . . . STST—Statistics on Statistics . Error Reporting . . . . . . MVCP Command Syntax Errors Controller Errors . . . . . Unit Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents The Media Contro Panel . . . . . . . . Starting the Media Control Panel . . . . Determining Available Ports . . . . . . Using Telnet to Determine Available Ports Using vtrstat to Determine Units in Use Using Telnet to Determine Units in Use . Sample Startups of the Media Control Panel Operating the Media Control Panel . . . . Playing or Recording an Existing Clip . . . Creating a New Clip . . . . . . . . Changing Cue Points and Edit Points . . . Controlling a Video Deck . . . . . . .
Figures Figures Figure 1-1 Figure 1-2 Figure 1-3 Figure 1-4 Figure 1-5 Figure 1-6 Figure 2-1 Figure 2-2 Figure 6-1 Figure 6-2 Figure 6-3 Figure 6-4 Figure 7-1 Figure A-1 Figure A-2 Figure A-3 Figure A-4 Figure A-5 Figure A-6 Figure A-7 Figure A-8 Figure A-9 Figure A-10 Figure A-11 007-4403-003 Functional Overview . . . . . . . . . . Video Server Technology Software Components . . One Logical Unit with One Control Connection . . One Logical Unit with Two Control Connections . .
Tables Tables Table 1-1 Table 1-2 Table 1-3 Table 1-4 Table 2-1 Table 2-2 Table 2-3 Table 2-4 Table 2-5 Table 2-6 Table 2-7 Table 2-8 Table 2-9 Table 2-10 Table 2-11 Table 2-12 Table 2-13 Table 2-14 Table 2-15 Table 3-1 Table 3-2 Table 3-3 Table 3-4 Table 3-5 Table 3-6 007-4403-003 Support for File Formats and Compression Types . . . . . . Hardware Components of the SGI Media Server . . . . . . Comparison of SGI Media Server Models . . . . . . . . SMPTE Standards Supported by the SGI Media Server . . .
Tables Table 4-1 Table 4-2 Table 6-1 Table 7-1 Table 7-2 Table 7-3 Table 7-4 Table 7-5 Table 7-6 Table 9-1 Table 10-1 Table 10-2 Table A-1 Table A-2 Table A-3 xviii Logging Levels . . . . . . . . . . . . . . . rotatelogs Command Options . . . . . . . . . MVCP Virtual Clip Commands . . . . . . . . . . VDCP Commands Supported by the SGI Media Server . . . Harris Automation Device Parameters . . . . . . . . DB-9 Pin Assignments . . . . . . . . . . . . . Configuration for a Mini-Din to DB-9 Adapter . . . . .
About This Manual The SGI Media Server for Broadcast is a completely integrated solution for serving video, audio, and data that is based on open architecture, data networking, and storage technology. The core of the multichannel SGI Media Server is the SGI Video Server Technology (VST) software. VST supports a variety of video file formats and compression types. This manual describes how to use the SGI Media Server to play and record digital media.
About This Manual • Chapter 7, “Configuring and Using External Devices,” describes how to handle the external devices connected to the SGI Media Server. • Chapter 8, “Troubleshooting,” describes some likely problem scenarios you might experience while operating your SGI Media Server and what to do. • Chapter 9, “Introduction to MVCP,” describes some common tasks you routinely perform using MVCP commands.
About This Manual Release Notes The VST release notes provide information about the release that is not included in this document. Included are known issues with installation and setup, product issues, and documentation errata.
About This Manual vtrstat(1) Describes how to get VST status. vtrclip(1) Describes clip management. vvtr(1) Describes the VST server. vtrd(1) Describes the VST daemon. vtrvfutil(1) Describes the VST vframe clip utility. vtrdircopy(1) Describes the copy-directory daemon for VST. vtrftp(1) Describes the command-line FTP client for VST. vtrftpd(1) Describes the real-time-enabled FTP daemon for VST. vtrmpegutil(1) Describes the MPEG-2 parsing utility for VST.
About This Manual Other Publications Refer to the following publications for additional information: • IRIX Admin: Software Installation and Licensing for information about installing software that runs under IRIX, the SGI implementation of the UNIX operating system • IRIX Admin: System Configuration and Operation for information about IRIX system administration tasks • IRIX Admin: Disks and Filesystems for information about general filesystem concepts and system administration procedures for SCSI dis
About This Manual Conventions The following conventions are used throughout this publication: Convention Meaning command This fixed-space font denotes literal items such as commands, files, routines, path names, signals, messages, and programming language structures. variable Italic typeface denotes variable entries and words or concepts being defined. user input This bold, fixed-space font denotes literal items that the user enters in interactive sessions.
About This Manual • Use the Feedback option on the Technical Publications Library webpage: http://docs.sgi.com • Contact your customer service representative and ask that an incident be filed in the SGI incident tracking system. • Send mail to the following address: Technical Publications SGI 1500 Crittenden Lane, M/S 535 Mountain View, CA 94043-1351 SGI values your comments and will respond to them promptly.
Chapter 1 1. Overview of the SGI Media Server This chapter describes the SGI Media Server, which provides real-time, frame-accurate recording and playback of broadcast-quality digital media data. The SGI Media Server manages video as data, distributing the files over the existing LAN/WAN infrastructure—whether 100 Base-TX, Gigabit Ethernet, or enhanced video networks— within a facility or between facilities.
1: Overview of the SGI Media Server This functionality is shown in Figure 1-1.
Software Overview Software Overview The SGI Media Server software provides scalability and maximum flexibility. The software includes the following: • SGI Video Server Technology (VST), the core software of the SGI Media Server. VST provides real-time, frame-accurate recording and playback of broadcast-quality digital media. • Control interface modules, which provide device-dependent code. For example, there is a control interface module that contains the code that is specific to VDCP controllers.
1: Overview of the SGI Media Server Control workstation Silic onG raph Automation controller ics s Graphic Silicon ol ntr Co face r inte ules d mo P) P/I TC ( 2) CP - 4 2 2) MV (RS S-42 P (R C ) VD y P2 P/IP C n So P (T C MV l ica Logits un r ) rve ST Se gy (V o e olo d i V hn c Te M ia ed s rt po e rag Sto ice v de ace rf inte ules d o m at rm Fo face r inte ules d mo dia Me ce i v de ace rf inte ules d mo Clip cache Playback/recording devices Figure 1-2 4 Video Server Technology Softw
Software Overview Clip Cache Digital media data that the SGI Media Server processes for playout and recording is stored in one or more clip caches. Each audio/video segment that is stored in a clip cache is called a clip.
1: Overview of the SGI Media Server The following control interface modules are provided: • The Video Disk Communications Protocol (VDCP). This control protocol provides control of VST over RS-422. The VDCP interface module supports back-to-back play and record (subject to restrictions imposed by the video I/O port capabilities). • The Sony RS-422 VTR (also called, 9-pin or P2) protocol.
Software Overview Compression Formats The MPEG-2, DVCPRO 25, DVCPRO 50, DVCAM, and DV (16-bit/48 Khz only) compression algorithms can be used to provide a compressed video stream, which can be stored in a file. This file format is useful for transporting video across data networks. In addition to traditional TCP/IP data networks, this data can also be transmitted across coaxial video networks as data to and from VTRs, nonlinear editors, and servers.
1: Overview of the SGI Media Server Table 1-1 summarizes the support for the various file formats and compression types.
Software Overview Logical Playback and Record Units Logical units enable media ports to play and record clips. Each SGI Media Server unit can be thought of as a logical VTR transport that is capable of loading, cueing, playing, and recording clips using a specific media port. Logical units are created automatically by VST when the SGI Media Server control GUI or an automation controller is used.
1: Overview of the SGI Media Server A single unit can also be controlled by multiple control ports. For example, two tightly integrated applications might control a single unit, where each application would have its own control port. This is shown in Figure 1-4.
Software Overview A media port can be controlled by multiple logical units. For example, an application with one control connection and two units could be cueing one clip while playing out another, enabling back-to-back playout of clips when allowed by the media format. This example is shown in Figure 1-5.
1: Overview of the SGI Media Server Hardware Overview This book describes the SGI Media Server Models 325, 345, 365, and 385. Their hardware configuration consists of the components shown in Table 1-2.
Hardware Overview Note: In many respects, the audio/video cards listed in Table 1-2 are functionally equivalent. Section “Internal Devices” on page 17 describe their differences. Subsequent references to PCI-VIDAUD-MSB-B cards in this manual also apply to all of the cards unless otherwise noted. A typical hardware configuration is shown in Figure 1-6.
1: Overview of the SGI Media Server Automation controller SGI Media Server CHANNEL 2 CHANNEL 1 CHANNEL 2 CHANNEL 1 OUTPUT OUTPUT GOOD GOOD FAULT FAULT XIO 10 48VDC 12VDC Video deck Serial ports Video in Video out Ethernet port Live feed rk two Ne Broadcast system Video deck P/I T 0 et 1 P Silico FT se Ba ern Eth TC 0 /10 nGra phics Graphics Silicon P Workstation CHANNEL 2 CHANNEL 1 CHANNEL 2 CHANNEL 1 OUTPUT GOOD OUTPUT GOOD FAULT FAULT XIO 10 48VDC 12VDC SGI Med
Hardware Overview The System Unit The Origin 350 server provides massive processing, storage, and throughput capabilities to satisfy large production requirements. They are built from a scalable node architecture, enabling small configurations that can be incrementally upgraded to the larger configurations. Each Origin server can be configured as a single module or as multiple modules with a single system image.
1: Overview of the SGI Media Server 1. The base compute module has four internal PCI slots; however, one PCI slot of the base compute module is required for the IO9 base I/O card. Therefore, the number of available slots in the base compute module is reduced by one. Disk Storage The SGI Media Server disk storage holds the XFS real-time filesystems that contain the video content stored in the clip cache.
Hardware Overview – Miranda TCP-101i Time Code Processor and Little Red LTC Reader – Horita Master Timecode Generator and PR-232 SMPTE Time Code Translator For more information about installing these devices for use with the SGI Media Server, see Chapter 7, “Configuring and Using External Devices.” For a complete list of external devices that interface with the SGI Media Server, see the release notes.
1: Overview of the SGI Media Server Supported SMPTE Standards The SGI Media Server provides integrated support for the following SMPTE standards. The SGI Media Server is designed to interact with signal formats and media file formats that follow the SMPTE standards and constraints.
Chapter 2 2. System Setup This chapter describes the power, rack space, PCI, and video/audio connections required to install and set up an SGI Media Server.
2: System Setup Power Requirements Power requirements for the Origin 350 base platform supporting the SGI Media Server are shown in Table 2-1. It includes the power requirements for the 2U-high PCI-X expansion module also. Table 2-1 Power Requirements for the SGI Media Server Base Unit Specification Value Input volts 110 or 220 volts, 20 amp universal auto-switching power supply Power bay output 640 watts DC (3.3/5/12v) Cooling N+1 redundant cooling Note: A power redundancy option is available.
Rack Space Requirements Table 2-3 shows the power and size specifications for external RAID storage systems. Table 2-3 Power and Size Specifications for the External RAID Storage System Specification Value Input Volts Dual internal rack power distribution to enclosures, single phase, 250 VAC (180 minimum, 257 maximum), 50/60 Hz, 16A (25A circuit breakers) Dimensions 13.34 cm x 44.45 cm x 50.0 cm (5.25” x 17.5” x 19.
2: System Setup Sample Space Requirements for Model 345 Table 2-5 shows the rack space requirements for a four-channel Model 345 with TP900 storage.
PCI Configuration Requirements Sample Space Requirements for Model 385 Table 2-7 shows the rack space requirements for an eight-channel Model 385 with TP9100 storage.
2: System Setup Table 2-8 Supported Bus Speeds for Optimal Add-On Cards (continued) Add-On Cards 33Mhz 66Mhz 1-Gigabit single-port FC HBA with PCI X X 2-Gigabit single-port FC HBA with PCI X X 2-Gigabit dual-port FC HBA with PCI or PCI-X X PCI-VIAUD-MSB-B card X Serial I/O card X 100Mhz X Cards that support only 33Mhz bus speed will cause the PCI bus to lock to 33Mhz. This can degrade performance of networking and storage cards that support 66Mhz bus speeds or higher.
PCI Configuration Requirements Note: SGI does not support configurations that share serial boards with Fibre Channel HBAs on the same bus. Recommended Card Layouts The tables in this section recommend card layouts for the SGI Media Server infrastructure. They represent only standard minimum and maximum configuration options. The following two conventions are used in the tables: • Optional slot layout possibilities are in parentheses.
2: System Setup A Four-Channel Model 345 System or a Six-Channel Model 365 System For both Model 345 and Model 365, Table 2-9 shows the internal PCI slot layout for the Origin 350 base compute module. The base compute module houses two video cards. For a four-channel Model 345 system, place the two additional video cards on bus 1 of the PCI expansion module (PX2U). For a six-channel Model 365 system, place the additional four video cards on bus 1 and bus 2 of the compute expansion module.
Video/Audio Connections PE Brick Layout for Origin 350 Systems (continued) Table 2-10 Bus Slot Recommended Card Layout for PE Brick Module (001p02) Xtalk Slot 5 2 PCI-VIDAUD-MSB-B card8 (Serial)1 12 2 6 1 Serial—best choice1 13 1 6 2 Serial—best choice1 13 2 1. See the introductory text for section “Recommended Card Layouts” on page 25 for conventions used in this table.
2: System Setup The card supports the following audio I/O types: • AES/EBU • Embedded • Analog The audio and video connections to the card are made through the rear panel of the SGI Media Server. The panel and connections are described in the following subsections. The MSB-REARPANEL-B Rear Panel The MSB-REARPANEL-B provides the physical audio and video connections to the SGI Media Server. A rackmounted unit supports up to two video/audio cards (channels) in the server.
Video/Audio Connections Figure 2-2 depicts the left-half, rear view and shows a single ACTIVE THRU SDI connector. As with the front of the panel, the rear halves are identical. ACTIVE THRU CABLE Figure 2-2 MSB-REARPANEL-B Left-Half Rear View Video Connections The MSB-REARPANEL provides SDI and GENLOCK/COMPOSITE video connectors. SDI Video Connectors Table 2-11 provides a description of each SDI video connector.
2: System Setup Note: All SDI video complies with SMPTE 259M specifications. Genlock/Composite Connectors Table 2-12 describes the GENLOCK/COMPOSITE connectors. Table 2-12 GENLOCK/COMPOSITE Connectors Connector Description IN This connector is the Genlock video input for the PCI-VIDAUD-MSB-B card. This composite analog signal should contain either NTSC or PAL Blackburst, generated by a standard video sync signal source. THRU This connector is an active loopthrough output of the Genlock input.
Video/Audio Connections Table 2-13 AES/EBU Audio Input Connectors Connector Description 3/4 This connector is an AES/EBU digital audio input for channels 3 and 4 of the PCI-VIDAUD-MSB-B card. The input accepts two discrete channels of digital audio conforming to the SMPTE 276M standard. 5/6 This connector is an AES/EBU digital audio input for channels 5 and 6 of the PCI-VIDAUD-MSB-B card. The input accepts two discrete channels of digital audio conforming to the SMPTE 276M standard.
2: System Setup ANALOG AUDIO Connectors Table 2-15 describes the analog audio connectors. Table 2-15 32 Analog Audio Connector Connector Description IN 1/L This female XLR connector is a balanced analog audio input for channel 1 or Left of the PCI-VIDAUD-MSB-B card. The connector accepts a single audio channel. IN 2/R/TC This female XLR connector is a balanced analog audio input for channel 2, Right, or the SMPTE timecode of the PCI-VIDAUD-MSB-B card. It accepts a single channel of audio.
Chapter 3 3. System Configuration This chapter describes how you configure the SGI Media Server for proper operation.
3: System Configuration Note: You can also use MVCP SET commands to alter control values but the changes will only persist until the next VST restart. In contrast, control values set in the configuration files persist from a VST start until changed by a SET command. Table 3-1 Configuration Files Configuration File Purpose /usr/vtr/config/control-in.conf Configures the server to be controlled by remote devices.
Configuration Files For a detailed discussion of the SGI Media Server controls and values applicable to each configuration file and device, see the vst-control(5) man page. The file formats and organization for the following files are described in the following sections of this chapter: • /usr/vtr/config/control-in.conf • /usr/vtr/config/control-out.conf • /usr/vtr/config/ports.conf Table 3-2 describes the various peer directories of /usr/vtr/config.
3: System Configuration Configuring Device Interfaces A device file contains variables called controls that map device register settings or establish settings for SGI Media Server interaction with peripheral control systems, such as the Harris Automation ADC100. The controls consist of name-value pairs. The device register settings establish specific behaviors, such as the compression format for video ingestion.
Configuring System Defaults • Detecting a vertical interval timecode (VITC) on line 14 • Processing the VITC value for each frame • Accepting analog audio input using the MSB-REARPANEL-B connected to a PCI-VIDAUD-MSB-B peripheral Configuring System Defaults You use VST controls in files in the /usr/vtr/config/system-defaults directory to specify default, systemwide behavior. For example, the file main might contain the following: vtr.main.
3: System Configuration Configuring Video Compression The PCI-VIDAUD-MSB-B multiformat codec (MFCODEC) devices support several file formats for video compression: DIF, SGI MPEG-2, SMPTE 360M (playout only), and MXF. The DIF video format supports DVCPRO 25, DVCPRO 50, DVCAM, and DV (16-bit/48 Khz audio only) fixed-sized compression. To enable MPEG-2 video compression, add the following line to the appropriate MFCODEC_n file: vtr.media.video.input.compression.
Configuring Video Compression Each GOP structure has a GOP period, which is the interval between two successive occurrences of the GOP structure, exclusive of the I-frame. Table 3-3 defines the GOP period for each supported GOP structure. Table 3-3 ! Supported GOP Structure and Period GOP Structure GOP Period I 1 IP 1 IPB 2 IPBB 3 Caution: Attempts to apply unsupported GOP structures may generate unpredictable results.
3: System Configuration For example, Table 3-4 defines examples of valid GOP sizes, their periods, and structures. Example GOP Size, Period, and Structure Table 3-4 Size Period Stored GOP Structure 1 1 I 15 1 IPPPPPPPPPPPPPP 6 3 IBBPBB 15 3 IBBPBBPBBPBBPBB To enable MPEG-2 video compression with the default I-frame compression and GOP size 1, add the following line to the appropriate MFCODEC_n file: vtr.media.video.input.compression.
Configuring Audio Support The following controls affect only MPEG-2 compression. • vtr.media.video.input.compression.gop_structure • vtr.media.video.input.compression.gop_size • vtr.media.video.input.compression.sampling They are ignored for DVCPRO 25, DVCPRO 50, DVCAM, and DV (16-bit/48 Khz audio only) video ingestion. Configuring Audio Support For the MFCODEC devices, you can select the audio port map and source map for both input and output.
3: System Configuration The matrix in Table 3-5 shows all possible selections. Table 3-5 Source Selections for Record Input Pairs Audio Input Sources Record Inputs of Each Channel 1/2 3/4 5/6 7/8 Embedded 1/2 X X X X Embedded 3/4 X X X X Embedded 5/6 X X X X Embedded 7/8 X X X X AES/EBU 1/2 X X X X AES/EBU 3/4 X X X X AES/EBU 5/6 X X X X Analog 1/2 X X X X Input notes: 42 • All audio selections are in pairs.
Configuring Audio Support Output As shown in Table 3-6, there are four pairs (eight channels) of audio output. Each audio output type has the equivalent play output pair routed to it at all times. Analog 1/2 can be selected for simple audio monitoring.
3: System Configuration Channel Map/Source Control SGI Media Server controls allow you to select what type of audio to route to each MFCODEC input pair. The choices are embedded (E), AES/EBU (D), or analog (A). The control, vtr.media.audio.input.channel_map.source, is set in the /usr/vtr/config/device-defaults/MFCODEC_n file for the unit you want to configure. This control, combined with the vtr.media.audio.input.channel_map.
Configuring Audio Support Note: For each MFCODEC input pair, its source choice (src_i) has a possible value of 1, 2, 3, or 4. However, as noted previously, these four source choices are not always available for each input type. For instance, if analog was selected for a particular MFCODEC input pair on the vtr.media.audio.input.channel_map.source control, the only valid value for the source is 1.
3: System Configuration Identifying Audio Ports The vtrhwinfo command provides detailed information regarding the configured video and audio ports. The command lists the installed PCI-VIDAUD-MSB-B peripherals and their audio channel interfaces.
Configuring the SGI Media Server for Control by Remote Devices Configuring the SGI Media Server for Control by Remote Devices To configure the SGI Media Server so that it can be controlled by remote devices, use the /usr/vtr/config/control-in.conf file .
3: System Configuration by the “signal 1” configuration line (also specified in control-in.conf) and is using a zero-frame command latency so that commands are executed as quickly as possible. The preroll should always be 0, except for VDCP controllers, for which the preroll is 3. The ingested content to be stored in the directory /usr/vtr/clips/press-conference. The following sections describe each variable in this configuration line.
Configuring the SGI Media Server for Control by Remote Devices Note: Serial and TCP ports (communications ports) are unrelated to video ports (signal ports). speed The speed value specifies the connection speed of the serial connection between the server and the controlling device, usually 38400. On rare occasions, 9600 is used. For TCP connections, enter a hyphen (-) for this setting.
3: System Configuration latency When the SGI Media Server receives a command, the command can apply only to the next frame to enter the video port output queue. For example, if the video port output queue holds three frames, the first frame that can be affected by an incoming command is the third frame in the queue. If a stop command is received, the first two frames in the video port output queue are displayed; the third is not displayed because it is affected by the stop command.
Configuring the SGI Media Server for Control by Remote Devices by an external device. For example, to specify that signal 1 corresponds to the video port known as MFCODEC_4, add the following line: signal 1 MFCODEC_4 Example control-in.conf File The following is a sample control-in.
3: System Configuration # # Signal ports # # Each signal (video) port is mapped from a port number to port name # with a line of this form: # # signal # # port number: Disk port number (> 0) # port name: Video server port name (e.g.
Configuring the SGI Media Server to Control Other Devices connection The valid values of connection include the following: rs232 RS-232 control connection rs422 RS-422 control connection These values must correspond with the type of connection between the video device and the SGI Media Server. The device and the SGI Media Server must agree on the serial connection; the cable between them must be appropriate for that connection.
3: System Configuration Configuring the VTR Daemon (vtrd) The /usr/vtr/config/vtrd.conf file specifies information that controls the VTR daemon process (vtrd). The daemon process is the parent for all instances of the vvtr child process, the process executing for video operations. For more information about the vtrd.conf file format, see the vtrd(1) man page. Mapping Physical Ports to Logical Port Names You can use the /usr/vtr/ports.
Tuning the SGI Media Server (Setting the Maximum DMA Size) vtr.main.timing_standard 625 Note: The system timing standard controls the default video output timing only if the control vtr.media.video.output.timing is not changed from its default value of system. The vtr.media.video.output.timing control appears in the /usr/vtr/config/system-defaults/MFCODEC_n files.
3: System Configuration # reboot 56 007-4403-003
Chapter 4 4. Running the SGI Media Server This chapter consists of the following topics: • “Starting and Stopping VST” on page 57 • “Logging Events” on page 59 • “Monitoring the System” on page 63 Starting and Stopping VST If properly configured, the Video Server Technology (VST) software is normally started automatically when the server boots.
4: Running the SGI Media Server Controlling the Autostart of VST By default, VST is configured to autostart when the system boots. As superuser, you can control the autostart of VST at boot time using the chkconfig command with the vtr option. The following enables automatic startup: # chkconfig vtr on The following disables automatic startup: # chkconfig vtr off Starting VST Manually You must be root to start VST.
Logging Events Setting Startup Options When the VST daemon vtrd starts, it reads the configuration file /usr/vtr/config/vtrd.conf. The daemon vtrd is the VST server daemon that manages the VST parent server processes. The default installation operates normally without any change to the startup options. However, you can change the startup options for vvtr, the VST server process by editing the /usr/vtr/config/vtrd.conf file and adding them immediately after the program path, /usr/vtr/bin/vvtr.
4: Running the SGI Media Server VST Log Message Structure Each VST log message has the following format: c dd-hh:mm:ss.mmmmmm pppp log_message The fields represent the following: c Severity code of the message dd Day of the month hh:mm:ss.
Logging Events The following is an example of a message that has a severity code of 2 (Debug2 severity level). The message was written on day 14 of the month at the time that is shown in the message, and the ID of the process that wrote the message is 8254: 2 14-22:23:50.316766 8254 mvcp/ninety9 <-- 100 VTR Ready The following example shows a Notice-level message: N 29-09:26:11.
4: Running the SGI Media Server Managing Log Rollover Log rollover is the practice of saving the current log file and restarting logging into an empty log file. Rollover avoids the problems of running out of disk space and of having a list of log messages too long to handle easily. VST manages the vtrlog server log file. By default, the log file is saved and a new log file begun every night at 2:00 a.m. if the log file is at least 10 MB. The default number of log files retained on the system is 10.
Monitoring the System Monitoring the System Once VST is installed and running, you can monitor its operation using the tools mentioned in this chapter. Two tools, vtrstat and mcstat, work directly with VST. This section describes how to monitor VST in the following subsections: • “vtrstat” on page 63 • “Standard IRIX Tools” on page 64 Note: The tool mcstat is part of SGI Media Server control GUI, which you can use for non-production, developmental activities.
4: Running the SGI Media Server Example 4-1 shows an example output of vtrstat.
Chapter 5 5. Adding and Removing Clips Clips are segments of audio and video. Managing clips involves adding and removing them to and from the SGI Media Server clip cache.
5: Adding and Removing Clips Overview of Adding Clips Procedure This section provides a procedural overview of the tasks involved in adding clips to the SGI Media Server. The following sections explain the steps in the following procedure in greater detail. To add clips to the cache, use the following procedure. 1. Copy media to the SGI Media Server. You must use a real-time filesystem.
Media Types and Formats elements outside of MVCP sessions. DO NOT use rm, mv, cp, or other native UNIX filesystem commands to manipulate clip content elements residing in the real-time filesystem. Media Types and Formats The SGI Media Server supports two media types, intraframe and interframe media, and several media formats: DIF, SGI MPEG-2, SMPTE 360M (playout only), and MXF. Media Types The SGI Media Server supports intraframe media.
5: Adding and Removing Clips DIF An industry standard format used to store DVCPRO 25, DVCPRO 50, DVCAM, and DV (16-bit/48 Khz audio only) compressed material. MXF An industry standard format used to store MPEG-2, DVCPRO 25, and DVCPRO 50. SMPTE 360M (playout only) An industry-standard exchange format. Playout support is limited to MPEG-2 I-frame compression. Adding Clips to the SGI Media Server The simplest way to move clips from an editing workstation to the SGI Media Server is with FTP.
Adding Clips to the SGI Media Server real-time partition. The real-time partition stores SGI Media Server clip content for playout and the ingested media processed during the encoding process. Most applications, including /usr/bsd/ftp, have no means to distinguish among temporary filesystem characteristics. If you invoke ftp and use the get command on a SGI Media Server to get a file from another platform, the content is stored on the data partition, but not the real-time partition.
5: Adding and Removing Clips You can set the start, in, and out points of a clip using the command site editpoints. By default, these attributes are not transferred with the clip. Proxy Transfers As mentioned previously, a get command with the FTP client on a server will do the wrong thing by writing the file to the data partition of your real-time filesystem. Avoid this use of ftp with vtrftpd. Instead, use proxy transfers between servers, as described in the following paragraphs.
Adding Clips to the SGI Media Server Remote system type is UNIX. Using binary mode to transfer files. ftp> proxy put testftp local: testftp remote: testftp server1.csd.sgi.com:200 Type set to I. server1.csd.sgi.com:227 Entering Passive Mode (130,62,124,44,8,11) server2.csd.sgi.com:200 Type set to I. server2.csd.sgi.com:200 PORT command successful. server2.csd.sgi.com:150 Opening BINARY mode data connection for ’testftp’. server1.csd.sgi.
5: Adding and Removing Clips Clip Alignment Certain clips might need to be aligned in the filesystem for enhanced performance. In single-disk systems, media files are aligned only with the filesystem’s block size so that only one I/O operation is needed to access the data. In multidisk, RAID striped systems, the media files must also be aligned with the stripes. When the SGI Media Server is used to record media, it automatically places the media data in the correct, aligned locations on the disk.
Transferring a Clip Segment Note: If the clip cache resides on a striped XLV volume, the major alignment matches the stripe size of the XLV volume. Notifying the SGI Media Server The SGI Media Server detects the clips when the clip is first loaded and every time the SGI Media Server starts. The clips are then listed in mcclips.
5: Adding and Removing Clips Overriding Clip Segment Transfer If in and out points are set in a clip, but you want to transfer the entire clip, you can override this feature. To transfer an entire file that has in and out points set, enter the following at any point in the session: ftp> site marks This command is a toggle. To turn the clip segment transfer feature on again, enter the command again. Removing Clips There are three ways to remove clips from the SGI Media Server.
MXF Record and Playout Media compression formats such as MPEG-2 require a collateral frame index file to enable reliable playout and ingestion processing. This index contains a frame-by-frame description of the content clip that includes a frame directory for the content file, frame size, offset, timecode, and other pertinent information.
Chapter 6 6. Virtual Clips A virtual clip (vclip) directly links clip content segments through the use of metadata. A clip content segment defines a frame-continuous portion of a larger clip, characterized by in and out points. A virtual clip consists of metadata describing the referenced content using a series of clip name references and in and out points. A virtual clip is similar to an edit decision list or a play list.
6: Virtual Clips The remainder of this chapter explains the Multiport Video Computer Protocol (MVCP) commands applied for vclip operations: • “Virtual Clip Command Overview” on page 78 • “File Operations on Virtual Clips” on page 79 • “Working with Segments” on page 80 • “Working with Frames” on page 85 Virtual Clip Command Overview Table 6-1 provides an alphabetical summary of the MVCP commands used to manipulate virtual clips. The remainder of the chapter describes these commands in more detail.
File Operations on Virtual Clips File Operations on Virtual Clips This section describes the MVCP commands you use to create, open, save, close, or remove virtual clips. This section also describes how to build a non-virtual clip. Creating and Opening Virtual Clips To create a virtual clip, use the MVCP command CMK. The syntax and arguments for CMK and the related command COPN are described briefly as follows: CMK clip-name format-name COPN clip-name clip-name Specifies the name of the clip to create.
6: Virtual Clips clip-name Specifies the segmented virtual clip for the extraction of segment information for the copy into the non-virtual clip destination. The segmented virtual clip must have the movie/vclip format. new-clip Specifies a non-virtual clip destination. start Specifies the start timecode for the non-virtual output.
Working with Segments • Whether the segment data (the in points and out points, for example) are copied into the vclip or simply pointed at by the vclip. • Whether or not the segment referenced in the source clip is erased. The following are valid values for src-op: • The value FCP copies the segment data (the in and out points, for example) from the source clip to the target vclip, as shown in Figure 6-3. The source clip must be segmented.
6: Virtual Clips src-in Specifies the in point in the source clip. If this argument is unspecified, src-in is set to the in point of the source clip. src-out Specifies the out point in the source clip. If this argument is unspecified, src-out is calculated from the following: • The src-in plus in/out duration if the in/out duration is specified • The out point of the source clip if the in/out duration is not specified Figure 6-2 illustrates some of these arguments.
Working with Segments When a segment from a source clip is removed (FRM), the segments before and after the copied segment are joined. The FCL operation is not supported by the PCI-VIDAUD-MSB-B codec.
6: Virtual Clips Use the in and out arguments to display information about segments in a subsection of the vclip. For each segment in a vclip, CSLS displays a line of information in the following format: trk in out clip-name src-trk src-clip src-in src-out trk Always an asterisk (*). in The in point of the segment in the vclip. out The out point of the segment in the vclip. clip-name The system-dependent name of a clip created automatically in the system used for reference counting.
Working with Frames Source vclip Segment cleared Blackened segment Segment removed Figure 6-4 Clearing Versus Removing Segments Working with Frames Instead of adding or removing segments, you can use MVCP commands to add or remove frames in a vclip. Inserting Empty Frames into a Vclip The CFNW command inserts empty (black and silent) frames into a clip based on fixed-format clip content (DVCPRO, DVCPRO 50, DVCAM, or DV (16-bit/48 Khz audio only)).
6: Virtual Clips track-mask Must be an asterisk (*). in Specifies the in point in timecode in the vclip where the empty frames are to be inserted. out Specifies the out point in timecode in the vclip where the inserted empty frames end. To use CFNW, the specified clip must have previously been opened or created using COPN or CMK, respectively, during the current MVCP session.
Chapter 7 7. Configuring and Using External Devices Installation of the SGI Media Server includes configuring it to work with the following types of external devices: • 007-4403-003 Devices that control the SGI Media Server.
7: Configuring and Using External Devices This chapter explains installing and configuring these devices in the following sections: • “Configuring and Using the Sony (P2) Protocol” on page 88 • “Configuring the SGI Media Server to Control a VTR” on page 91 • “Configuring the SGI Media Server for Control by VDCP” on page 93 • “Using House Timecode Readers with the SGI Media Server” on page 98 • “RS-232 and RS-422 Cabling” on page 99 Configuring and Using the Sony (P2) Protocol The Sony (P2) protoc
Configuring and Using the Sony (P2) Protocol • +/-15% playback/recording/editing Note: VAR_FORWARD and VAR_REVERSE are fully implemented. Configuring Sony Protocol Control Ports To configure Sony protocol control ports, follow these steps: 1. As root, use the following command to verify that the vst_eoe.sw.sony subsystem is installed: # /usr/vtr/bin/vtrswinfo -subsys -short Installed software: vst_eoe (1279037220) vst_eoe.man.base (1279037220) vst_eoe.man.ftpd (1279037220) vst_eoe.man.
7: Configuring and Using External Devices 4. Edit the control defaults file for each Sony control port as needed. The directory /usr/vtr/config/system_defaults contains files specifying the default control settings for system-wide resources, including the control processors managing any Sony protocol control ports. • Put control settings that apply to all Sony control ports in vtr.
Configuring the SGI Media Server to Control a VTR 5. Make sure that the EDIT-ON/EE-ON delay time for your edit controller matches the delay time set by VST controls. Changing the Clip Loaded in a Sony Controlled Logical Unit The Sony deck control protocol was originally developed to control VTRs, thus it has no facility for clip management operations including the loading and unloading of clips. The control vtr.control.clip.name can be set to change the clip currently loaded.
7: Configuring and Using External Devices vst_eoe (1279037220) vst_eoe.man.base (1279037220) vst_eoe.man.ftpd (1279037220) vst_eoe.man.relnotes (1279037220) vst_eoe.man.tools (1279037220) vst_eoe.sw.base (1279037220) vst_eoe.sw.clipmirror (1279037220) vst_eoe.sw.diaquest (1279037220) vst_eoe.sw.ftpd (1279037220) vst_eoe.sw.little-red (1279037220) vst_eoe.sw.louth (1279037220) vst_eoe.sw.merlin (1279037220) vst_eoe.sw.merlin_fw (1279037220) vst_eoe.sw.mfcodec (1279037220) vst_eoe.sw.
Configuring the SGI Media Server for Control by VDCP • vtr.media.output.mode • vtr.edit.coincidence.preroll • vtr.media.video.sync_port To guarantee frame-accurate control, the control vtr.media.video.sync_port must be set to the name of the SGI Media Server video port that is connected to the VTR. The application mcpanel does this automatically, but other applications must ensure that the control is set correctly.
7: Configuring and Using External Devices ! Caution: Do not open any units (using the MVCP command UOPN) belonging to a VDCP control protocol processor in order to control them. This section consists of these subsections: • “VDCP Commands” on page 94 • “Using the Harris Automation ADC100 Automation Controller with the SGI Media Server” on page 96 VDCP Commands Table 7-1 summarizes the VDCP commands that the SGI Media Server supports.
Configuring the SGI Media Server for Control by VDCP Table 7-1 007-4403-003 VDCP Commands Supported by the SGI Media Server (continued) Command Type Commands Reset/Select Reset Std. Time New Copy Sort Mode Close Port Select Port Record Init Play Cue Cue with Data Delete ID Clear % to Signal Full Record Init with Data Disk Preroll Sense Request Open Port Next Last Port Status Request Position Request Active ID Request Device Type Request Syst.
7: Configuring and Using External Devices Using the Harris Automation ADC100 Automation Controller with the SGI Media Server An ADC100 Harris Automation controller is connected to the SGI Media Server using one or two serial ports per the video port to be controlled. If you want to play and record at the same time, two serial port connections are required, unless you are using VDCP multiport command support. Follow these steps to connect and configure an ADC100 Harris Automation controller: 1.
Configuring the SGI Media Server for Control by VDCP 3. For each Harris Automation communications port connected to a serial port, include a control port configuration line in the file /usr/vtr/config/control-in.conf. See section “Control Port Configuration Line” on page 47 for configuration instructions and examples and section “RS-232 and RS-422 Cabling” on page 99 for cabling instructions. 4.
7: Configuring and Using External Devices pathname prefix field permits you to specify an arbitrary and relative (relative to /usr/vtr/clips) prefix for the clip path. As shown in Example 7-1, ports 7 and 8, corresponding to MFCODEC_0 and MFCODEC_1, will have their ingested clip content placed in directories /usr/vtr/clips/path1 and /usr/vtr/clips/path2, respectively. MFCODEC_2 and MFCODEC_3, if used for ingest purposes, will both use the directory /usr/vtr/clips as the content ingest path.
RS-232 and RS-422 Cabling The following example shows the control-in.conf file for a Horita PR-232 connected to serial port 3: hsip rs232 3 9600 0 1 29.97 This example shows a Miranda Little Red in a 625/50 configuration: little-red rs232 3 9600 0 1 25 4. Add a line for each device to control-in.conf to configure the SGI Media Server to work with Horita and the Miranda Little Red timecode readers. The following is an example: hsip rs232 3 9600 0 1 29.97 little-red rs232 2 9600 0 1 29.
7: Configuring and Using External Devices Pin 3 Transmit Data (TD) Pin 2 Receive Data (RD) Pin 4 Data Terminal Ready (DTR) (not used) Pin 1 Data Carrier Detect (DCD) (not used) Pin 5 Ground Pin 6 Data Set Ready (DSR) (not used) Pin 7 Request to Send (RTS) Figure 7-1 Pin 9 Ringing Indicator (RI) (not used) Pin 8 Clear to Send (CTS) DB-9 Pinouts for RS-232 and RS-422 Protocols Table 7-3 describes the pin assignments for the RS-232 and RS-422 protocols.
RS-232 and RS-422 Cabling Proper pinouts for passing RS-422 input from Mini-Din connectors to DB-9 connectors are described in the following tables. The Mini-Din connectors are those found on the Menet board. The Menet board can be identified by its six serial ports and four Ethernet ports. There are also notes for RJ12/16 and RJ45 connectors. A proper adapter from Mini-Din to DB-9 uses the configuration shown in Table 7-4.
7: Configuring and Using External Devices Table 7-6 shows the pin assignments for an RS-422 serial port to an RJ-45 cable connector.
Chapter 8 8. Troubleshooting This chapter lists an assortment of common problems and their solutions. The problems include the following: • “625/50 Clips Do Not Play” on page 103 • “Adding a Clip Takes Excessively Long” on page 103 • “Crash: Semaphore Limit Exceeded” on page 104 • “Configuring to Boot From a Backup Plex” on page 104 • “SGI Media Server Crash Files” on page 105 625/50 Clips Do Not Play The default values for the controls are NTSC-specific.
8: Troubleshooting Crash: Semaphore Limit Exceeded If vvtr crashes, you might have exceeded the number of configured pollable semaphores. The log would appear as follows: C 06-14:29:23.348170 1386 Failed opening semaphore file descriptor (sems open=147): No space left on device A 06-14:29:23.348985 1386 FATAL SYSTEM ERROR: SYSTEM CONFIGURATION ERROR To fix the problem, follow these steps: 1. Edit the file /var/sysgen/master.d/usema and increase USMAXDEVS, for example, to 1050. 2.
SGI Media Server Crash Files 4. Reset the SystemPartition, OSLoadPartition, and root environment variables to the values of the disk partition that contains the alternate plex and the swap environment variable to have the value of the alternate swap partition. For example: >> >> >> >> setenv setenv setenv setenv SystemPartition dksc(0,2,8) OSLoadPartition dksc(0,2,0) root dks0d2s0 swap /dev/dsk/dks0d2s1 5. Exit the Command Monitor and restart the system: >> exit ... Option? 1 Starting up the system... .
8: Troubleshooting 3. Run the dbx command on the core file as shown in the following: server 2# dbx ./vvtr ./core . . . (dbx) The dbx utility prints its header information and then prompts for more input. 4. Enter the following dbx command sequence: (dbx)record output /usr/tmp/core.number.txt (dbx)where (Press the space bar or Enter key as needed.) (dbx)quit Send the /usr/tmp/core.number.txt file to SGI support personnel.
Chapter 9 9. Introduction to MVCP This chapter describes common tasks you routinely perform using MVCP commands. Each task is discussed in a tutorial fashion to introduce you to the way MVCP works. Once you master the basic tasks presented in this chapter, you can proceed to the other features offered by MVCP commands. The tasks presented in this chapter are not logically sequential, but modular.
9: Introduction to MVCP • “Configuring Video Recording Compression” on page 114 • “Recording a Clip” on page 114 • “Editing Clips” on page 115 • “Displaying Your Logo” on page 116 • “Playing Clips from a Playlist” on page 117 • “Monitoring Unit State” on page 118 • “Monitoring the System” on page 119 Manual Access to Video Server Technology Video Server Technology (VST) applications routinely open a TCP/IP connection to a host running VST on the MVCP port, normally 5250.
Creating and Deleting a Unit Creating and Deleting a Unit A unit is a virtual VTR. It can play and record video and audio just like a VTR. The UADD command, which you can use to create units, returns the name of the unit as shown in the following example: % UADD MFCODEC_0 * SHAR 202 OK U1 U1, in this case, controls the MFCODEC_0 video board, which includes both an input video port and an output video port.
9: Introduction to MVCP Loading, Creating, and Unloading a Clip To load and unload a clip into a unit, use the following commands, respectively: LOAD unit-name clip-name OUT CRTE UNLD unit-name unit-name Specifies the name of the unit on which the clip is loaded. clip-name Specifies the name of the clip to be loaded. The OUT option means that the clip, clip-name, can only be played, not recorded onto.
Cueing Decks to Play or Record Cueing Decks to Play or Record You can play and record on units without cueing them. There is, however, a good chance that the beginning of the playing or recording will not be clean; the frame count might be off by several frames or the audio might be garbled. You can avoid these problems by cueing the units for playing or recording.
9: Introduction to MVCP 1. Open a TCP/IP connection to a host machine running VST. If successful, VST responds: 100 VTR Ready 2. Create a unit, which is a virtual videotape deck: % UADD MFCODEC_0 * SHAR 3. Load the clip: % LOAD unit-name clip-name OUT unit-name Name of the unit on which the clip is loaded The OUT option means that the clip, clip-name, can only be played, not recorded onto. 4. Cue the clip for playback: % CUE unit-name 5.
Listing Video and Deck Control Ports Device-specific You use the SET and GET commands to specify and retrieve the control values for individual media units that control communication with the video port and audio. System-wide You use the SSET and SGET commands to specify and retrieve the control values for global system values—for example, the log level.
9: Introduction to MVCP Configuring Video Recording Compression To record video using the SGI Media Server, you must set the compression type using vtr.media.video.input.compression.type.
Editing Clips 6. Record onto the clip: % REC unit-name Editing Clips You can edit clips on two levels of granularity: • Clip • Frame Editing at the Clip Level The following MVCP commands provide basic editing functionality for a clip already loaded in a unit: CEDP Sets in and out edit points. CEDP in-point out-point CRM Removes a clip. CRM clip-name CCP Copies a clip. CCP clip-name new-clip-name CMV Renames a clip.
9: Introduction to MVCP Editing at the Frame Level The following MVCP commands manipulate the frames within a clip that is already loaded in a unit: FRM Removes a frame. In film, the equivalent is cutting out frames of film and splicing the two parts of the film back together. FRM unit-name in-frame out-frame FCLR Changes (clears) a frame to black but does not remove it. FCLR unit-name in-frame out-frame FNEW Inserts a black frame into the clip.
Playing Clips from a Playlist Playing Clips from a Playlist The commands to execute a playlist can be performed over a single MVCP control connection. Some control implementations may find it easier to use a unique MVCP control connection for each unit. The commands and the order in which they are sent is identical in either case. 1. Create a unit on the media port. % UADD port 202 OK U1 2. Create a second unit on the same media port. % UADD port 202 OK U2 3. Load the first clip into U1.
9: Introduction to MVCP 8. Play U2 as with U1 above. % /SEQA /SYNR PLAY U2 200 OK 9. Load next clip into U1. % LOAD U1 clip3 OUT 202 OK clip3 movie/dif/dvcpro 108969984 108969984 00:00:00.00 00:00:30.08 * * 29.97 19990415T004148.636950Z CL 10. Cue U1 with a queued command. % /SEQA CUE U1 200 OK 11. Play U1 as above. % /SEQA /SYNR PLAY U1 200 OK Monitoring Unit State When executing a play list, you can display the state of the list execution.
Monitoring the System of the server, and on play the unit status reports seven frames ahead of the frame on the server output port.
9: Introduction to MVCP UADD Unit added URM Unit removed (using UCLS) UCHG Unit state changed UCTL Unit control changed UERR Unit error CADD Clip added CRM Clip removed CEDP Edit points changed CCHG Clip media changed CMV Clip moved CCHP Clip protection changed You can add one or more of these event types to the MON command after the slash (/) that separates the unit names from the event types. If event types are not specified, notification of UCHG, URM, and UCTL events are returned.
Monitoring the System STLS—List Statistics You can return statistical values for one or all components in a system using the list statistics command: STLS [component-name [statistics-type]] component-name Specifies the name of the component about which you want statistics . If omitted, statistics for all components are returned. statistics-type Specifies the type of statistics you want returned. If omitted, all statistics for the specified component are returned.
9: Introduction to MVCP mean Specifies the mean of the values. stddev Specifies the standard deviation of the values. Error Reporting The SGI Media Server reports three types of errors: • MVCP command syntax errors • Controller errors • Unit errors MVCP Command Syntax Errors All MVCP commands return error responses for syntax violations—for example, entering a letter instead of a number.
Chapter 10 10. Clip Mirror Configuration A clip mirror provides an optional, hot-backup capability for the SGI Media Server. Though optional, a clip mirror platform is recommended. A clip mirror duplicates ingested media content processed by the primary SGI Media Server. This redundant structure ensures the availability of important media in the event of a catastrophic SGI Media Server failure.
10: Clip Mirror Configuration Clip Mirror Service Overview Clip cache mirroring is performed using a TCP/IP network communications interface. The clip mirror subsystem transfers clip cache content from the primary SGI Media Server to the clip mirror platform. The transfer is unidirectional and automatic between the primary and mirror platforms and is accomplished using FTP.
Controlling Clip Mirror Operation • If content resides on the mirror platform and is absent from the primary SGI Media Server, a message is generated in /usr/vtr/adm/logs/vtrlog on the primary SGI Media Server. • Clip removal or renaming on the primary SGI Media Server generates clip removal or renaming on the mirror platform. The clip may be removed manually from the mirror using an MVCP commands (CRM).
10: Clip Mirror Configuration control parameters for clip mirroring. The parameters are described in the subsequent subsections. Table 10-1 Clip Mirror Control Parameters Control Parameter Meaning vtr.clipmirror.primary_server.hostname Specifies the primary SGI Media Server to mirror. Set on the clip mirror platform. vtr.clipmirror.local_server.hostname Contains the named identity of the primary SGI Media Server network interface dedicated for file transfer. Set on the primary SGI Media Server. vtr.
Controlling Clip Mirror Operation Parameter vtr.clipmirror.local_server.hostname The vtr.clipmirror.local_server.hostname control specifies the name of the network interface alias for transfers between the primary SGI Media Server and the mirror. A primary SGI Media Server may possess multiple network interfaces, each described by a static IP address and name alias. This control routes clip content network traffic over a specific interface from the primary SGI Media Server to the mirror platform.
10: Clip Mirror Configuration Alternatively, the mirror platform can replace the primary SGI Media Server, and the former primary SGI Media Server can be configured as a mirror platform upon service resumption. Configuring Primary and Mirror Platform Filesystems The SGI Media Server filesystem requires precise tuning and configuration to provide optimal resource allocation. Therefore, it is important to match filesystem structures between the primary SGI Media Server and a mirror platform.
Configuring Primary and Mirror Platform Filesystems 5. On the primary SGI Media Server platform, verify that the configuration file /usr/vtr/config/system-defaults/clipmirror contains the control vtr.clipmirror.local_server.hostname and has the proper value to permit transfers over a dedicated network interface. 6.
10: Clip Mirror Configuration Redesignating Servers To redesignate a mirror platform as the primary SGI Media Server, follow these steps: 1. Disable clip mirroring on the mirror platform, as shown in the following command: SSET clipmirror vtr.clipmirror.primary_server.hostname "" 2. On a new primary SGI Media Server server, verify that the /usr/vtr/config/system-defaults/clipmirror file has the following control unset, as shown in the following entry: vtr.clipmirror.primary_server.
Bandwidth Management Note: The FTP control values must match on both the primary SGI Media Server and the mirror platform. Table 10-2 FTP Control Parameters Control Parameter Meaning vtr.ftp.io.rate.default Specifies the default clip transfer rate (bits/s) for clip mirror operations. vtr.ftp.io.rate.enforce Specifies whether the transfer rate may exceed the value specified by the control vtr.ftp.io.rate.default.The value 0 allows the bandwidth to exceed that default.
10: Clip Mirror Configuration The transfer rate should be slightly above the video input bit rate for the the SGI Media Server. The example above (32000000) represents approximately 1.2 times the real-time rate for a single DVCPRO 25 video stream. The number of FTP transfers set by the vtr.ftp.procs.max control plus the total number of active video codecs defines the number of concurrent data streams under SGI Media Server control. This value, when multiplied by the number the value of control vtr.ftp.io.
Appendix A A. The SGI Media Server Control GUIs ! Caution: Do not use the control GUIs for the control of on-air operations. The control GUIs are designed for non-production activities by developers. SGI Media Server control graphical user interfaces (GUIs) consists of the following: • “The Media Contro Panel” on page 134 (mcpanel), which enables clips to be played and recorded. • “The Unit Status Monitor” on page 159 (mcstat), which displays the status of SGI Media Server ports.
A: The SGI Media Server Control GUIs Running VST Graphical Tools from a Workstation VST is installed only on the SGI Media Server. Do not install VST or component parts on a workstation to use VST tools. To use the VST graphical tools from a workstation, do the following: 1. On your workstation, enter the following command to grant the SGI Media Server X access to your workstation: xhosts +media-server-name 2. Log in to the SGI Media Server. 3.
The Media Contro Panel Starting the Media Control Panel To establish a control connection to VST and start the Media Control Panel, enter the following: % /usr/vtr/bin/mcpanel -h hostname -p videoPort|unit For more complete control of mcpanel, use it with the following set of flags: % /usr/vtr/bin/mcpanel [-h hostname] [-p videoPort|unit] [-D deckCtlPort] [-c clipname] [-r] [-C "inpoint outpoint"] [-P] [-v loglevel] Table A-1 describes each of the options available when starting the Media Control Panel
A: The SGI Media Server Control GUIs Media Control Panel Options (continued) Table A-1 Option Description -C Specifies that the loaded clip should be cued with the specified in and out points. If * is specified for either inpoint or outpoint, the default edit in point or out point is used. -P Specifies that the clip whose name is clipname should start playing when the Media Control Panel starts. -v Sets the logging verbosity level to loglevel.
The Media Contro Panel The Media Control Panel, shown in Figure A-1, is displayed in its own window. This control panel represents a unit, or logical VTR, that is used to play and record clips. The buttons in the control panel are similar in function to those of a standard VTR. For example, there are buttons to load a clip, play it, and pause. Figure A-1 Media Control Panel See “Operating the Media Control Panel” on page 140 for a detailed description of the Media Control Panel.
A: The SGI Media Server Control GUIs Using Telnet to Determine Available Ports To determine which video and deck control ports are available on the SGI Media Server, establish a telnet connection to the server and then use the MVCP PLS (List Ports) command. (See section “Manual Access to Video Server Technology” on page 108 for details.) The following example shows the PLS command output.
The Media Contro Panel Sample Startups of the Media Control Panel The following are examples of starting the Media Control Panel: • When the Media Control Panel is started by entering the following command, a control connection is made to the MFCODEC_12 video port on the media_server host using a newly added unit.
A: The SGI Media Server Control GUIs Operating the Media Control Panel Figure A-2 shows the appearance of the Media Control Panel after a clip has been loaded. The header of the control panel identifies the host, control port, and unit to which the control panel is connected.
The Media Contro Panel The menu bar gives you access to the following: • The File pulldown menu, which lets you load or unload an existing clip, create a new clip, or close the control panel. Most of the functions available in this pulldown menu are also available through buttons in the control panel. • The View pulldown menu, which lets you access the Deck Control window. The Speed Control Panel, and the MPEG-2 controls.
A: The SGI Media Server Control GUIs • The edit points (under Mark) are persistent values stored with a clip. They are used to initialize the cue points when the clip is loaded. An in point (In), the duration (Dur), and an out point (Out) are specified using the following format: hh:mm:ss:ff The hh field is the hours, mm is the minutes, ss is the seconds, and ff is the frame number. In drop-frame mode, the final colon is replaced by a period: hh:mm:ss.
The Media Contro Panel Note: A clip must be cued before it can be played or recorded. This can be accomplished explicitly by clicking a cue button or implicitly by clicking the play or record button without first clicking a cue button. If you click a cue button and then click play or record, the clip starts playing or recording immediately. If you click play or record without first clicking a cue button, the control panel first cues the clip and then starts the requested function.
A: The SGI Media Server Control GUIs <| The jog backward button jogs the clip backward by one frame. Each time you click the jog backward button, the clip jogs back one frame. If the clip is playing when you click this button, the clip jogs backward one frame and then pauses. You have to click either the play button or the pause button to resume play. > The forward play button plays the clip in the forward direction. If the clip is not cued, it is cued before it begins playout.
The Media Contro Panel FCue Forward play without cue (in and out) points set BCue Backward play without cue (in and out) points set If the direction is one of the forward directions (Fwd, F Lp, F/Bwd, or F/B Lp), the clip is cued at its in point. If the direction is one of the backward directions (Bwd, B Lp, B/Fwd, or B/F Lp), the clip is cued at its out point. The forward direction means that the clip plays from its in point to its out point.
A: The SGI Media Server Control GUIs • The middle Option pulldown menu lets you choose the following options: PB The clip’s audio and video are output when a clip is playing; nothing is output at other times (default). PB/EE The clip’s audio and video are output when a clip is playing; the input signal is output at other times. Note: The EE (end-to-end) option emulates a video deck feature and works only when you have an active input source.
The Media Contro Panel In general, buttons that are enabled and can be used appear darker than those that are disabled. For example, when you load an existing clip, the cue for playout button (—>|>) is darker than the cue for recording button (—>|•). This indicates that the cue for playout button is enabled and the cue for recording button is not. Playing or Recording an Existing Clip To play or record an existing clip, follow these steps: 1.
A: The SGI Media Server Control GUIs Figure A-3 148 Loading a Clip into the Logical VTR 007-4403-003
The Media Contro Panel The Load Clip window lists the name, duration, and format of each clip that is stored under /usr/vtr/clips, which is the VST clip cache. For example, clip_8.231 has a duration of 00:00:10.01 and its format is MPEG-2. (If the duration contains an asterisk [*], it means that no material has been recorded in the clip.) Note: If a clip is stored in a directory within /usr/vtr/clips, that directory name precedes the clip name.
A: The SGI Media Server Control GUIs Creating a New Clip To create a new clip and record its content, follow these steps: 1. Click the Create button in the Media Control Panel. The Create Clip window, shown in Figure A-4, appears. Figure A-4 Create Clip Window 2. Enter the name of the clip in the Clip Name field. 3. Choose the compression type of the clip from the Compression option pulldown menu. By default, mpeg2 is chosen for the compression type. 4.
The Media Contro Panel For more information about controlling the video deck, see “Controlling a Video Deck” on page 152. Changing Cue Points and Edit Points You can change the cue points and edit points of a clip in the Media Control Panel in three ways: • Select and type a new value. For example, if you want to change a value from 00:00:00.01 to 00:00:00.05, select the “1” and type “5.” • Click inside a field and use the scroll bar.
A: The SGI Media Server Control GUIs Any changes you make to the edit points or cue points are temporary. The changes cease to exist after the clip is unloaded unless you do one of the following: • To make changes to the edit points permanent (that is, stored persistently with the clip), click the Save Marks button after you make the changes. • To make changes to the cue points permanent, copy them to the edit points and then click the Save Marks button.
The Media Contro Panel Accessing the Deck Control Window To access the Deck Control window, choose View > Deck Control Panel from the menu bar of the Media Control Panel. The Deck Control window, shown in Figure A-5, appears in a separate window.
A: The SGI Media Server Control GUIs Using the Deck Control Window The File pulldown menu in the menu bar of the Deck Control window gives you access to the following options: Close Close the Deck Control window. Exit Close both the Deck Control window and the control panel from which it was launched. The following describes each of the displays and buttons in the Deck Control window: • The edit points let you set the amount of time to preroll, the in point, the duration, and the out point.
The Media Contro Panel • 007-4403-003 You can use the following deck control function buttons: Review Review the specified edit. After the edit is finished, you can use this option to examine the finished edit. Capture Perform a frame-accurate recording from the selected portion of a loaded and cued source tape to the clip currently loaded. For more information about recording, see “Recording From the Deck to a Clip” on page 157. Rehearse Practice the specified edit.
A: The SGI Media Server Control GUIs • The deck control buttons, which control playout and recording, correspond to standard VTR buttons. The following describes these buttons: << The fast-reverse button moves the deck in reverse at a fast speed. <| The jog backward button jogs the deck backward by one frame. Each time you click the jog backward button, the deck jogs back one frame. If the deck is playing when you click this button, the deck jogs backward one frame and then pauses.
The Media Contro Panel Recording From the Deck to a Clip Before using the SGI Media Server to record video from a deck you must do the folowing: • Connect the output of the deck to the input of the video card on the server. • Connect the audio output of the deck to the audio inputs of the server. To record from the deck to a clip, follow these steps: 1. Use the Media Control Panel to do the following: ■ Create a new clip.
A: The SGI Media Server Control GUIs Recording From a Clip to the Deck Before using the SGI Media Server to lay back video to a deck you must do the following: • Connect the input of the deck to the output of the video card on the server. • Connect the audio input of the deck to the audio outputs of the server. To record from a clip to the deck, follow these steps: 1. Use the Media Control Panel to do the following: ■ Load the clip from which you want to record.
The Unit Status Monitor The Unit Status Monitor The Unit Status Monitor, invoked by the mcstat command, graphically displays the activity of all units that are currently open on the SGI Media Server. Figure A-6 shows an example of mcstat output when VST is running. When VST is not running, mcstat exits. Figure A-6 mcstat Output The command displays a list of all the media ports supported by the SGI Media Server.
A: The SGI Media Server Control GUIs The Clip Manager This section describes how to use the Clip Manager graphical user interface (GUI) to manage media clips. Clip Manager is a sample GUI application that you can customize.
The Clip Manager Table A-3 Log Severity Levels (continued) Priority Log Level Description Error -3 Problem that needs correcting but does not require immediate action Warning -2 Possible problem but could be a transient problem that corrects itself Notice -1 Condition that might require attention, but is not an error condition Info 0 Informational message Debugn n Informational message that normally is of use to engineers for debugging; may be Debug1, Debug2, or Debug3, with Debug3 produ
A: The SGI Media Server Control GUIs Figure A-7 Clip Manager Window Note: You can also start the Clip Manager by choosing Utilities > Clip Manager in the Media Control Panel menu bar.
The Clip Manager Clip Manager Menus The File pulldown menu in the menu bar of the Clip Manager window provides the following options: • Info, to obtain information about a clip • Rename, to rename a clip • Delete, to delete a clip • Protect, to set the protection levels for a clip • Close, to close the Clip Manager window • Exit, to close the Clip Manager window and exit the program • Load, to load a clip into a unit controlled by Sony protocol Except for the Close and Exit options, you must
A: The SGI Media Server Control GUIs Obtaining Information About a Clip To obtain information about a clip, follow these steps: 1. Select the clip in the Clip Manager window. 2. Choose File > Info from the menu bar. The clip information window, as shown in Figure A-8, appears. Figure A-8 The Clip Information Window This window shows the in and out points of the clip, the edit points, the size of the clip, and the protection. An asterisk (*) indicates that the value is not set.
The Clip Manager Renaming a Clip To rename a clip, follow these steps: 1. Do one of the following: • Select the clip in the Clip Manager window and then choose File > Rename from the menu bar. • If the clip information window for the clip is displayed, click the Rename button in the information window. The Rename Clip window, as shown in Figure A-9, appears. Figure A-9 Rename Clip Window 2. Enter the new name of the clip. 3. Click the Rename button.
A: The SGI Media Server Control GUIs Figure A-10 Delete Clip Window 2. Click the Delete button to delete the clip. Setting the Protections for a Clip By default, a clip can be deleted, recorded into, and renamed, and its edit point attributes can be changed. Therefore, if you want a clip to be protected from any of these changes, you must set the protections for that clip. This would be especially useful when multiple applications and/or automation controllers are using the SGI Media Server.
The Clip Manager Figure A-11 Set-Protections Window This window identifies the protections that can be set. Each protection is preceded by a check box. If there is a red check in the check box, the corresponding protection is selected. If there is no red check, the corresponding protection is not selected. Note: The default is that a clip has no protections set. Therefore, you must set protections if you want the clip to have any. 2.
Glossary 9-Pin The Sony protocol for communicating with video devices. 9-Pin is the same as RS-422. AES (Audio Engineering Society) AES Stereo Digital Audio Input/Output. This connection provides a stream of digital audio data that complies with the AES Digital Audio format. automation controller Computers that control broadcast devices.
Glossary clip cache XFS filesystems in which the SGI Media Server stores clips. The clip cache can reside on a normal XFS filesystem that can be shared with other uses, or a real-time filesystem created on a set of striped disks or RAID units. cue point Timecodes that are used to move around within a clip and to control the portion of the clip that is played.
Glossary For example, if a clip has an edit in point of 00:00:30.00, its cue in point is initialized to 30 seconds when the clip is loaded. Edit points may also be called “edit marks.” Fibre Channel The Fibre Channel Standard defines a high-speed data transfer interface that can be used to connect workstations, mainframes, supercomputers, storage devices and displays. The standard addresses the need for very fast transfers of large volumes of information.
Glossary GRIO Guaranteed rate I/O. GRIO is included in IRIX and is used by the SGI Media Server to guarantee disk bandwidth for recording and playback while allowing non-priority access to the clip cache for other operations. Horita A company that makes, among other components, timecode readers. Its identifier in configuration files is hsip. See www.horita.com. hsip See Horita. Little Red A timecode reader made by Miranda. Its identifier in configuration files is little-red. See http://www.miranda.com.
Glossary P2 P2 is the Panasonic name for the Sony protocol (RS-422). port A point at which an external device connects to the SGI Media Server. Video ports, used by video input and output devices. MFCODEC video ports are named MFCODEC_n (for example, MFCODEC_2). The term media port refers to either a video or a deck control port.
Glossary as well. VST can parse VDCP through serial ports. Video Server Technology (VST) Video Server Technology is an element of the Video Computing Platform (VCP) from SGI. VST is the clip serving platform element of VCP. The core VST software provides management of a simple database of clips (the clip cache), a control API for managing and operating the VST, and a core library which supports various external interface modules.
Index problems, 10 Sony, 6, 109 VST interfaces, 5 Numbers 100 Base-TX network, 12, 17 1000 Base-SX network, 12, 17 4:2:0 compression sampling, 40 4:2:2 compression sampling, 40 625/50 system configuring, 54 troubleshooting, 103 A ADC100 controller (See Harris Automation controllers.
Index clip, 5 add and remove, 65 cache, 5, 6, 16 creating, 150 deleting, 165 editing, 115 finding a name, 110 loading and unloading, 110 managing, 160 mirroring, 123 obtaining information, 164 playing, 147 recording, 114, 147, 150 renaming, 165 setting protections, 166 troubleshooting, 103 clip alignment, 72 Clip Manager, 141, 160 CLN MVCP command, 115 CLS MVCP command, 110 CMK MVCP command, 78, 79 CMV MVCP command, 115 commands sequencing, 111 compression configuring, 38 D10/IMX, 6, 17 DV, 3, 6, 7, 17, 38
Index D D10/IMX compression, 6, 17 D-10/IMX encoding, 18, 74 DB-9 connector, 99 debug log level, 60 Deck Control Panel, 152-158 device configuration, 36 external configuring and using, 87-99 files, 36 device defaults, 36 Diaquest configuring for, 36 controls for, 92 deck control module, 91 Diaquest software, 6, 17 DIF video format, 7, 27, 38, 67, 68 disk storage, 21 DMA size, setting, 55-56 DV compression, 3, 6, 7, 17, 38, 67, 114 DVCAM compression, 3, 6, 7, 17, 38, 67, 114 DVCPRO 25 compression, 3, 6, 7,
Index GXF (See SMPTE 360M.
Index CCLS, 78, 80 CCP, 115 CEDP, 110, 115 CFCL, 78 CFNW, 78, 85 CFRM, 78 CINF, 69 CLN, 115 CLS, 110 CMK, 78, 79 CMV, 115 COPN, 78, 79 CRM, 74, 80, 115 CSAV, 78, 80 CSCL, 78, 84 CSLS, 78, 83 CSRM, 78, 84 CUE, 111 CUER, 111 CUPS, 78, 79, 80 ERR, 122 FCLR, 116 FINS, 116 FNEW, 116 FOVR, 116 FRM, 116 GET, 113 LOAD, 110 MON, 119 PLAY, 112 PLS, 113 REC, 115 SET, 34, 113 SGET, 113 SSET, 113 STLS, 120 STST, 120 UADD, 109 UCLS, 109 UERR, 122 ULS, 119 007-4403-002 UNLD, 110 UOPN, 94, 109 USTA, 119 MVCP SET command
Index PCI-VIDAUD-MSB-IMX audio/video cards (See also PCI-VIDAUD-MSB-B.
Index Sony automation controller, 109 Sony control protocol, 1, 12, 16, 47, 87, 88-91 space requirements, 21 SSET MVCP command, 113 stack trace files, 105 standards, supported, 18 starting VST automatically, 58 from backup plex, 104-105 manually, 58 options, 59 statistics analysis, 121 list, 121 MVCP commands, 120 status, 143 of units, 119 STLS MVCP command, 120 stopping VST, 58 storage, 12, 16 storage device interface modules, 6 STST MVCP command, 120 system defaults, configuring, 37 setup, 19 tuning for
Index Video Disk Communications Protocol (See VDCP.) video formats DIF, 7, 27, 38, 67, 68 list of, 8 MXF, 7, 27, 38, 67, 68, 74, 75 SGI MPEG-2, 7, 27, 38, 67 SMPTE 360M (playout only), 27, 38, 68, 171 Video Server Technology (See VST.) virtual clips file operations, 79 frames, 85 overview, 77 segments, 80 VST checking status, 59 events, 59-62 monitoring, 63 overview, 3, 5 starting automatically, 58 manually, 58 options, 59 stopping, 58 VTR RS-422 control protocol (See Sony control protocol.
Index X XFS filesystem, 130 XFS real-time filesystem, 68 007-4403-002 183
