2 ms·
> Disk resources are equally vast, with a DiskFam of around 260 gigabytes of on-line storage containing approximately 140,000 digital image files. The 140'000
by BasilPH 4y ago
> Disk resources are equally vast, with a DiskFam of
around 260 gigabytes of on-line storage containing approximately 140,000 digital image files.
The 140'000 image files would translate to an 80 minute runtime at 30 fps. So I assume that's all the storage they had.
Makes me think of the day when my friend brought a 256MB USB stick to school and we were blown away.
- aidenn0 4y agoFilms are 24fps. Also, the first time I saw an SD card, I felt like I was in a Gibson novel.
- BasilPH 4y agoYou're right. That's what I found in the Wikipedia article[^1]: > The film required 800,000 machine hours and 114,240 frames of animation in total, divided between 1,561 shots that totaled over 77 minutes. This comes out to 24 FPS. The article talks of 140k frames, but it looks like they didn't use all of them for the final movie. [^1]: https://en.wikipedia.org/wiki/Toy_Story https://en.wikipedia.org/wiki/Toy_Story
- dagmx 4y agoMany shots are left out by the time a film is finished and every shot has multiple iterations in each of many departments that touch it. This post has an example diagram of a feature film pipeline. https://www.gfx.dev/python-for-feature-film https://www.gfx.dev/python-for-feature-film Toy Story would have been more rudimentary and ad hoc, given how early it was, but this is generally the same pipeline that’s been in use even for old hand drawn animated films.