Hedge
Search…
Questions

How do I reset my password?

You can request a password reset here: https://postlab.cloud/password

Does Postlab need certain permissions to run on macOS?

Yes, Postlab requires access to macOS' Accessibility.
Upon its first launch, Postlab prompts you to allow access to:
  1. 1.
    System Events - click OK.
  2. 2.
    Accessibility - click Enable Accessibility.
System Events
Accessibility
If you're using Final Cut Pro or Premiere Pro, the first time you Upload Your Work or Discard Changes, Postlab prompts you to allow access to System Events for your host NLE.
Once those three permissions are set, Postlab is ready to go.

What if I don't enable these permissions?

If you don't enable these permissions, Postlab may not work as expected, as Postlab can't open or close NLEs and can't observe changes made.
If you happened to dismiss these system alerts, you can at a later time manually enable these permissions in System Preferences > Security & Privacy:
  1. 1.
    Accessibility
  2. 2.
    Automation
Avid Media Composer Teams will not see Avid Media Composer listed under System Preferences > Security & Privacy > Automation > System Events.

Where should I store my media?

You can store both your proxy and original media on Postlab Drive. Team Members can then (re)link to those assets, just as you would expect using shared storage in a facility. With larger media, Pinning a folder on Drive ensures files aren't re-downloaded to your Drive Cache.
You can also use Postlab Drive along with other locally attached storage and/or network attached storage. Final Cut Pro teams can take advantage of Postlab's Relink Prevention feature by defining the MEDIA LOCATION for Libraries added as Documents to a Production.

Where should I store Postlab's caches?

In Postlab there are 3 categories of caches:
  1. 1.
    Productions - Preferences > General > DEFAULT PRODUCTION LOCATION
  2. 2.
    Drive - Preferences > Drive > CACHE LOCATION
  3. 3.
    Your host NLE - Final Cut Pro, Premiere Pro
Store these caches on a dedicated SSD or NVMe disk, whether internal or external over Thunderbolt 3/4.
In Final Cut Pro, set your Library's Cache to a folder outside your Library.
For Premiere Pro, if you're using Projects with Postlab Productions, Postlab creates Scratch Disks for you in the same folder where your Productions are cached (Preferences > General > DEFAULT PRODUCTION LOCATION).
Do not store Postlab's caches on:
  • A spinning disk or a RAID with spinning disks.
  • Solid-state hybrid drives (e.g. SSHD's or Fusion Drives).
  • Shared storage - network attached storage (NAS), a storage area network (SAN), or cloud storage (e.g. Postlab Drive).

I installed or updated Postlab and get a Missing Components error.

Missing Components
This is not something destructive, and easily remedied. Although in most cases it's caused by conflicting installations of developer tools, the remedy doesn't interfere with other apps and only touches Postlab.

Latest Release

  1. 1.
    In the Missing Components dialog, click Quit.
  2. 2.
    Redownload the latest release if you trashed it after installing Postlab.
  3. 3.
    Remount the Postlab Installer DMG.
  4. 4.
    Re-run the Installer.
  5. 5.
    Relaunch Postlab.
If you run into this often, reach out.

How do I move my Media and/or Cache outside my FCP Library?

Before Postlab, one or more of your Library's Storage Locations were likely set to In Library. With Postlab, nothing goes in the Library. This keeps your Library as lean as possible for quickly importing Libraries or uploading changes to Postlab.
When importing or uploading a Library, Postlab will detect if any of these exist in your Library:
  • Cache, which includes these folders:
    • /Render Files
    • /Analysis Files
  • Original Media
  • Proxy Media
  • Optimized Media
Here's how to move and/or remove these.

Cache

In FCP, select your Library in the Libraries sidebar, go to the Inspector.
Next to Storage Locations, click Modify Settings.
If Cache is set to In Library, choose a folder outside of your Library on a high-performance local drive.
Do not store a FCP Library's Cache on shared storage, whether it's network attached storage (NAS), a storage area network (SAN), or cloud storage (e.g. Postlab Drive).
FCP will ask you to confirm: Do you want to move your render files? You can Include your current cache to be moved to this new folder, or Don't Include and FCP will create a new cache there.
Once you decide, click one of those options, and your Cache will be outside your Library.
Afterwards, go back to Postlab and import or upload your Library.

Original, Proxy, and Optimized Media

FCP's Consolidate feature lets you move media inside a Library to a destination folder outside the Library.
In FCP, select your Library in the Libraries sidebar, then go to the Inspector.
In the Media section, click Consolidate.
In the Consolidate Library Media dialog, select the media you'd like to move based on the media types you're currently using:
  • Original media
  • Optimized media
  • Proxy media
If you try consolidating a media type that doesn't exist in your Library, FCP will offer to Transcode media of that type, or you can Continue with the consolidation.
A folder for each media type will appear in the location defined in Library > Storage Locations > Media, which should be outside your Library.
Afterwards, go back to Postlab and import or upload your Library.

Manual Removal

In some cases, you may need to move or remove these files or folders from your Library manually before importing or uploading to Postlab.

Method 1

This requires deep digging into your FCP Library (.fcpbundle) so be sure to make a backup of the Library before proceeding!
  1. 1.
    With your Library open from Postlab, in FCP, select your Library in the Libraries sidebar, then choose File > Reveal in Finder (or press Shift-Command-R).
  2. 2.
    In Finder, duplicate your Library (.fcpbundle) to another location (e.g. your Desktop) outside the .postlab bundle.
  3. 3.
    In the .postlab bundle, right-click on the Library, then choose Show Package Contents.
  4. 4.
    Locate these folders, then move them to the Trash:
    1. 1.
      Render Files
    2. 2.
      Analysis Files
  5. 5.
    In Postlab, try importing your Library into your Postlab Production.

Method 2

If that feels a bit too surgical, here's an alternative method:
  1. 1.
    In Postlab, create a new Library in your Production, then Start Editing.
  2. 2.
    In FCP:
    1. 1.
      Set your Library's Storage Locations. (Remember: nothing goes In Library.)
    2. 2.
      Open the Library you couldn't import into Postlab, then drag-and-drop all Events into the newly created Library you opened from Postlab.
  3. 3.
    Back in Postlab, upload the newly created Library.
This method won't preserve the Activity Log in the former Library. You can either keep the former Library in your Production until it's no longer needed or retry Method 1. Still having trouble? Reach out.

Why won't Premiere Pro launch when I Start Editing my Project?

Currently, Postlab supports these versions of Premiere Pro:
  • 2019 (13.1.5)
  • 2020 (14.x)
  • 2021 (15.x)
  • 2022 (22.x)
If Premiere Pro doesn't launch, you likely have an unsupported version installed on your workstation. Remove the older versions of Premiere Pro, then Postlab will launch.
Have multiple versions of Premiere Pro installed? Postlab will also detect those, then prompt you to launch the desired version.
Change Default Project Version takes you to Preferences > Templates. Then you can set which Premiere Pro Project version will be used as the DEFAULT EMPTY PROJECT when adding Projects as Documents to a Production.

Which services are required to use Postlab from my location?

Here's a complete list of services, hostnames, IP addresses, and ports needed by Postlab. If your network is behind a firewall and can't reach some of Postlab's services, you may need to:
  1. 1.
    Add these services to your allowed lists.
  2. 2.
    Disable deep packet inspection (DPI) for these services.

Services using non-standard ports

Service
Hostnames
IP addresses
Ports
Postlab Core - San Francisco
gl-sf-01.postlab.cloud
167.99.171.165
8443
Postlab Core - Amsterdam
​gl-ams-01.postlab.cloud
128.199.41.247
8443
Postlab Core - New York
gl-nyc-01.postlab.cloud
167.172.137.156
8443

Services using standard ports

Service
Hostnames
IP addresses
Ports
Airtable (database)
api.airtable.com​
443
Postlab user API
postlab.cloud
188.166.121.40
443
Postlab server API
toren01.postlab.cloud
134.209.198.20
443
Postlab update service
sparkle.postlab.cloud
178.128.251.17
443
Postlab documentation
docs.hedge.video
165.22.35.90
67.205.137.100
443
Postlab Drive / Lucidlink
s3.wasabisys.com
443
Postlab Drive / Lucidlink
s3.us-east-1.wasabisys.com
443
Postlab Drive / Lucidlink
s3.us-east-2.wasabisys.com
443
Postlab Drive / Lucidlink
s3.us-west-1.wasabisys.com
443
Postlab Drive / Lucidlink
s3.eu-central-1.wasabisys.com
443

Additional Notes - Postlab Drive

Postlab Drive is built with LucidLink technology. Detailed information about LucidLink's network requirements can be found here: https://support.lucidlink.com/support/solutions/articles/31000053458-firewall-port-s-and-required-software-disclosure
Postlab Drive stores its data on Wasabi's servers. More information can be found here: https://wasabi-support.zendesk.com/hc/en-us/articles/360015106031-What-are-the-service-URLs-for-Wasabi-s-different-regions-