Clips are segments of audio and video. Managing clips involves adding and removing them from Video Server Toolkit (VST).
This section provides a procedural overview of the tasks involved in adding clips to VST's cache.
The following sections explain the steps in the following procedure in greater detail.
To add clips to the cache, use the following procedure.
Copy media to the VST machine.
If you are not using a real-time filesystem, use FTP put or get commands.
If you are using a real-time filesystem (recommended), you can either use the vtrutil tool included with VST, or a modified form of FTP, vtrftpd, installable from the VST image. You use the familiar FTP command, get, with vtrftpd to add files to VST.
For more information, see “Adding Clips to VST”.
Align the clips.
If you used FTP or vtrftpd to add clips to VST, you must align them. For more information, see “Clip Alignment”.
Clips added to VST using the vtrutil tool are already aligned.
Register the clip with VST.
Clips are registered automatically upon startup of VST.
If you want notify VST more quickly, or if you have added clips to the system in a different way from those listed in step 1, use one of the following options:
Install the fsmon daemon from the VST image. It periodically updates the list of clips in the cache.
At times, however, fsmon may not auto detect a clip because of an unrecognized format. In that case, you must use one of the following options to notify VST.
Use the mvcp command, CADD.
Use the vtrclip tool.
For more information see, “Notifying VST”.
VST can use different media types and formats
VST supports two types of media:
In intraframe media, the video data for each frame is self-contained and does not depend on the data from neighboring frames. Examples of intraframe media include JPEG, Rice, DVCPRO, and uncompressed video.
In interframe media, the compression techniques used for some video frames may require data from neighboring frames in order to decompress the video frame. An example of interframe media is MPEG1 and MPEG2.
VST uses different formats for storing digital media in its clip cache filesystem(s):
The vframe (short for variable-size frame) format is specific to VST. The video and audio data for each frame is stored contiguously in the media file. A separate index file contains header information that describes the encoding parameters of the video and audio data, and a frame map that stores the offsets of the video and audio data for each frame within the media file.
The vtrvfutil command-line utility provides various analysis and update functions for the vframe format. See the vtrvfutil man page for further information.
The stream format is used for playback of MPEG2 media.
The vtrmpegutil command line utility provides various analogies and update functions for MPEG2 stream format assets. See the vtrmpegutil man page for more information.
Adding clips to VST has been partially automated. For all clip formats:
Transfer the media file into the filesystem, /usr/vtr/clips.
For Vframe or stream format clips, transfer the index file for the clip into /usr/vtr/index.
There are several ways to transfer clips into VST. Which process you use depends on the type of filesystem used. There are two types of files systems:
To guarantee real-time I/O rates, you must use a real-time filesystem.
To transfer clips to a real-time filesystem, use the customized version of ftpd (server) called vtrftpd. It is in subsystem vst_eoe.sw.ftpd. Only this version of FTP can write to real-time filesystems locally.
The feature enhancement in vtrftpd is used when you:
Use FTP (client) on a system connected to VST server.
Use FTP (client) proxy on the VST server.
Both of these methods set up a TCP/IP connection with the vtrftpd server running on the VST system.
To write to the filesystem, use of the following methods:
On the remote archive server, use FTP's put command to copy a clip to the clip cache of VST from a remote host.
On the machine running VST, use a proxy (secondary control) connection, vtrftpd, as follows to copy a clip from the remote archive system to the local clip cache of VST:
ftp source-system ftp> cd source-directory ftp> proxy open localhost ftp> proxy get filename /usr/vtr/clips/filename ftp> cd index ftp> proxy get indexname /usr/vtr/index/indexname ftp> proxy bye ftp> bye
localhost is the VST machine.
vtrftpd is not used when you only use ftp (client) on the VST server because the ftpd server on another system would not be the enhanced version. To copy a clip from the archive server to VST on the machine running VST, login to the archive system, run ftp, and use the put command.
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.
When media data is transferred to VST, it often must be aligned with the disk's blocks and stripes. Whether or not media data must be aligned on your disks depends on the media type of the media file:
Vframe media data requires alignment.
DIF or Interframe media data does not require alignment.
The media data (video and audio for each frame) for a Vframe media clip must be aligned on natural filesystem and disk drive boundaries to enable efficient read and write access to the clip.
Frame-oriented media data in an intraframe clip is aligned along two boundaries:
A single element of a frame (a video field or audio chunk) never crosses a minor or major alignment boundary. VST will not do a read or write operation to the clip media file which crosses a major alignment boundary.
The minor alignment matches the greater of the filesystem block size, or the system memory page size. On O2 workstations, the minor alignment is usually 4 KB, unless a larger filesystem block size was used to construct an XFS filesystem. On Origin, the minor alignment is usually 16 KB, unless a larger filesystem block size was used.
If the clip cache resides on a single disk, no major alignment is required.
If the clip cache resides on a single RAID subsystem, major alignment is required for efficient I/O access to the media data. Either make a real-time filesystem on the RAID and set the real-time extent size of the XFS filesystem to the desired I/O operation size, or add a configuration line to /usr/vtr/config/vtrfsinfo.conf. For example:
|Note: vtrfsinfo.conf is not created by VST so you first must create the file.|
If the clip cache resides on a striped XLV volume, the major alignment matches the stripe size of the XLV volume.
A vframe clip is automatically aligned if you use vtrvfutil to copy the clip, as follows:
% vtrvfutil OriginalClipName NewClipName
vtrufutil automatically stores the media files in /usr/vtr/clips/.
To copy a vframe clip from outside the clip cache, use the following syntax:
% vtrvfutil -i file=MediaFile,index=IndexFile - NewClipName
vtrvfutil can also be used to realign a clip in-place, as follows:
% vtrvfutil -c realign ClipName
See the vtrufutil man page for a complete list of the options.
VST detects the clips when the clip is first loaded and every time VST starts. The clips are then listed in mcclips.
If you place a clip in the clip filesystem, the first time you attempt to access the clip through VST, it attempts to auto-detect the clip's format and add it to the VST clip list. However, until you attempt to access the clip, it will not be visible in a list of clips you obtain from VST. To see the clip immediately, use the following command:
|Note: There might be a delay because adding clips always has a lower priority then playout/record.|
You can also use the following mvcp command to notify VST of an added clip.
However, if you install the vst_eoe.sw_fsmon subsystem, the VST filesystem Monitor will monitor the clip filesystem for clips that are added or deleted and automatically update the internal VST clip list. Sometimes, FSmon cannot autodetect clips added to VST when the clips require the use of an index file, for example, for MPEG and Rice-encoded clips. In this case, you must use the vtrclip add command to add the index file and notify VST.
vtrftpd honors in and out points on DIF clips for transfers from the real-time filesystem on the server. You can transfer the segment of a clip between in and out points instead of having to transfer the whole clip, saving transfer time and disk space in many cases.
If a clip has no in or out point set, vtrftpd uses these defaults:
If the start point (beginning of the file) is invalid or missing, it is set to 00:00:00.00.
If the in point is invalid or missing, it is set to the start point.
If the out point is invalid or missing, it is set to the end of the file.
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.
For more information about using the VST Control panel to remove a clip, see the VST Developer's Guide.
You can completely remove a clip from VST using the following command:
clipName is the name of the clip file.
MVCP command, CRM.
For more information about the CRM command, see Appendix A, “Multiport Video Computer Protocol (MVCP) Command Summary.”
vtrvfutil makes the clip readable by Silicon Graphics digital media tools, such as dminfo, dmconvert, and mediaplayer, or third-party tools that use the Silicon Graphics Movie Library.
# vtrvfutil -c makeqt clipName
clipName is the name of the clip file.
|Note: Clip files are not necessarily usable by other tools.|