Questions
Last updated
Last updated
Set Drive's Cache Location () to a dedicated SSD or NVMe disk, whether internal or external over Thunderbolt 3/4.
with this File System and Partition Map:
File System: APFS (Apple File System)
Partition Map Type: GPT (GUID Partition Table)
SSD or NVMe disks formatted as HFS+, macOS' legacy file system, won't yield as much performance as APFS.
Using disks formatted as ExFAT file systems with MBR (Master Boot Record) partition maps are unreliable for caching, and overall much slower than APFS-formatted disks. If you're using an ExFAT volume for Drive's cache, back up any other data on that disk, then reformat it as APFS with GPT.
Generally, Drive won't eject when one or more of these situations apply:
Preferences > Drive > CACHE LOCATION) isn’t suitable for PostLab Drive.Energy Saver settings allow your Mac to sleep or for disks to spin down.Since your Mac treats Drive like another local disk, letting your Mac put your hard disk to sleep while Drive is connected is like pulling the cables from a hard drive or improperly ejecting a Drive while an operation’s in progress.
To prevent this from happening, modify your Energy Saver settings to:
Computer Sleep: Never
Put hard disks to sleep when possible: DISABLED
Causes may include one or a combination of:
An ISP outage at your location. That outage could be sustained over time or intermittent.
Your Mac can't connect to your ISP's DNS servers.
Another local area networking issue (e.g. power cycling your local network hardware).
Connecting your computer to the public Internet over Ethernet (hard-wired, cabled) is a quick way to improve stability and performance and reduce the unpredictability of your computer’s network connection.
This error means macOS couldn't clean up a previous mount point.
Restarting your computer usually solves it, but the manual fix is also simple:
In Finder, make a new window.
Press Shift-Command-G.
Go to /Volumes.
Look for an empty Drive folder and delete it (macOS Administrator account password required).
Go back to PostLab, and connect Drive.
Drive by itself doesn't need speed as there's little to no overhead, but your media's data rate can of course outpace your connection's download speed making live playback from the cloud impractical. The best way to handle that is a proxy workflow, to minimize the data rate of your media. If that is not possible, simply drag files from Drive to your hard drive. That will trigger a full file download, which you can do overnight.
Delete Premiere Pro's Media Cache files, then see if playback improves.
Unfortunately, Adobe changed the process of deleting Premiere's Pro Media Cache between Premiere Pro 2019 and 2020. Use these videos from Adobe to quickly determine how best to delete the Media Cache for your version of Premiere Pro.
First, check or for status updates. If all services report running at 100% within the past 24 hours and there are no other status updates, then something local to your network is likely interfering with PostLab’s performance.
Also, you can use the to help you diagnose connection issues with PostLab from your location.
(Help > Request Support) and we'll be in touch.
Are you on macOS 15 (Sequoia)? Then and install the LucidLink client first, to add support for Drive on this version.
If this happens again on the same computer, there's most likely a permissions issue. .