Maya: implement matchmove publishing

[kalisp]

Changelog Description

Add possibility to export multiple cameras in single matchmove family instance, both in abc and ma.

Exposed flag 'Keep image planes' to control export of image planes.

Additional info

Switch to matchmove from camera family was chosen to don't break existing workflow where only single camera is expected (Houdini, Nuke). It is important to note, that alembic and maya scenes don't support identical feature, so it is possible to have richer matchmove data in .ma, compared to .abc format. For instance Image planes will not be preserved in .abc file.

Testing notes:

1.create multiple cameras in Maya
2. select all of them and Create matchmove instance
3. publish
4. try to load both via Reference (abc) and Referenca (ma), it should load all cameras (previously it would load only first camera even if you would select multiple for Creation step).

[ynbot]

Task linked: OP-6360 Maya: multiple cameras publish

[BigRoy]

Hmm - I don't think I'll be approving this from my end. This seems to go against the whole concept of what the camera family is designed to be.

This just seems off. The whole intent for the camera family is to be a single camera - or maybe also a stereo camera (technically two lenses) but even then I'd say it's likely better to make that a stereoCamera family to be explicit about the content.

What's the reason you need multiple cameras in a single camera instance as opposed to you just publishing multiple camera instances?

Or, if you want to put any amount of cameras into an instance without rules - why not use a pointcache instance?

The Houdini (loading) logic for example is also expecting it currently to be a single camera and I anticipate other hosts to be doing the same.

[kalisp]

Hmm - I don't think I'll be approving this from my end. This seems to go against the whole concept of what the camera family is designed to be.

I'll let @m-u-r-p-h-y or @antirotor reply to this. But thanks for valid concerns, I was expecting them.

[tokejepsen]

You could have a family called "cameras" that'll publish each camera collected as "camera" family.

[m-u-r-p-h-y]

Hmm - I don't think I'll be approving this from my end. This seems to go against the whole concept of what the camera family is designed to be.

I'll let @m-u-r-p-h-y or @antirotor reply to this. But thanks for valid concerns, I was expecting them.

If this family is meant for one camera only,(we should check if we have single camera only present) and we need a multicamera family to cover the use case of publishing dozens or even hundreds of cameras used for photogrammetry model reconstruction (including corresponding image planes).

(I could not find a better picture quickly to demonstrate it :)

[BigRoy]

Pointcache family can export any amount of cameras + include geo or locators if needed.

[kalisp]

Reattached image planes to original cameras (must have been wrong previously when testing).

[LiborBatek]

Now the ImagePlanes stays untouched in the active workfile but they dont appear in the Published asset of matchmove....

[LiborBatek]

Even tho now Publish produces correct data with all connected ImagePlanes and keyframes, there are few issues still.

1. Matchmove Instance' s Keep input connections does not have any effect when OFF
2. Cameras having different names when published...this could be possible issue in some use cases ...now there is suffix present _baked in the names
3. I propose to change the terms Camera (Alembic) and Camera (Maya Scene) in the matchmove instance to

Extract Alembic and Extract Maya Scene

[kalisp]

Removed copying of input connections as BigRoy mentioned couple of times it might be dangerous. Explicitly exposed only flag for control of exporting Image planes.

[LiborBatek]

Now all works as it should and matchMove asset being correctly produced with ImagePlanes just when Keep ImagePlanes being Enabled and vice versa.

There is also correctly publish Camera and its Scale if animated, so all good!

had been fixed and user is not acting