You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now, a full render consists first of a scene render (similar to the PR render; which may/may not render all the images, just those specified in config.yaml), and then an edit render, where the images are compiled with sounds and other post-processing effects into a video file.
We need to cache the images to a separate S3 bucket location. Furthermore, PR/Scene renders should have the ability to tell what frames are already in cache to be able to honor the config option force_update for a specific frame.
Action Items:
set up s3 bucket to be able to upload to them
ability to read bucket to see what frames exist
ability to download bucket for full/edit renders
see what's there, render what's needed
The text was updated successfully, but these errors were encountered:
As of now, a full render consists first of a scene render (similar to the PR render; which may/may not render all the images, just those specified in config.yaml), and then an edit render, where the images are compiled with sounds and other post-processing effects into a video file.
We need to cache the images to a separate S3 bucket location. Furthermore, PR/Scene renders should have the ability to tell what frames are already in cache to be able to honor the config option
force_update
for a specific frame.Action Items:
The text was updated successfully, but these errors were encountered: