Administration Guide : Command-line manual pages

MOVSYNC(1M) manual page


movsync - responsible for sending preview frames from video, Shockwave Flash Annimation, HTML and MP3 files to the Xinet WebNative Suite MySQL database.


movsync [ -v ] [ -d dblev | -D ] [ -fid FileID ] [ -volflags flags ] [ -n count ] [ -config path to XML-config file ] [ full file path ]


The movsync (1M) program is responsible for sending preview frames from video, Shockwave Flash (SWF), HTML and MP3 files to the Xinet WebNative Suite MySQL database. Xinet WebNative Suite programs write events into webdblog files, located in the /var/adm/appletalk directory. The dblogd (1M) daemon reads the webdblog files, and when it finds a match to a video or interactive file type listed in the Xinet file-type library (/usr/adm/appletalk/filetype ), dblogd (1M) gives the file to fpod (1M) for processing. The fpod (1M) daemon then calls movsync (1M) to process each of these files. Before it does so, movsync (1M) runs a second match-comparison based on Type for Video or MP3 files, the first three bytes for SWF files and file suffix for HTML files. With each match, it creates key-frame previews for the WebNative Suite database, and for video files, if configured to do so, optional low-resolution videos that are made available through WebNative Portal. For MP3 files, it also stores cover artwork, additional artwork and some metadata that is associated with the file. The movsync (1M) program is configured on a per-volume basis, typically through the nativeadmin GUI. Optionally, for debugging purposes, an XML configuration file may be passed to movsync (1M) via the -config command option and will override settings stored in the database. How movsync (1M) processes a file depends upon its nativeadmin GUI configuration (stored in the MovieSettings and HTMLSettings columns in the Volumes table of the database and the /usr/etc/venture/var/vsp.conf settings file) and whether it determines the file to be a video file, a Shockwave Flash Annimation file (SWF , not Flash animation, FLA ), MP3 or an HTML file. The following files will be classified as video files: mpg4, M4V, M4VP, MPEG, MooV, VfW, AIFC, RIFF, and ASF. Depending how it's configured, movsync (1M) will pass these on to the Xinet Video Engine and store what it recieves back into the database (optionally, also including low-resolution videos to be used with the Video Reel Generator). Shockwave Flash Animation Files typically have a type of SWFL . The movsync (1M) process identifies these files for processing by looking at the first three bytes: CWS means the file is a compressed Shockwave Flash file, FWS means it is uncompressed. After identification, movsync (1M) passes the file to the browser capture process, browcapt (1M) , which depending on the server platform, uses various mechanisms to capture Web page previews for movsync (1M) . The movsync (1M) process identifies any file with the following file extensions as an HTML file: htm , html , url , webloc , mht , and webarchive . It passes HTML files on to htmlsync (1M) , which is responsible for generating Web page previews. The htmlsync (1M) process will in turn call browcapt (1M) to generate the JPEG screens that movsync (1M) will store in the database. When the movsync (1M) process encounters an MP3 file, it extracts and stores MP3 album art along with basic MP3 information such as codec name, sample rate, bitrate and number of channels. The album art is extracted from the MP3 and stored in the database. If present, album art tagged with ID3PT_COVERFRONT will be added as the first item, with all other album art added in the order it is stored in the MP3 file.

Command Options

The flags are defined as follows:
Displays the current version and exits.
-d dblev
Turns on debugging at a certain level, represented by dblev (in hex).
Turns on full debugging.
-fid FileID
The WebNative Suite file identification number (in decimal) for the file to be processed. A file path is not needed when a FileID is supplied.
-volflags flags
Optional decimal volume information flags (normally pulled from the WebNative Suite database).
-n count
The movsync (1M) program is called repeatedly for the same file to monitor its progress. This options passes the process execution count of a particular file, starting with 0 as first occurrence.
-config path to XML-config file
The path specifies the name of an XML configuration file which movsync (1M) will use instead of the database settings. (See Examples .)
-full file path
While not as sure as identifying the file by its file identification number, you may supply the full file path alone, letting movsync (1M) supply the file identification number. If it cannot associate a number with the name, movsync (1M) will exit.


movsync -fid316
Process file ID 316 for the first time. This tells movsync(1M) to process the file with ID 316 using the settings that have been configured for the volume on which the file resides.
movsync -config test.xml
This tells movsync (1M) to use the XML file test.xml rather than values stored in the Volume table of the database to process the file . You can model temporary XML-configuration files on this example, test.xml ; but, take care. If you make mistakes, you'll see unexpected results. This example sets the <framespersec> value to 2 . You may use any value between 1 and 8 . Finally, the example has been configured to potentially generate three kinds of lower-resolution videos, (although the last two have been disabled): there's a QuickTime video with a high quality setting (H:5) , a Flash video, disabled, with a medium-quality setting (M:9) and a Windows Media video, also disabled, with a low quality setting (L:18).

<?xml version="1.0" encoding="utf-8"?> 

 Files /usr/etc/venture/bin/movsync