Open mkolar opened 3 years ago
Is the end goal to output a format that is cross host compatible?
Haven't seen any library that tackles something like this. Only know of these:
https://github.com/Toolchefs/kiko https://github.com/Autodesk/animx
We might have a need in the near future for something like this, but one requirement which I thought would be useful to add here is to be able to read the format outside of the host.
Ultimatelly it would be great to have something cross-host, but for starters we keep getting requests for Studio Library format specifically.
We have an existing library (Studio Library) which we would like to ingest into Ftrack, so we can use Ftrack to tag and search for metadata, so a way to "publish" or "sync" a studio library folder would be good as well but that is probably just a script job.
What is more important is for us is tagging. Is this something the Pype Team has looked at before? Initially thinking that we would just use Ftrack for tagging (if possible) and use as a front end for everyone to be able to see but I guess it would be good to later have that data in MongoDB.
We need to implement support for publishing and loading animation curves, that can be shared across shots, or possible even shows. The ultimate goal is for the artist to run publish on an animation scene, which will extract alembic cache as we do now (optionally), but also animation clip that can be loaded using our Loader, Library loader and a new animation library GUI.
Multiple studios have suggested sticking to Studio Library format, for now considering its wide adoption. This is probably a good idea considering there's not a huge need at the moment for cross host compatibility of this data, even though ultimately that should be our target.
[cuID:OP-1531]