Questions

Is there a limit to the number of libraries that can be in a Team Bundle?

No, there is no limit. If a bundle becomes massive, you might want to split your projects amongst different Team Bundles depending on your organization and file structure. It's fine for a Team Bundle to be tens of gigabytes large.

My Team Bundle is growing quite large. Why is that and is there a way to reduce the file size?

Older Versions or Discarded Documents

Older versions of PostLab saved more and larger versions of your documents more frequently. Since we changed this behavior, Team Bundles no longer grow in size as quickly. However, older documents may still remain. There are a few options to get rid of them:

Start Fresh

Start a fresh Team Bundle; export the documents or collections you wish to transfer, create a new Team Bundle, and import the documents. Note that the document's version history will not be included in the transfer.

Attic

The attic is there to safe keep accidental discards. In your current Team Bundle; select a document and under 'File' in the menu bar, click 'Open Attic'. A finder window opens with all discarded versions of your documents in compressed `.aar' or '.zip' files. Remove any of the larger files.

Trash

It could be you removed documents or whole collections via the 'Move to Trash' option. These items aren't deleted immediately. They are in the trash for safekeeping. To empty the trash in PostLab, go to File > Open Trash to view the Trash. There you'll see a button that says "Empty". Clicking this button will empty the trash.

Final Cut Pro: Optical Flow Analysis Files

Another reason a Team Bundle could rapidly increase in size is due to 'Optical Flow analysis files' when editing with Final Cut Pro. When converting clips to a different frame rate in Final Cut Pro using 'Optical Flow,' large analysis files are generated in your Library. To manage these files, avoid applying optical flow until finalizing your edits. Alternatively, place the converted clip in a separate timeline, export it as a standalone clip, and then import it back into your project. This allows you to delete the analysis files from the library.

Does PostLab support remote collaborating through a cloud storage provider client on a NAS?

No. PostLab needs a single source of truth in order to sync correctly. In other words, all team members need to access the exact same Team Bundle. Team Bundles that are synced through a cloud storage provider with a NAS will cause conflicts, because each Team Member works from their own version of the Team Bundle.

Can I switch between working locally from a NAS and remotely from my laptop?

As a single user without a team, yes. Use a cloud service like Dropbox and let your NAS connect to it so that there's a single source of truth (the cloud) while having a local copy on the NAS too.

If cloud syncing is not an option for you, simply transfer the Team Bundle between the NAS and your laptop before heading out. You can do this manually if the Team Bundle isn't too large. However, the best approach is to sync a Team Bundle through an app like Chronosync. Ensure that you do not start working on either the NAS or laptop until the Team Bundle is fully synced.

This workflow does not support team collaboration because a Team Bundle exists in two locations.

How do backups work?

PostLab inherently creates backups as each version is created, but the bundles themselves you need to back up yourself.

If something happens to a PostLab Team Bundle, is the data recoverable?

Yes. The contents of a Team Bundle are encrypted. In a worst case scenario, you can send us a Team Bundle and we'll be able to extract all stored data, but that has never been needed; so far, corrupted Team Bundles (100% caused by failing cloud syncs) were easily restored with a bit of help from us.

Is macOS 13 really the minimum PostLab can run on?

Yes. PostLab is built completely in Swift and SwiftUI, which requires macOS 13 or newer. There's is no older or even legacy version available for older macOS releases.