MMS - ETERE Aspera Quality Check is the action used by ETERE system to Perform an advanced audio\video quality check from Etere re-calling an API of Aspera.
MMS---Aspera---General-Tab
MMS---Aspera---Tab
To create this action, the following fields must be filled.
NB: to use ASPERA action you need the licence "EA1544-> Etere Aspera Driver".
GENERAL TAB
Name: Give it a short name to identify the action.
Operation: Select "Aspera Integration" 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 or delete.
DESTINATION
Device: Select the destination device to which the files would be copied.
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 where the files would be copied to.
Filename: Choose, among the following options, how the destination filename should be managed.
• Keep source name - Enable this option to maintain the file source file name in the destination. This option is enabled by default. Not available for Rename file action.
• 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 action, a rule is used that must take the value from a flexi that contains characters not supported by the operating system (such as | \ / : * ") ETERE automatically replaces them with the character - (hyphen)
Extension: This parameter allows modification of the extension of the destination file, activating the "Change" flag and typing it in the field.
OPTIONS
Do not use media folders even if configured: Enable this option to ignore the translated path, even if it's configured.
Concurrent processes: Indicate the maximum number of actions that can be taken at the workstation simultaneously.
Never update DB files: The file won't be updated in the database.
Update all assets linked to the source file: If enabled (default), the copied file will be associated with all the asset forms linked to the source file.
Enabling this option is useful, for instance, when a single file is used by multiple assets (e.g. which transmit it overlaid with different logos); in this case, every time the file is copied, the new copy will be updated across all linked assets.
If disabled, the copied file will be associated only with the asset form for which the T-workflow has been launched.
Disabling this option is useful, for instance, when a single big file (e.g. a live feed recording) is used by multiple assets which partially retrieve a smaller file; in this case, only the support from which the partial retrieve has been executed will be updated.
Use SSL: Enable this option to use SSL (Secure Socket Layer) when saving the file in a destination path over the network. If enabled, the service media manager would attempt to complete the action using the following authentication steps in sequential order:
- FTP over TLS (Transport Layer Security)
- FTP over SSL (Secure Socket Layer)
- Plain FTP (without encryption)
If the FTP server supports SSL encryption, the Media Manager service will use a new set of libraries for copying files. Else, Plain FTP would be used.
Use passive mode: If checked, the FTP client will try to use passive mode for all file transfers (upload/download/move); otherwise (if disabled), the standard active way will be used.
Use "passive server to server" when moving between FTP servers: Enable this option if both source and destination devices use the FTP protocol and support 'passive mode'.
Check the file size with db value: If enabled, an additional check would be performed to compare the size of the copied physical file and the file size stored on db. This is useful to signal if the file has not been copied entirely into the destination folder. In this case, its file size differs from the original one, and this check can alert the operator by signalling an error in the wf. Not available for this kind of action.
Skip media check: Allow to avoid checking if the source file's device and codec match with the ones defined in the action. This is mandatory in the case of the Memory cut action because the Memory cut wf is attached to a new empty asset with no meta file, so the action would end in error if this parameter is disabled. Not available for this kind of action.
Maximum Bandwidth: The maximum bandwidth option is only supported for copies to limit the bandwidth used for data transfers.
ASPERA TAB
Connection Parameters:
Web service URL (mandatory) -> URL on which the Aspera web services is available (i.e. where jobs are managed): http://[AsperaServer]:[40001]/services/soap/[ServiceName] For instance: . http://172.31.230.98:40001/services/soap/Transfer-201210
User (mandatory if required by ws) -> Login username for accessing the Aspera web service.
Password (mandatory if required by ws) -> Login password for authenticating the username in the web service.
Job options:
CreatePath (optional) -> Specify if directories should be created if they don't exist. Possible values are:
Yes or No (default)
FileOverwrite (optional) -> Specify the transfer behaviour in case a file to transfer already exists in the destination. Possible values are:
Always Existing files w ill be alw ays overw ritten.
Never Existing files w ill be never overw ritten.
Diff (default) Existing files w ill be overw ritten if they're different.
Older Existing files w ill be overw ritten if they're older.
DiffAndOlder Existing files w ill be overw ritten if they're different and older.
RateBWC (optional) -> Cap on data transfer rates in Kbps. (default 10000000). Please note that a value of "10000000" indicates that no bandwidth cap will be applied.
RatePriority (optional) -> Set the priority when sharing virtual bandwidth cap. Possible values are:
1 High priority
2 (default) Normal priority
ChannelPort (optional) -> Enter the UDP port over which data will be transported. (default is 33001)
Operation (mandatory) -> Specify the transfer type for which the action is aimed:
U Upload files to an Aspera server from a source cloud-device.
D Download files from an Aspera server to a destination cloud-device.
Local End Point:
Url -> User Login name of local transfer endpoint.
Port (optional) -> SSH port over which the Aspera system will initiate the transfer (default is 22).
User (mandatory) -> Login name to access the remote transfer endpoint
Password (mandatory) -> Login password to access the remote transfer endpoint