SL Neo MAM

SL Neo MAM (Media Asset Management) is the content management system created on the basis of the Skylark SL Neo platform.

• Database service (stored.exe).
• Media Connect Client Application (maconnect.exe)
• Web management of the WebAccess archive (mamproject.exe)
• Transfer Manager Server Application (transfermgr.exe)

Additional licensing is required for:

• the number of connections (considering different IP addresses),
• basic MAM functions (XMP schemes, shortcuts, user rights, BINs),
• tape archive support.

Come functions described in this manual may be unavailable in the Demo mode.

Detailed information about licensing and the license format.

MAM uses the following terms:

The picture displays one of possible variants of implementing МАМ on SL NEO Platform.

• media_db – the local database root folder.
  • db – the folder with database structure information.
    • metadata.txt – the file with database files metadata.
    • store_d.txt – the file with the database structure and basic information on media files.
    • uuid.txt – the file with a service identifier.
    • watch_NAME.txt – the file with structure and basic information about media files on the connected volume titled “NAME”.
  • media – the folder containing subfolders with original media files of the “filename-NIDx-y” category, where NIDx-y is the database internal identifier. Cyrillic names are replaced with underscores. If the volume has been connected to the database root, the folder will be empty.
  • proxy – the folder containing subfolders with proxy-copies of the “filename-NIDx-y” category, where NIDx-y is the database internal identifier. Cyrillic names are replaced with underscores.
  • log – the folder contains saved Event logs. Logs are stored from 1 to 1000 days (the time value is set by the Event Log History option). The title of the file with Event logs has the “stored_YYYY_DD_MM.log” format. Added in 2.2.8 version.
• hires – the folder at the local or network resource containing original media files. The path is set in the Disk Path parameter when creating Volume.
• archive – the folder at the local or network resource containing archive materials. The path is set in the Archive Path parameter.

Text files in the “db” folder may have backup copies of the “filename_N.txt.md5” category, where N is the number from 1 (the newest copy) to 5 (the oldest copy).

It is recommended to place hires and archive folders in the network. They can be connected to the MAM server in several ways:

• by specifying the full network path in MAM settings (e.g.: \\IP_ADDRESS\hires)
• by connecting the network disk, e.g. N:\
• by connecting the network resource to the folder, e.g. Z:\hires

Find out the current version and see the log of software changes.

General information on SL NEO software installation.

Activating the Storage component is enough for the MAM server functioning.

Working with MAM starts from launching SL NEO Media Server that activates the database service and connects to external volumes.

Setting MAM starts from configuring the database: “Andministrator Control Panel→Manage→Storages”

The MAM server usually stores HiRes (BRV) copies of materials on external storage-volumes. A network folder connected to the database may be such a storage. The Volumes tab allows you to set connecting Windows folders or other databases to the configured database. Connecting can be implemented into a folder or the root of the configured database.
The dialog for adding/editing the volume.

Configuring archive parameters is implemented in the Archive Parameters tab.

Starting from version 2.0.60, the Metadata Connectors interface for bulk sending metadata to МАМ has been added.

More details on loading metadata via Metadata Connectors.

Metadata fields are configured according to client needs. Fields configured at this stage expand the basic metadata set for clips in the database.

The Edit Metadata Schema configuring window: “ACP → Status Tab → Database name (Storage) → Metadata Schema…”

Parameter	Description
Load Preset	Loading the schema basic template offered by developers. Basic – basic fields for a MAM server. Vod – basic fields for a VOD server.
Namespaces…	Allows setting non-standard name spaces (if the actual imported XMP file contains fields with unknown name spaces, they will not be displayed during editing, but they will be saved and displayed during export, or after adding corresponding fields to the schema). Prefix – the prefix name. Uri – The usual format is a http://name address. Any address can be set; for example, this URI is used for the “Photoshop” namespace: http://ns.adobe.com/photoshop/1.0/. For the “Skylark” namespace you can use, for example, http://skylark.tv. It is important to always use the same URI for the same prefixes, to avoid conflicts with XMP files containing other URI for that same prefix.
Edit value sets…	The editor of vocab values for fields with the Array type and the Value Restrictions parameter=Dictionary
Secondary event types…	Editing the preset list of values of the Title field for key frames with the Secondary event type
Status certificates…	Editing statuses and dependencies for USER_1-USER16 certificates \\The material status title (e.g.: QCD accepted, QC passed, trimmed, ready for airing) and dependencies with other certificates in the system can be assigned for each of 16 certificates. For instance, the screenshot displays the configured dependency of the Approved status certificate from the Reviewed and Annotated statuses certificate – the first one cannot be installed without the second one. Starting from version 2.4.58, the drop-down Color menu allows setting a status color. After setting a status, the clip icon gets a strip of a corresponding color.
Schema Properties	Fields in the current scheme. Add – adds a new field.
Download schema…	Save schema settings to the local computer.
Upload schema…	Restore settings from the local computer.
Save	Save settings.
Close	Close the window without saving.

Metadata fields editing window

Starting from the 2.0.51 version, there is an option to configure deleting to the Trash folder. This feature is applied to all MAM server clients, but may be redefined by the client local setting.

The configuring window: ACP→Status→Storage_N→Trash Settings…

The possibility of multiuser work is an important part of the MAM system. The Skylark MAM server provides the mechanism of creating and editing user accounts that can work with the database. For convenience of granting access rights, there is a mechanism of combining user accounts into groups.

The window for user and group management: ACP→Status→Storage_N→Manage_Users…

While utilizing the MAM system, desynchronization of the database and physical video files may occur.
A few possible reasons:

• Restoring the database from backup.
• An attempt to delete opened and blocked files.
• Invalid configuration of access rights in the file system.

To search “broken” links and “excessive” files in the database, a Garbage Collect finalizer has been created (added in the 1.8.113 version).

The Garbage Collect configuring window: Administrator Control Panel→Status Tab→Database Name (Storage)→Garbage Collect…

Option	Description
Remove profiles with no media	Deleting profiles (LRV, BRV (which are not on volumes), WP1, WP8) with no actual files. The situation may occur only after rollbacks to backups. The option is available starting from the 2.0.53. version.
Scan unregistered media	Launching the procedure of searching lost files. When clicking, the dialog of selecting the search area appears: MEDIA – the database, ARCHIVE – an archive folder (if configured). As a result of scanning, it shows the general number of lost files with links to them. The listed files can be deleted by the Remove unregistered media button.
Remove unregistered media	The option is activated after scanning the database (Scan unregistered media). Deletes files with no links in the database. After successful deletion, the message appears:: Deletion completed N of N.

Starting from version 2.3.97, the database service does not launch if there is an error of loading the existing database. The existing files are not re-recorded, which allows further restoration.

Possible messages on stored.exe service errors.

Contact Skylark support, if you experience any of the errors.

See the detailed description of Media Connect functions.

Description of MAM Certificates Check Functions.

Starting from version 2.1.0, an MP4 or HLS proxy-copy of the material with the h264 codec for viewing in browsers is available. Generation of up to 8 versions of WebProxy profiles with different h264 encoding settings is supported. WebProxy in the HLS format has support of multi-bitrate and encryption. Starting from version 2.1.26, WebProxy encoding with using the Nvidia NVENC (Pascal) hardware multi-stream encoder is supported.

Originally, the function was created for interaction of the MAM database with the Skylark VOD server announced in the Skylark SL Neo 2.1 software line, and the WebAccess server (web-access to MAM). However, the functional was also used for integration with the AdvertiZoom media planning system, which allowed viewing database clips directly via the AdvertiZoom interface.

The client, knowing the clip title in the database, requests the MAM server by a certain URL address. The MAM server checks the requested clip for web-proxy. If web-proxy is found, it is immediately sent to the client; otherwise, the server generates it on the fly.

The function requires activating the setting: Administrator Control Panel→Manage→Storages→Storage_N→Web Proxy

Parameter	Description
Profile number	Selecting the configurable profile number, from 1 to 8 (according to WP1-WP8 profiles)
Use Proxy as source if available	Encoding WebProxy based on the proxy-copy of the material. “Use proxy as source” is used in cases, when HIRES copy is absent; for instance, when using an archive on tape. Here, a WP profile is required as a Proxy option but for web-viewing, so it is faster to generate one from a Proxy. For VOD this option must be inactive, as profiles must be generated from a HIRES.
Frame rate	Frame frequency of WebProxy files. Available variants: as in the source, 24M, 24, 25, 30M, 30, 50, 60M, 60.
Width	Image width in pixels.
Height	Image height in pixels.
Bitrate (kbps)	Configuring the stream in kbps. Supported values are from 200kbps to 10000kbps with a 50kbps interval, or Auto.
GOP size (sec)	Configuring the interval between i-frames in seconds, from 0.5sec to 10.0sec with the 0.1sec interval.
Profile	Configuring the h264 encoding profile. Default Main Baseline
Max B-frame	The number of B-frames in one GOP. The option is available, when selecting Profile = Main. The parameter may possess the value from 0 to 4.
Format	Selecting a container. MP4 HLS (TS)
Deinterlace	Deinterlacing while encoding.
Encrypt	Turning on AES128 encryption of HLS (TS) data. Viewing such files requires an AES encryption key file. The link to the AES encryption key is automatically added to the playlist file, and the key is placed in the folder with m3u8 playlists and TS files. Added in version 2.2.4.
Encoder	Selecting an encoder for h264 encoding: Default – CPU, NVENC – Nvidia NVENC (Pascal) hardware multi-stream encoder.

Settings are available, if Format = HLS (TS) is selected.

Viewing video is implemented in the browser by the link like http://IP_ADDR:7901/storage/DB_NAME@TITLE/WP1, where:

• IP_ADDR – The server IP address,
• DB_NAME – the database service name,
• TITLE – the clip ID,
• WP1 or WP2 – the lower or higher quality, respectively.

A Url example: http://127.0.0.1:7901/storage/SL_NEO_Storage_1@rec1/WP1

Starting from version 2.0.60, the Metadata Connectors interface for bulk sending metadata to МАМ has been added. Description of the basic connector configuration.

The connector receives a file that must contain XMP batches divided by any number of any kind of dividers (\n, \r\n, ….).

An example of a file containing one XMP batch with ID fields and filename in the skylark namespace:

meta.xmp

<?xpacket begin="" id="W5M0MpCehiHzreSzNTczkc9d"?>
 <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="XMP Core 4.4.0-Exiv2">
   <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
      <rdf:Description rdf:about=""
            xmlns:skylark="http://skylark.tv">
         <skylark:id>
            <rdf:Alt>
               <rdf:li xml:lang="x-default">newid</rdf:li>
            </rdf:Alt>
         </skylark:id>
         <skylark:filename>
            <rdf:Alt>
               <rdf:li xml:lang="x-default">newfile</rdf:li>
            </rdf:Alt>
         </skylark:filename>
      </rdf:Description>
   </rdf:RDF>
 </x:xmpmeta>
<?xpacket end="w"?>

The file with XMP batches is sent by the PUT method to the address: http://IP_ADDRESS:7901/storage/<STORAGE_NAME>?connector=<CONNECTOR_NAME>

An example of a program on nodejs that loads metadata to the Storage_1 database and the “test” connector:

put_metadata.js

var fs = require("fs");
var request = require("request");
var sourceFile = 'demo_metadata2.xmp';
var connectorUrl = 'http://localhost:7901/storage/Storage_1?connector=test'
console.log('Skylark Metadata Loader');
 
fs.stat(sourceFile, function(err, stats) {
	var file = fs.createReadStream(sourceFile)
	  .pipe(request.put({url: connectorUrl, headers:{'Content-Length': stats["size"]}}, function(err, res, body){
		if(res.statusCode === 200) {
			console.log('Load success'); 
		}
		console.log('Response status: ', res.statusCode);
		console.log(body);
	  }));
});

The “request” and “fs” nodejs extensions must be installed for this example to work (the “npm install module_name” command).

Launching the program is implemented from the command-line interface: “nodejs program_file_name.js”.

A new asset has been created during loading.

Transfer Manager User Guide

Any multi-user professional solution cannot be imagined without logs and logging user actions in the system. Skylark MAM provides such opportunities.

To get objective information from the MAM action log, we recommend implementing several actions while configuring the system:

• Deactivate the Enable local admin priveleges parameter: Administrator Control Panel→Manage→Storage_N→Storage Parameters.
• Deactivate the database guest account: Administrator Control Panel→Status→Storage→Manage Users.
• Create the necessary number of accounts to be used separately for every client workplace: Administrator Control Panel→Status→Storage→Manage Users.
• Set passwords for all database accounts, including the Administrator one: Administrator Control Panel→Status→Storage→Manage Users.

Database service system logs are formed at the MAM server and are written to the folder C:\Program Files (x86)\SL NEO Media Platform\run\logs\YYYY_MM\YYYY_MM_DD\, as a txt file.

For viewing logs, we recommend using the Notepad++ text editor.

Logs contain information about the operation time, IP address and login of the operation initiator, implemented action, execution status, etc.

The Media Connect client application can log user actions in Media Browser to a text file. The function can be activated in the application settings: Media Connect→File Menu→Configure…→Storage Tab→Log user actions to. In this field, specify a path to the folder that will store the log file in the txt format.

For viewing logs, we recommend using the Notepad++ text editor.

Logs contain information about the operation date and time, clip name, implemented action, execution status, etc.

The Media Connect application allows viewing the executing process of current operations in Media Browser (import, export, renaming, transfer and so on).

Media Connect→Window Menu→Browser job list

The Media Connect application allows viewing the executing process of current archiving and restoring operations.

Media Connect→Window Menu→Archive Queue

• Broadview creates on-air playlists in the Skylark format.
• Integrated: the mode of viewing proxy-copies (LRV) from the Broadview interface (LRV is searched in the network folder)
• BV can download data about the media availability from Skylark in the XML format (available by the address http://IP_ADDR:7901/storage/DB_NAME@TITLE))

• Receiving information about the edit (points) from Skylark.
• Work is being done on realization of unloading metadata from BV in the XML format to upload it to MAM. Documentation on the format: export_version_to_mam_v2_tz.docx, export_version_to_mam_v2_210515.txt

Skylark Software Updating Order