On 08/02/2013 at 19:14, xxxxxxxx wrote:
R14's support for Alembic has done wonders for our ability to make it a real pipeline citizen for us (at Mirada). We're now able to share cameras, models and animation seamlessly between Maya, Houdini, Cinema4D and (shortly) Max - but want to refine how C4D shares its data.
To that end, I'm trying to identify how to control the export options. I was able to reverse-engineer the format ID and have it successfully writing Alembic files - but without much control, and the API documentation is completely silent on Alembic.
I'm generally interested in being able to preserve the heirarchy (it currently shares a single mesh, compacted from the entire element being written), but other typical controls like frame relative sampling, frame interval and such are fairly essential to maintain parity with our other applications. I see a number of ABCEXPORT_ constants but am unsure where I should make use of them and how to provide the additional data that Alembic will make use of.
Anyone have some unreleased documentation or sample code for passing additional parameters to the Alembic exporter?