Regarding the Mocap Library app, I have looked into the theory behind Data Models and how to design an app around a database.
I will use MongoDB as the database back-end, with pymongo to connect the app to the database.
Here is my 'schema' which is the lingo for the Data Model.
.png)
What I have designed is a flexible, multi-purpose system that allows for a comprehensive range of clips for a VFX Crowd artist.
The first object is the mocap file. This can be from a mocap shoot, an archived file from a provious job, a purchased package from a third party (e.g. Mixamo).
The mocap file may contain more than one animation clip. So, this is an one-to-many relationship
The clip may or may not have a one or more props assiciated with it. The props can be associated with more than one clip. That's a many-to-many relationship.
The clip could have one or more transitions in it (e.g idle -> react -> run -> collapse). That's an one-to-many relationship.
The clip will be assigned to at least one rig. The rig will also have other clips associated with it. Another many-to-many relationship.
Lastly, a clip can be a Vignette and be associated with other Vignette clips. I believe this is a one-to-many relationship.
