Blender Git Commit Log

Refactor Alembic data reading

The logic to read data is now separated from the AlembicObject and moved to a
separate file to help separating concerns.

We use structures to gather which data to read from the Alembic schemas. Those
structures are a bit redundant with the actual schemas, however they allow us
to read data of one schema type as if it were of another type. For now this is
only used to treat subdivision objects as regular polygon meshes, but in the
future it could be used to treat curves or meshes as point clouds when rendering
points is supported.

This centralizes the logic to read data based on the frame range. Instead of
writing one loop for each schema type and requested attributes, we only have
two functions which abstract the logic to gather the relevant frame times and
to lookup the right sample for the time. It would be nice to go a step further
and only have a single entry point, but the differences in handling between
attributes and regular data makes this a bit tricky but not impossible. Those
loops also handle setting up the time sampling information in the cache to make
sure that we never forget to do so, as this was quite a source of bugs.

This solves a few design issues, and allows to deduplicate data across frames
for all types (thus reducing memory usage) and to read arbitrary attributes for
polygon and subdivision meshes. The code for curves attributes is already in
place, but will not work, that would have to wait until example files are made
available. For attribute types, we support bool, int, float, vectors, and colors.
If need be we could also support matrices and quaternions.