This documents describes MVR v1.5. You may want to view the latest version 1.6.
Introduction
In the entertainment industry, the MVR file format allows programs to share data and geometry for a scene. A scene is a set of parametric objects such as fixtures, trusses, video screens, and other objects that are used in the entertainment industry.
In the entertainment industry, the MVR file format allows programs to share data and geometry for a scene. A scene is a set of parametric objects such as fixtures, trusses, video screens, and other objects that are used in the entertainment industry.
All objects used have a persistent unique ID to track changes between the exchanging programs.
Typical workflow
- Program A saves an MVR file containing a scene;
- Program B imports this file;
- Program B changes some parametric data in the scene;
- Program B saves an MVR containing the scene;
- Program A imports this file and applies the changes to the existing objects.
Definition
An MVR file is a ZIP archive file containing one Root File named
GeneralSceneDescription.xml, along with all other files referenced via this Root File.
- The archive must not use encryption or password protection.
- All files referenced by the Root File shall be placed at the root level. They shall not be placed in folders.
- Files shall be placed using either STORE (uncompressed) or DEFLATE compression. No other compression algorithms are supported.
- Files may be placed into the archive in any order.
- A
Universal.gdtffile can be added as template GDTF to define Gobos, Emitters und filter to reference. - Filenames within the archive must not differ only by case. Eg it is prohibited to have the files
GEO1.glbandgeo1.glbwithin the same archive.
The file name of the ZIP archive can be chosen freely. The extension is:
*.mvr
Example of a typical MVR archive:
GeneralSceneDescription.xml
Custom@Fixture1.gdtf
Custom@Fixture2.gdtf
geo1.3ds
geo1.glb
Textr12.png
Universal.gdtf
References: