...
Please see Desktop Client - 4.0.0.0 for more information
Metus MAM Web Client
In addition to the Desktop Client, Metus MAM can also be accessed and used by web client that can run inside all popular web browsers and from all operating systems. This lightweight client, while lacking all features of the desktop client, still allows users to import video files, enter metadata, browse the archive and play the proxy files and more features.
...
Please see Web Client - 4.0.0.0 for more information
Metus MAM NLE Plug-ins
Metus MAM has plugins for Grass Valley EDIUS™ and SONY Vegas™. These are opened from within the NLE interface and allow the user to search and browse the MAM project as if he/she were using the Desktop clients. Found assets can be played inside the plugin, and dragged and dropped into the timeline. By default, what goes to the timeline are the proxy versions of the files, so that they can be played from a networked storage without glitch. After users finish their editing on the NLE, a control on the plugin switches the files on the timeline with their high-res versions. Then, after the render is performed, the rendered file is imported back into the MAM.
...
Please see NLE Plug-ins for more information
Metus MAC Client (Discontinue)
Metus MAC Client is a desktop client that runs on MacOSX to search and browse the archive from MAC computers, and interface with Final Cut Pro. Selected videos can be played on the user interface and dragged to FCP interface, upon which their proxy versions, together with marker metadata are added to the FCP timeline. The users, after finishing their edit on the interface, then can switch the proxy versions of the videos with the hi-res versions with a control on the FCP Client. The files rendered from the timeline can be ingested automatically back into the MAM. The features provided with the MAC client are limited with above.
Please see Mac Client for more information
SERVER SIDE components
...
Metus Archive Server
MAS is the server side component that is the glue that holds the system together. It manages the storages that are defined in the system. It sits between the clients, the database, and the other server side components and regulates the media and data traffic. It manages media traffic, in accordance with the security levels of the assets and access rights of the users. It handles the archiving process (of moving and distributing the imported files between defined storage/s) and delivers the file path to the client, with the necessary access level enabled. This file access mechanism prevents MAS from becoming a bottleneck in the system. MAS also handles the media life cycle of assets according to pre-set rules, and shuffles the archived files between the various online and nearline storages. And, it can function as a backup for other servers.
...