Alembic > Export

Exports either all objects or selected objects to an Alembic cache file.

Alembic > Export All in Alembic > and Alembic > Export Selection in Alembic >

Opens the Alembic Export window from which you can set options for exporting Alembic files. Selecting Export All in Alembic exports all polygon, NURBS, and subdivision objects in the scene to an Alembic file. Selecting Export Selection in Alembic exports selected objects to an Alembic file.

General Options

Cache time range

Render Settings: Specifies that your current Render Settings determine the Cache Time Range.
Time Slider: Specifies that the current playback range in your Time Slider determines the Cache Time Range.
Start/End: Specifies that the range of frames between (and including) the specified Start and End times determines the Cache Time Range.
Start/End: These fields let you specify a Start and End time for the Cache Time Range.

Evaluate every: When creating an Alembic file, one sample of your object's transformations is taken every frame and saved to the Alembic file by default. Evaluate every specifies how often samples are taken during file creation. For example, a value of 2 caches the transformations of the current object at every other frame of the Cache Time Range.
Pre Roll Start Frame: Specifies at which frame to start the scene evaluation. Use this option to set the starting frame for time dependent translations that require run-ups

Advanced Options

Don't Skip Unwritten Frames: Evaluates every frame regardless of whether or not there are changes in object translation values between frames.
Verbose: Outputs frame number information to the Script Editor or output window.
No Normals: When on, normal data from the original polygon objects is not included in the exported Alembic cache file.
Renderable: When on, any non-renderable nodes or hierarchy, such as hidden objects, are not included in the Alembic file.
Strip Namespaces: When on, any namespaces associated with the exported objects are removed from the Alembic file. For example, an object with the namespace taco:foo:bar appears as bar in the Alembic file.
UV Write: When on, UV data from polygon meshes and subdivision objects are written to the Alembic file. Only the current UV map is included.
Whole Frame Geo: When on, geometry data at whole frames is sampled and written to the file. When off, geometry data is sampled at sub-frames and written to the file. This is the default setting.
World Space: When on, the top node in the node hierarchy is stored as world space. By default, these nodes are stored as local space.
Write Visibility: When on, the visibility state of objects is stored in the Alembic file. Otherwise, all objects are considered visible.

Callbacks

A recommended way to use callbacks with the Alembic export, is to first define a global procedure. For example, in the Script Editor, define the following:

global proc perFrameCallback(int $frame) 
{ 
    print $frame; 
}

The full MEL callback is then:

perFrameCallback(#FRAME#)

Note

For correct syntax, callback commands cannot contain the following:

Spaces between characters. For example, ( ).
Single quotes. For example, (').
Double quotes. For example, (").

Per Frame Callback MEL: When each frame is evaluated, the string specified is evaluated as a Mel command. For example, print("#FRAME#").
Post Job Callback MEL: When the translation has finished, the string specified is evaluated as a Mel command. For example, print("Done!").
Per Frame Callback Python: When each frame is evaluated, the string specified is evaluated as a python command. For example, print("#FRAME#").
Post Job Callback Python: When the translation has finished, the string specified is evaluated as a python command. For example, print("Done!").