MMS - Wave form export is the action used by ETERE system to export the waveform from a source metafile to destination device.
MMS---Wave form
To create this action, the following fields must be filled.
GENERAL TAB
Name: Give it a short name to identify the action.
Operation: Select "Copy file" option.
SOURCE
Current metafile: Select this option to use the current metafile previously set.
Device/Codec: Select the source device and codec. If the metadevice contains multiple versions (codecs) of the file, select the codec you wish to copy.
DESTINATION
Device: Select the destination device to which the image file will be exported.
Path: If the selected cloud device contains more than one path, this parameter allows one to choose one of them as the destination path.
Codec: Select the destination codec of the copied files.
Filename: Choose, among the following options, how the destination filename should be managed:
• Keep source name - Enable this option to maintain the source filename for the destination file. This option is enabled by default.
• Asset ID - Rename the file as the ID of the asset to which the wf is attached.
• Asset code - Rename the file as the asset code to which the wf is attached.
• Asset code + type - Rename the file as the code and the type of the asset to which the wf is attached.
• Generate a unique name - The physical file will be named using a unique identification (UID) automatically generated by a system algorithm.
By default, one unique name is generated for each metafile; therefore, in case the file is formed by multiple physical files (e.g. mpg, pd, vix), Etere DataMover will use the same UID for all files but different extensions; for instance, the files 2143.mpg, 2143. vix and 2143.pd will become 02BD0000000000000075.mpg, 02BD0000000000000075.vix, 02BD0000000000000075.pd.
If the metafile name is changed, Etere DataMover will use the same UID for both the file and the metafile, thus allowing the support of video servers on which video files are managed, maintaining a relationship between the name of metafiles and physical files.
• Use custom rules - The file will be named with a custom filename based on database references (e.g.: Flexi-metadata, asset data...) and free text.
Note: If in the RENAME option, the rule takes the value from a flexi which contains characters not supported by the operating system (such as | \ / : * "), ETERE automatically replaces them with the character '-' (hyphen).
Extension: This parameter allows the modification of the destination file's extension, activating the "Change" flag and typing it in the field.