Postlab Drive uses a cache file to manage and serve data. This cache acts as a warehouse:
When downloading a file, its chunks are stored in the warehouse, ready to be served to your NLE.
When you upload a file, it's moved into the warehouse, broken down into chunks, ready for transport as soon as there's bandwidth available.
Once the warehouse is full, and there's room needed, the oldest chunks are removed from cache.
Once there's room, new file chunks are brought in.
Postlab functions as the warehouse manager, and stores file chunks on a FIFO basis: first in, first out. However, sometimes you need files to remain in cache, which you can do by pinning a Bookmark. Use cases for pinning are to force a folder of media to stay available locally or to automatically download files others upload. Also, when your connection has too much latency to let you scrub fluidly enough, pinning helps.
To keep a folder cached, you can pin a Bookmark. Pinning fully downloads a folder's contents into the cache, and flags it as not to be removed. This ensures those files stay on your local computer, instead of having to (re)download them. To keep room for non-pinned files and uploads, Postlab allows 80% of the cache to be used for pinning.
In Postlab, create or open a
Production go to
[➕] at the bottom of the Drive panel, then select
Select the Folder on Postlab Drive to Bookmark.
Click the pin next to the Bookmark to pin that folder.
Pinning is a local feature, meaning you can't decide for other team members that a folder is to be pinned.
To make your cache completely available again, when for instance needing to upload a lot of media, it's possible to clear all pinned files in one go. Go to
Preferences... → Drive → CACHE SIZE and click
Clear all pins. All pins for the currently connected Drives will be cleared, on your computer only.
Current Location to a folder on a fast, local disk. Possible cache locations may include:
An internal SSD
An external SSD
A RAID configured for high-performance use
Using drives with spinning platter disks (measured in RPMs) or solid-state hybrid drives (e.g. SSHD's or Fusion Drives) will result in slower Drive performance.
If Postlab Drive's cache file is like a conveyor belt, this is where you specify how long the conveyor belt will be. You do this by specifying the
Current cache size on your local Mac.
Current cache size by:
Using the slider
Entering a value in GB
Currently, you can set the Cache Size on your local Mac up to 1000 GB, or 1 TB.
Drive LOVES cache. The more the better. The larger your cache, the less data has to be redownloaded, so give it all you can spare. If Drive is essential to your workflow, we recommend dedicating a 1TB external TB3 NVME disk to the cache.
You can't have a too large cache, so feel free to set it to more than you have free space left. Drive will handle it gracefully, don't worry.
NEVER put your Drive cache on a network drive. No, also not on a Jellyfish's Cache share. 10GE only gets you so far, and it's nowhere near the 3000MB/s Apple SSDs give you.
Uploading huge files? Make sure your cache is larger than the largest file you're uploading. Uploading a 25GB file with a 20GB cache will not work.
Changes are applied the next time you connect to your Team's Drive. If you change settings while a Drive is connected, reconnect it to apply your changes.
If you don't have enough space for your cache, and would like to enlarge it to ensure more files are kept in cache, you can move a cache:
.drivecache file to an external drive. The faster the drive, the better!
Launch Postlab, then go to
Preferences... → Drive.
Set the cache location to the new disk, and increase cache size.
If the last step doesn't work after moving the cache, delete the cache and Postlab will build a new one.