To run analysis on media, you must create a Media Server configuration file that instructs Media Server how to process the media. Micro Focus recommends that you save the configuration in a location accessible to CFS, and configure CFS to send the configuration to Media Server with each request.
Example Media Server configurations are provided with CFS in the script_resources/mediaserver
directory.
The Media Server configuration must meet the following requirements.
There is no single configuration that can process both images and video, so you must configure Media Server to ingest the correct type of media.
The following example demonstrates how to configure ingestion. To process audio or video files, set the parameter IngestEngine=AudioVideo
so that Media Server uses the settings in the [AudioVideo]
section of the configuration. To process image files (including PDF files and office documents that contain embedded images), set the parameter IngestEngine=Image
. The Lua functions analyze_media_in_document
and analyze_media_in_file
allow you to override individual parameters, so if you request analysis from a Lua script you can first determine the file type and then set the value of the parameter when you call the function.
[Ingest] IngestRate=0 IngestEngine=AudioVideo [AudioVideo] Type=LibAv [Image] Type=Image
For more information about configuring ingestion, and the file types that are supported, refer to the Media Server Administration Guide.
Create a section in the configuration file named [Analysis]
, and configure the analysis operations that you want to run.
The following example configures face detection and optical character recognition:
[Analysis] AnalysisEngine0=FaceDetect AnalysisEngine1=OCR [FaceDetect] Type=FaceDetect MinSize=70 [OCR] Type=OCR
For more information about configuring analysis in Media Server, refer to the Media Server Administration Guide.
CFS expects Media Server to return the results of analysis in the process
action response. You must create a section in the configuration file named [Output]
, and configure an output task to write data to the action response.
[Output] OutputEngine0=response
[response] Type=response
|