Version Protocol Date Author Description /18/05 A. Gaynulin Preliminary Usernotes

Transcription

1 PRODUCT ADC & Invenio. TOPIC Telestream FlipFactory TRANSCODER DATE: March 18 th, 2005 REVISION HISTORY Version Protocol Date Author Description /18/05 A. Gaynulin Preliminary Usernotes E. Redkin /21/05 B. Cribbs Updating Usernotes /27/05 A. Gaynulin Updating Usernotes for phase II /27/06 A. Gaynulin Updating Usernotes for Timeout /21/06 A. Gaynulin Updating Usernotes for Omneon support /10/06 A. Gaynulin Updating Usernotes for ProfileXP Support DESCRIPTION A Telestream Flip Factory system allows the conversion of video files from one input format to one (or more) output format(s). To know the complete list of the supported Input and output formats, please refer to the documentation of the manufacturer. For Reference Only (references Applicable Documents #2) File Media Sources: Non-Streaming Abekas 6000 (on page E-3) ClipMail Pro/Express (on page E-3) DG Systems (on page E-3) Sony media source evtr (on page E-4) FTP Server (on page E-5) GVG Profile (on page E-6) GVG Profile PDR/XP/MAN (on page E-6) Leitch WANStreamer (on page E-7) Liquid Network File (on page E-8) Local File (on page E-8) Local file (Copy) (on page E-8) Media DVX (on page E-8) Network File (on page E-9) Network File (Copy) (on page E-10) Network File (Samba) (on page E-10) Omneon Director (on page E-11) Open Media Framework (OMF) (on page E-11) SeaChange MediaCluster (on page E-12) Sony evtr (on page E-12) Thomson NEXTORE Decoder (on page E-13) Matrox Multi-file Decoder (on page E-14) Imagine Communications Corp. 1

2 Vortex Network File (on page E-14) Vyvx Catch Server (on page E-15) Streaming Leitch VR (on page E-16) ClipMail Pro/Express (on page E-16) Cineon/DPX Profile (on page E-16) OMF Decoder (on page E-18) GVG Profile (on page E-18) Sony MAV70 SXF Reader (on page E-19) File Media Destinations: Attachment FTP Server GVG Profile GVG Profile PDR/XP/MAN Leitch WANStreamer Liquid Network Server Local Folder Local Storage Network Folder Network Folder (Samba) Pinnacle MediaStream SeaChange MediaCluster Telestream ClipMail Vortex Network Server WebDAV Server Web Server (Local) Web Server (Remote) Supported Output Formats Streaming Media 3GP Media Format (page D-3) Flash Media Format (page D-3) MPEG Layer 3 Elementary Stream Media Format (page D-3) MPEG Layer 4 Elementary Stream Media Format (page D-3) PacketVideo MPEG4 Format (page D-3) QuickTime Media Format (page D-3) QuickTime Streaming Format (page D-4) VideoClipStream Media Format (page D-4) WAVE Audio Media Format (page D-4) Windows Media Format (page D-4) Broadcast Media Abekas 6000 Format (page D-5) Grass Valley Group Profile GXF Media Format (page D-5) Leitch Media Format (page D-5) MXF Media Format (page D-6) Omneon Media Format (page D-6) SeaChange Media Format (page D-6) Sony MAV70 Media Format (page D-6) Vortex Media Format (page D-7) Professional Media AVI Media Format (page D-8) Avid OMF Media Format (page D-8) Imagine Communications Corp. 2

3 Avid TransferManager DV Media Format (page D-8) ClipMail MPEG Format (page D-8) DV Stream Media Format (page D-8) DVD Stream Media Format (page D-8) IPV SpectreView Media Format (page D-8) MPEG1 System Stream Media Format (page D-9) MPEG2 Program Stream Media Format (page D-9) MPEG2 Transport Stream Format (page D-9) MPEG4 Media Format (page D-9) MXF Stream Format (page D-9) Pinnacle Liquid Media Format (page D-9) Pinnacle MediaStream Media Format (page D-9) VOD Transport Stream Media Format (page D-10) Misc Duplicate Original Format (page D-2) This user note describes how to load and configure the Telestream Flip Factory Transcoder driver under ADC NT. REQUIREMENTS For the minimum system requirements of the Telestream Flip Factory system, please refer to appropriate user s guide. On the automation side, the requirements are the following ones: Imagine Communications Device server chassis running under windows 2000 with one NIC dedicated to automation purpose and with other one NIC dedicated for the control of the Telestream Flip Factory system. The NIC dedicated to the control of the transcoding system will have to be configured with TCP-IP protocol. ADC software v10.0.x or above with a Flip Factory driver (Device Type = Archive; Sub device Type = Flip Factory Transcoder). The Telestream Flip Factory computer and the Imagine Communications device servers must be on same domain or workgroup. That is required by W2K security. It is highly recommended to configure the computers in the same workgroup. On the device server(s), the Microsoft WinSock ActiveX component must be registered. This can be done by copying the MSWINSCK.OCX, MSWINSCK.OCA, MSWINSCK.DEP files to the C:\WINNT\system32 folder and performing registration of the OCX in the following way: Copy the files listed above to the C:\WINNT\system32 folder. Click the windows Start button and select the Run item. Type regsvr32 C:\WINNT\system32\MSWINSCK.OCX and press Enter. See that the following message box appeared and click the OK button: Imagine Communications Corp. 3

4 Now the Microsoft WinSock ActiveX component is registered successfully. On the device server(s), the Microsoft XML ActiveX component version 4.0 must be registered. This may be done by installing msxml.msi of version 4.0. The Telestream Flip Factory driver is based on a Standard Archive object and only responds to commands from a Distributor object, which may exist on an ADC Server. Below, this distributor is called Transcoder distributor. The driver handles COPY TO ARCHIVE commands that are inserted in a GMT List used for the transcoding in order to send the appropriate request to the Flip Factory. The Transcoder distributor must be configured in Archive routing mode and point to the Flip Factory driver. If the Source of the transcoding is a videodisk, the Transcoder distributor source tab must point to the videodisk driver and an appropriate fiber handle must be specified. If the Source of the transcoding is an Archive, the Transcoder Distributor source tab must point to the same Flip Factory driver. A non-zero fiber handle must be set also. It is assumed that the file to be transcoded is in the Archive. For each Telestream Flip Factory driver, at least, one distributor is required. If there is one transcoder distributor, then one transcoding at a time could be performed. Adding transcoder distributors will increase the number of simultaneous transcoding within the limits of the Telestream Flip Factory System. The driver also handles Query ID commands that are inserted in a GMT List used for verifying if the clip exists on any of the preconfigured Profile XP sources. The Video Disk Profile XP sources must be configured and assigned to the lists different from the one to which the Flip Factory is assigned to. It is important to remember the video disk channel and the list this pair is used for requesting the media id on the device, when the QRY command is received by the Flip Factory driver. SUPPORTED FEATURES Imagine Communications Corp. 4

5 The driver supports file transcoding: One single transcoding at a time Multiple transcoding at a time (Maximum number of transcodings depends on the license, configuration of the Telestream Flip Factory server and number of transcoder distributors). Verification is the source media is available on the preconfigured Profile XP source. The driver considers that the transcoding request has failed if the Telestream Flip Factory reports an error. DEVICE CONFIGURATION Please refer to the Telestream Flip Factory user s guide, for details. A technician from Telestream will install and configure the Telestream Flip Factory system. Just check with the user that the Telestream Flip Factory system has been properly installed and configured; The Flip Factory system must allow an automation system to control it. Make sure that: User settings have been set as required. Encoding parameters have been set as required (the specified user has a number of necessary factories and their settings meet your requirements) CABLE REQUIREMENTS The automation device server is connected to a hub or a switch where the Telestream Flip Factory server is also connected. This is done through a standard Ethernet 100Mb cable. DEVICE SERVER SETUP The driver Graphic User Interface includes 1 tab: It is called General and allows the configuration of general parameters of the transcoder. General tab: Imagine Communications Corp. 5

6 DEVICE NAME: This parameter defines the name of the driver into the ADC nt configuration. Default parameter is FLIPF. HOST NAME: This parameter identifies the Telestream Flip Factory System the driver is communicating with. This parameter can take a name or an IP address. Default parameter is localhost. PORT: This parameter identifies the Telestream Flip Factory System the driver is communicating with. This parameter can vary from 0 to Default parameter is FACTORY NAME: This parameter defines the factory that will be used to transcode the files. This parameter must be configured according to the Telestream Flip Factory settings. Default parameter is. PRIORITY: This parameter defines the priority to attach to each transcode command. Imagine Communications Corp. 6

7 The supported values are from 1 (lowest) to 9 (highest); Default parameter is 5. USER NAME: This parameter defines the user name that will be used to access specified factory for transcoding the files. This parameter must be configured according to the Telestream Flip Factory settings. Default parameter is. PASSWORD: This parameter defines the password that will be used for the current user name to access specified factory for transcoding the files. This parameter must be configured according to the Telestream Flip Factory settings. Default parameter is. POLLING: This parameter enables or disables polling the Flip Factory server by ADC Flip Factory Transcoder driver. The polling period is about 2 seconds. It s highly recommended to check this control, otherwise the Flip Factory status information will not be monitored while transcoding nothing. Default parameter is false (unchecked). TIMEOUT (MSEC): This parameter identifies the Polling period for the Telestream Flip Factory driver in milliseconds. This parameter can vary from 1000 to Default parameter is ReInitialize Click this button to make the Flip Factory driver re-read the flipfactory.ini file with the configuration. LOGGING: This parameter enables or disables logging of actions performed by the Flip Factory Transcoder driver. It s recommended to check this control if any troubles occurred while working with the Flip Factory server (logging may require a lot of disk space for log files). Remark 1:: the logging information will be stored on a local hard drive, disk C:\. The file name is formed according to the following scheme: log_ff_mm_dd_yy_xxxx.txt, where mm_dd_yy current date and xxxx random generated number. Default parameter is false (unchecked). INI file configuration Imagine Communications Corp. 7

8 The transcoding parameters are now configured in the flipfactory.ini file, which is to stored in the same folder where the ADC is installed to. The structure of the INI file is the following: Each factory (transcoding type) is configured as an independent section in this file. All the sections must have unique names within the ini file. The following keys are basically used in the ini file for configuring source of the transcoding and factory name: [factory1] Fiber = 1 SourceType = NTFS Directory= D:\VideoOut\ EXT =.mpg Destination=factoryGVG Timeout=00:00:10 Fiber The flip factory driver listens for the requests from distributors, Each distributor, which points to the FF driver should have its unique Fiber Handle. Flip Factory driver extracts this value from the incoming request from distributor and use it to define, which setting should be used for transcoding of this request. So, in the ini file the fiber value must be the same, as the Fiber Handle of the desired distributor. Remark 1: we strongly recommend using unique Fiber values within ini file, otherwise it may cause to the incorrect behavior of the FF device driver SourceType: It is possible to choose between NTFS sharing, FTP protocol, Omneon Director protocol and GVG Profile XP protocol to access to source video files. If NTFS format is selected, the transcoding request will contain the windows-style path to the transcoded file and access type will be NTFS shared (or local) folder. If FTP transport protocol is selected, the transcoding request will contain the ftp path parameters to the transcoded file and access type will be FTP protocol. Some additional keys should be added to the section where FTP source type is selected. If Omneon transport protocol is selected, the transcoding request will contain the omneon path parameters to the transcoded file and access type will be Omneon Director Protocol. Some additional keys should be added to the section where Omneon source type is selected. If GVGProfileXP transport protocol is selected, the transcoding request will Imagine Communications Corp. 8

9 contain the Profile XP path parameters to the transcoded file and access type will be Profile XP Protocol. Some additional keys should be added to the section where Omneon source type is selected. Directory: This parameter defines the source directory (storage) that will be used to get the files to be transcoded. It must be configured according to the selected transport protocol (e.g. C:\video\ for NTFS or /video/media1/ for FTP ). Remark 1:: Always specify the last slash character in the configured path. For example: C:\Video\ correct, C:\Video incorrect. Remark 2:: For FTP source the Directory value should contain the directory on the ftp server, where the transcoded media is situated. (For example for file ftp:// /video/media/1.mpg you should specify the /video/media1/ in the Directory field). EXT This parameter defines the source extension of the source filenames. Then, it can be modified to another value. Make sure that the right case is used. Remark 1: The driver does not insert the. (dot) character automatically between the filename and the extension. The. (dot) character must be set in the Source Extension field. Remark 2: A blank field can be configured. In this case, this configuration means that there is no extension for the IDs to be transcoded. Timeout This parameter defines the timeout for the distributor to be released. The template is HH:MM:SS. It takes value from 1 second till 1 hour. If the Timeout value is specified to zero value (00:00:00) or more than 1 hour then the timeout value is overridden and the distributor will not be released until the clip is transcoded. FTP source: For SourceType = FTP the following structure should be used to set up the transcoding parameters properly: [factory2] Fiber = 2 SourceType = FTP FTP_IP= FTP_PORT=21 FTP_USER=username Imagine Communications Corp. 9

10 FTP_PASS=password Directory=/video/ EXT =.mpg FTP_PASSIVEMODE = 1 FTP_VERBLIST = 0 Destination=factoryGVG Timeout=00:00:10 FTP_IP: This parameter defines the FTP server name where the files to be transcoded are situated. FTP_PORT: This parameter defines the port to connect to the FTP server where the files to be transcoded are situated.. This parameter can vary from 20 to FTP_USER: This parameter defines the user name that will be used to access specified FTP server. FTP_PASS: This parameter defines the password that will be used to access specified FTP server. Default parameter is. FTP_PASSIVEMODE: This parameter defines the ftp server access mode from passive to active (1 for passive, 0 for Active) VERBOSE LISTINGS: This parameter enables or disables verbose listings. (1 enabled, 0 - disabled) Omneon source: For SourceType = Omneon the following structure should be used to set up the transcoding parameters properly: [factory3] Fiber = 3 SourceType = Omneon Directory=/video/ EXT =.mov Destination=factoryGVG Domain=Workgroup Timeout=00:00:10 Imagine Communications Corp. 10

11 Domain: This parameter defines the domain or workgroup for Omneon server to connect using the Omneon director protocol. GVGProfileXP source: For SourceType = GVGProfileXP the following structure should be used to set up the transcoding parameters properly: [factory4] Fiber = 4 SourceType = GVGProfileXP Directory=ext:/videoout/ EXT =.mpg Destination=factory GVGServer=profile GVGRealIP= Timeout=00:00:10 GVGServer: This parameter defines the Profile XP Server name to connect to, using the Profile XP Protocol. GVGRealIP: This parameter defines the Profile XP Server real IP address to connect to, using the Profile XP Protocol. For processing the QRY commands the Flip Factory driver needs that the following section should be added to the INI file: [VIDEODISKSDATA] CHANNELS=x1 x2 FIBERHANDLES=y1 y2 LISTS=z1 z2 Where the following set (x1, y1, z1) corresponds to one profile XP driver and x1 is a channel number, where the profile XP driver is assigned to y1 is a fiber handle of the section in the same INI file, where the parameters to establish connection to this profile are specified z1 is a list number, to which the profile XP is assigned to The values in the strings (if more that 1 profile is configured) should be space separated. Example: Profile 1 is at channel 5 and assigned to list 2, its Fiber = 100. Imagine Communications Corp. 11

12 Profile 2 is at channel 6 and assigned to list 3, its Fiber = 101. [VIDEODISKSDATA] CHANNELS=5 6 FIBERHANDLES= LISTS=2 3 OPERATION NOTES The driver manages the following communication statuses with the Telestream Flip Factory: NO COM: There is no configured host name in the driver, or communication lost with the Telestream Flip Factory server.. OFFLINE: The driver is not communicating with the Telestream Flip Factory. UNTHREADED: The driver is communicating with the Telestream Flip Factory. BUSY: This status happens when the Telestream Flip Factory is currently transcoding some files. COMPATIBLE TELESTREAM VERSIONS Min Version : 3.0 FlipFactory HTTP Transcoding Engine. KNOWN ISSUES The driver is able to return 4 error messages to any client of the ADC nt that requests a transcoding. ID not found: o Error with source of the transcoding. Please refer to Flip Factory MDML Elements Reference. Device read/write error: o Error with destination of the transcoding. Please refer to Flip Factory MDML Elements Reference. Macro fail: o Error with message. Please refer to Flip Factory MDML Elements Reference. Operator aborted o Notifies the operator that the request was manually aborted (either via Client's allpication or via Flip Factory tools). Please refer to Flip Factory MDML Elements Reference. Imagine Communications Corp. 12

13 TROUBLESHOOTING 1. Ensure that the Telestream Flip Factory and the ADC can communicate over TCP/IP. Use the ping program to test the path. 2. Ensure that the Telestream Flip Factory and the ADC are configured in the same workgroup. 3. Ensure that the Telestream Flip Factory services (HTTP) are functioning properly on. Use IE to view that the Flip Factory server is on-line. 4. Ensure that the ADC nt software is running and properly configured as described above. Connect a ADC NT Configuration software to the ADC nt software and check the status of the Telestream Flip Factory driver in the Device Status window. If the ADC has not been able to connect to the Telestream Flip Factory, the status will be NO COM. A successful connection is indicated by the status UNTHREADED. 5. Ensure that the Microsoft WinSock ActiveX component is installed and registered successfully on the ADC. 6. Ensure that the Microsoft XML ActiveX component is installed and registered successfully on the ADC. INTERNAL DOCUMENT # TBD FILE TBD Imagine Communications Corp. 13