To whom it may concern:
I noticed that when importing an MVR my unit number is mapped, but my "position" is not mapped. In the United States lighting field, particularly in theater, we use the "position" to mean the "location" of the fixture. So the first electric (a batten on stage) would have a unique unit number per position, but not per plot. The "uniqueness" depends on the combination of the two fields. That's about as close to a UUID as possible in the workflow for most of our theaters.
Would it be possible to map this to the Location field in Capture? Location seems to be the equivalent and it would allow much easier bi-directional exchange with Vectorworks. As much as I would love to move to Capture for my plots--and I might: you have done a wonderful job recently with paperwork-scenery still requires parametric CAD software and Vectorworks makes the most sense for me at the moment and I would like to keep within the regional theater standards of numbering for our electricians.
This is less useful for checking my work, luckily my channels are unique.
I believe this might be a fundamental design flaw in the MVR file format, in the case of my file in the GeneralSceneDescription.xml I find:
{1.000000,0.000000,0.000000}{0.000000,1.000000,0.000000}{0.000000,0.000000,1.000000}{-5994.374570,-19853.605488,22737.494042} Blade3Rot.Blade3Rot.Blade3Rot,f 0.000000 Blade2Rot.Blade2Rot.Blade2Rot,f 0.000000 Blade4Rot.Blade4Rot.Blade4Rot,f 0.000000 Blade1Rot.Blade1Rot.Blade1Rot,f 0.000000 Blade3A.Blade3A.Blade3A,f 0.000000 Blade2A.Blade2A.Blade2A,f 0.000000 Blade4A.Blade4A.Blade4A,f 0.000000 Blade1A.Blade1A.Blade1A,f 0.000000 Yoke_Pan.Pan.Pan 1,f -2.935526 Body_Tilt.Tilt.Tilt 1,f 48.094321 Base_Zoom.Zoom.Zoom 1,f 8.000000 7A6EC634-F65F-42BE-A1C6-79C878BA4C92 Custom@ETC_Source_4_10deg.gdtf DMX Mode 2A817EB3-D6D9-4DD5-9942-C59914A4DB4A 0 603 26 0 0 0.299054,0.596594,44.620513 false
This then maps to:
Based on this, if the AUXData is present and contains Position information, I think that should be mapped to the Location field in Capture. I should also reiterate, this is a Vectorworks -> Capture workflow, but the MVR file format is missing a lot of critical data.
Also, for whatever it is worth, storing the meta-data of the UUID for export as plain text might allow for the development of custom workflows. Currently the "Identifier" does not seem to match up to the UUID in the mvr. I'm wondering if the UUID from the MVR should be mapped to the External Identifier on import? This would allow us to reconcile data between applications.