Administration Guide : Working with Videos : Introduction

Introduction
What Video for Xinet does
The Video module uses the Xinet Video Engine to extend the Xinet workflow by introducing highly-automated and easy-to-use scene-detection heuristics, coupled with low-resolution video conversion functionality. Portal users can browse, and search for the original video, low-resolution versions or key frames that have been stored in the Xinet database.
The Video module also stores previews of Flash SWF, HTML, MP3 files, and 3D AutoCAD files, and includes a Video Reel Generator which allows users to compose storyboards using assets on the system and can extract text from files and store it in the database for later searching. Video file compatibility provides details about the types of files with which the Video module is compatible
End users have a variety of viewing options, depending on Xinet software they are using, Volume configuration and the way key frames are being generated. They include:
When the Xinet Video Engine generates key frames, it does so based on scene changes. Administrative settings control scene-detection thresholds, the frequency of sampling for new scenes and the number of frames to be captured.
Some Video module features will not work without Xinet Portal; however, end users can still view key frames in either Browse mode or by using the mview CGI.
 
Xinet Portal users can stream the original-sized video files from the Stream File option.
Portal users have the ability to Stream and Download videos using different resolutions. In Portal, double-click on the video in the browser view, select Optional Videos tab from the left pane in mview, and then specify a new video resolution.
Note: The visibility of the Optional Videos tab will vary depending on the Download Permissions set for Portal users (On the Administration view, Volumes/Users > User Volume > Edit Volume - Download Permissions options).
Using Portal’s Video Reel Generator plug-in
A Video Reel Generator Collection plug-in allows Portal users to assemble existing video files, PDFs, InDesign documents, Office documents, and captured frames from HTML, SWF files, and images into new videos.
The Video module will also save the association between the reel and the elements used to create it in the Xinet database, so that clicking on any key frame in the reel can reveal the original asset that created that frame.
Note:
When Shockwave Flash (SWF) and HTML interactive files are used with the Video Reel Generator plug-in, they can only be used as static images, similar to PDF spreads.
Conventions
Xinet uses several typographical conventions in this manual to help readers distinguish what must be typed as is and what is simply a parameter to be substituted. In particular, readers should type text set in a typewriter-like font, like this, literally. For example:
# more README or C:\> type README
Readers should enter this command exactly as shown above (minus the shell prompt on Unix systems, #, or the c:\> prompt on Windows systems). Readers should substitute their own applicable text for text set in slanted typewriter type, like this. For example, when one sees
% ls directory_name or C:\> dir directory_name
one might type:
% ls doc or C:\> dir doc
On Unix systems
The two examples given above illustrate another convention: when a command must be issued by the superuser (root), you will see the prompt #; when a command may be issued by a normal user, you will see the prompt%. As in most documentation for Unix software, text references to Unix functions have the form more(1). The word in italic type is the name of the function; the parenthesized number is the section of the Unix Programmer’s Manual containing the function’s manual page.
On Windows systems
When the manual discusses locations for files and programs, it uses default installation path names. If you install files and programs in other locations, the path names will not be the same as in this manual.