Productions
In medialoopster productions are used to manage a closed pool of content.
The medialoopster system can have local installations in multiple premises, and multiple productions per such installation. An installation is considered on one geographical location with a LAN for which the site is recommended to be unique, thus multiple productions within the same installation are recommended to share the same site (settings.SITE_ID=1).
Within each production preferences determine storage paths and default devices. Furthermore assignments to sites as well as user and group permissions are controlled there.
Assets within a production must have unique names, but you can create the same asset in different productions or share the assets between these productions.
It is not recommended to delete productions, as the assets within will become unusable.
Options
Name | Required | Description | |
|---|---|---|---|
| Name | Yes | The name of the production. Also used for display on the browser interface. | |
| Codename | Yes | A unique short name used for task routing. It MUST NOT contain special or whitespace characters. | |
| Company | Yes | Reference to the company instance. | |
| Direct attached site | Yes | The direct associated site for this production. | |
| Network attached site: | No | Any other medialoopster site that is available through network routing. | |
| Storage root | Yes | The root path where the production's assets will reside, as seen by medialoopster, for example /mnt/medialoopster/nb/. The path MUST exist. | |
| Yes | The default mount path where the shared storage is mounted on NLE clients. Regardless of the clients OS this path should use forward slashes as path separators and it also requires a leading slash e.g. /Z:/shared-storage/ | ||
| Proxy root | Yes | The root path where the generated proxies will reside, as seen by medialoopster, for example /mnt/medialoopster/Proxy/nb/. The path MUST exist. | |
| Proxy url | Yes | The root url of the website that delivers the proxy material, for example http://ml-mycompany-media/nb/. | |
| Upload device | Yes | An intermediate device where media files will be placed after being uploaded through the browser interface. From here the files will be moved to it's final device according to it's detected asset type. | |
| Audio/Image/Video asset device | Yes | Default device for audio/image/video essence. | |
| Export type | Yes | The file type to be used at "Open list in editing system" on a favorite items list, to export the video assets information. Can choose between XML for Adobe Premiere and Apple Final Cut Pro 7, AAF for Avid Media Composer and FCPX for Apple Final Cut Pro X. | |
| Asset Hold Duration | No | Lifespan of an asset within medialoopster. The deletion date of new assets will be set according to these settings. You can assign a duration (in weeks) to each asset type. A value of 0 or not assigning a duration at all means, that type of asset will not obtain a deletion date automatically. The values assigned here can be overridden at device level. | |
Production user/group membership | - | Permissions on the production. By default no user or group has access to the production. Every PUM or PGM adds read access to the production. | |
| Has write access | No | Check that the user/group has write access as well, in addition to read access. | |
| Has delete access | No | Check that the user/group has delete access as well, in addition to read access. | |
| User/Group | No | Select the user/group. | |
| Export devices | - | For sharing assets asynchronously with a target production. | |
| Target production | No | The name of the target production. | |
| Device | No | The device of the target production where to intermediately copy the high resolution essence from the source production. From there, an asset will be created within the target production on a final device via watchfolder periodic tasks. | |
Never forget the trailing "/" for paths. This is important for path inclusion comparisons.
If there is only one production on the local installation, you can safely remove the <codename> from the paths.