Method and system for recording information about rendered assets
Systems and methods presented here allow recreation of prior scenes, even if assets used in the scenes have evolved over time. The systems and methods employ query of a database to obtain data for backup and retrieval, e.g., information about shots made at prior points in time, where a “shot” refers to a scene or associated set of sequential frames (a single image may also be considered a shot in some instances), rendered or not depending on context. In the VP-VCR systems and methods, information may be obtained about rendered scenes which allow knowledge and subsequent use of each asset employed in the scene, including its proper version and representation at the time of the rendering. Such may be employed not only to obtain prior versions of shots, but also to allow modification of assets in prior shots to obtain new effects.
1. An improved method of storing data about a composite product, the composite product including a plurality of assets, at least one of the plurality having associated version information therewith, comprising:
receiving a command to render a model file indicating a desired composite product, the composite product being a shot in a video, the model file indicating one or more computer graphics assets and respective version indicators constituting the composite product;
locking each asset referenced by the model file against modification, so that the one or more computer graphics assets are included in the rendering as they were at a time of the receiving a command to render a model file, and not as later modified;
rendering the model file and during the rendering, recording calls to a versioning and publishing application programming interface (API), the versioning and publishing application programming interface (API) enabling access to registered assets; and
during the rendering, monitoring calls to an operating system to record data about at least one file opened by an application associated with the render, the at least one file not referenced by the versioning and publishing application programming interface (API), and storing data together in a file from the recording calls to the versioning and publishing API and from the monitoring calls to an operating system,
wherein a use of the model file allows retrieval of prior versions of assets, locked in the locking step and referenced by the model file, that have been subsequently modified.
2. The method of claim 1 , wherein the command is received from a graphical user interface (GUI) including a viewer, the command associated with a model file viewed on the graphical user interface (GUI).
3. The method of claim 2 , wherein the command is associated with a rendering session.
4. The method of claim 3 , wherein the session is associated with a path for the rendered file.
5. The method of claim 1 , further comprising restoring the model file from a queue archive.
6. The method of claim 1 , wherein at least one of the assets indicated by the model file is indicated by a special reference (SPREF).
7. The method of claim 1 , wherein the version indicator is a number or is associated with one or more “published”, “latest”, “current”, or “approved” or arbitrary reference indicators.
8. The method of claim 1 , wherein the recording data is performed at an operating system level.
9. The method of claim 1 , further comprising comparing the recorded calls with the recorded data for debugging.
10. A non-transitory computer-readable medium, comprising instructions for causing a computing environment to perform the method of claim 1 .
11. An improved method of restoring a composite product, the composite product including a plurality of assets, at least one of the plurality having associated version information therewith, comprising:
upon receipt of a command to restore a shot including computer-generated (CG) assets constructed in a model file within an application, restoring the model file;
displaying a first list of assets associated with the model file, the model file including a list of assets including assets accessed using a versioning and publishing application programming interface (API) stored together with a list of assets accessed not using the versioning and publishing application programming interface (API), the assets on the list accessed not using the versioning and publishing application programming interface (API) determined by monitoring calls to an operating system;
modifying the displayed list of assets based on user input and displaying a second list of assets, the second list of assets different from the first list of assets, such that a subsequent rendering uses assets in the second list; and
rendering the composite product based on the model file and the displayed assets,
wherein a use of the model file allows retrieval of prior versions of assets that have been subsequently modified.
12. The method of claim 11 , wherein the displaying includes displaying a product lock table.
13. The method of claim 12 , wherein the product lock table includes data about each asset called by the model file, including a version indicator of at least one product, and further comprising resolving the version indicator by finding a first existing version indicator.
14. The method of claim 12 , wherein the product lock table includes data about each asset called by the model file, including a version indicator of at least one product.
15. The method of claim 11 , further comprising retrieving the model file associated with the assets from a queue archive database.
16. The method of claim 11 , further comprising, during the render, storing a path of each asset called by the model file.
17. The method of claim 11 , further comprising saving a record of a version of the application.
18. The method of claim 11 , further comprising, after the displaying and before the rendering, receiving user input modifying an asset in the displayed list.
19. A non-transitory computer-readable medium, comprising instructions for causing a computing environment to perform the method of claim 11 .