Focus Pan/Tilt attributes

[ebkgne]

At the moment you can only pass a UUID for a FocusPoint, but it would great to have Pan & Tilt too .as ni some cases you'd need one FocusPoint per fixture ....

thx

[LxLasso]

Just having a pan and tilt value doesn't really work because it needs to be relative to something. You will also be missing out on axial orientation.

Unfortunately the orientation of fixtures in an MVR is largely undefined at the moment. Someone would have to spend the time on understanding how fixtures are oriented in the relevant softwares on the market and then write down a solution that makes it possible to transport this information between all these softwares in an unambiguous way (if that's even possible). At the moment MVR is simply tailored to VectorWork's needs and it matches other softwares' needs poorly.

[moritzstaffel]

Unfortunately the orientation of fixtures in an MVR is largely undefined at the moment. Someone would have to spend the time on understanding how fixtures are oriented in the relevant softwares on the market and then write down a solution that makes it possible to transport this information between all these softwares in an unambiguous way (if that's even possible). At the moment MVR is simply tailored to VectorWork's needs and it matches other softwares' needs poorly. The position and orientation of a fixture is defined by the GDTF linked by the GDTF. This also defines all the other stuff. So the work on this is already done.

To transfer pan and tilt orientation, you currently need use focus points. For the next MVR version we want to support Pan and Tilt like @tourkit has proposed.

I think MVR works fine if you use GDTF with it to express the definition of the fixtures.

[LxLasso]

As you know GDTF is unusable for us in its current state.

What do you intend to make pan and tilt relative?

[moritzstaffel]

The MVR Pan Tilt will be based on the GDTF definition for the Pan and Tilt functionality.

We are currently thing about making them percentage based to that you can use the GDTF Channel Function to calculate the Pan/Tilt or that you can give an absolute value.

That approach is similar to the support of OSC that we have added to GDTF1.2.

All the definition is already in the GDTF. MVR and GDTF are designed to work together. So only together they give you the full feature set.

[RichardTea]

Well, that doesn't work for anyone at all then. Not even Vectorworks :(

As Lars and many others have said many times, it will never be the case that every fixture in an MVR will have a valid GDTF description. Even the demos at PLASA didn't. The more things that require a full GDTF, the less useful MVR becomes.

[LxLasso]

As long as the whole concept is based on the idea of all softwares involved natively relying on GDTF files it's all rather shot I'm afraid. It might be a vision for the future, but here and now it renders MVR a pretty pointless exercise. If it wasn't the only way of reading designs from VectorWorks or getting patch into MA3 we wouldn't have touched it.

[moritzstaffel]

MVR and GDTF are designed to work together. Just using MVR is like using a car without engine.

GDTF has all the technical information to do the Pan and Tilt features, even when you don't use GDTF as native fixture type in the software, you can calculate the resulting Pan and tilt.

In ChamSys, MA3, Vision and Vectorworks software product the GDTF exchange works pretty good.

[moritzstaffel]

Implemented by the 1.5 MVR Version