diff options
author | Richard Antalik <richardantalik@gmail.com> | 2020-03-19 02:05:18 +0300 |
---|---|---|
committer | Richard Antalik <richardantalik@gmail.com> | 2020-03-19 02:07:30 +0300 |
commit | 348d2fa09e0c01d62372f5999b62d06ac3b810f9 (patch) | |
tree | 36186498cb951601478819b8aceb01fbb7c9b879 /source/blender/editors/animation | |
parent | c8b4b4c0fa3b1255a79b90393ee9f5ddb2ec35e9 (diff) |
VSE: Disk cache
This patch implements dumping images from cache to HDD.
The main goal of this system is to provide a means to achieve consistent playback speed mainly for strips that are not possible to preview in real time.
How to use:
Disk cache has own settings in user preferences for path to storage, size limit and compression level.
To use disk cache, you need to check `Use Disk Cache` box, set `Disk Cache Directory`, `Disk Cache Limit` and save or open existing .blend file.
By default sequencer output will be cached only. Manual setting is possible in cache panel.
Uses:
- Replacement or alternative for proxies. Disk cache will work with any strip type, supports float images as well.
- Storage for strip thumbnails.
- Less RAM needs to be allocated for preview cache
How it works:
Disk cache is extension of RAM cache. Every image, that is stored or deleted in RAM will be stored or deleted on HDD as well. Images can be compressed to save space and for use on slower drives. Compressed images are slower to write and read though.
Images are stored in bulk of 100 rendered frames per one file. This is to overcome slow file access time for large amount of files. Drawback is, that if one frame needs to be redrawn, all 100 frames are deleted.
Reviewed By: sergey
Differential Revision: https://developer.blender.org/D5524
Diffstat (limited to 'source/blender/editors/animation')
0 files changed, 0 insertions, 0 deletions