Saturday, 8 September 2012

NATIV MioEverywhere

Walked past the stand and Jon Folland was busy doing some workflow setup in the MioEverywhere product, and the screen caught my attention.

This web based product takes care of most requirements for media management in media companies. The architecture based system has many opportunity for expansion and customization, still retaining a solid core.

The main features as defined by Jon:

- Windows based remote ingest client that validates input file and Meta data against rules defined in the system. Ensure that media submissions meet your minimum requirements.
- The windows based client support restart and resume making it usable in low and unreliable bandwidth regions.
- FTP and mount point with folder monitoring is also supported.

Asset management
- Any submitted file is analised and media related information is stored in the fully searchable database. For example you are able to find media of a certain frame rate, length and aspect ratio.
- META data information is added to the database
- You can attach any other files to the main media file, which also is index into the database for full text searching
- A universal proxy version is created of all media to allow frame accurate manipulation of the media in the web interface.
- Frame accurate shot logging of media in the system is possible, for later re purposing.

Any process can be placed into a failure detecting workflow system. Should one part of the workflow fail, all submission int other workflow will run op to the point of failure and then wait. After repairs, one can resubmit or simple continue the queued workflow processes.

Workflow is used to achieve automated but also human tasks around media management and the options are unlimited.

Shown processes included:
- Rhozet Carbon Coder API level integration allows for job creation and processing of outputs
- YouTube submission automation
- VoD processing

Please visit for detail.

ProxMox Unprivileged LXC containers USB Drive

Some quick notes on bind mounting under ProxMox and getting the permissions right. Reference -