Questions

I'm seeing an error saying "Something went wrong loading version bundle ....turf. Please reach out to support...". What should I do?

This message means that there has been a syncing hiccup, resulting in some files not being fully synced. This is often caused by a brief network dropout, a computer crash, or a premature computer shutdown while the syncing job hasn't finished yet.

Usually, this message clears itself when the person on the team who used the Team Bundle last resumes their syncing queue. Or have them open the latest project, make some changes, and save it again to force the syncing progress.

If you are absolutely sure that all syncing has been done, and no one is blocking the syncing progress, or when nobody on the team can access the Team Bundle anymore, then a Version Bundle has become corrupted by the syncing hiccup. This can be remedied by restoring it to a previous version.

You can do that by following these steps:

  1. Make sure to create a backup of the Team Bundle before you proceed.

  2. In Finder, right-click the Team Bundle and hit 'Show Package Contents.'

  3. In the folder 'versionbundles,' find the Version Bundle named in the alert.

  4. Go inside the Version Bundle: Right-click 'Show Package Contents.'

  5. Remove the 'Index' file (put it on your desktop).

  6. Next, go into the 'files' folder of the Version Bundle and sort this folder to ‘Last Date Modified’.

  7. In the newest folder, locate the 'index-backup' if there is one. If not, go to the second folder.

  8. Rename the 'index-backup' file to 'index.'

  9. Put this index file in the general folder of the Version Bundle.

  10. The Version Bundle is now put in it's previous state, before the syncing issue started.

Alternatively, if the procedure above does not help, you can remove the Version Bundle from the 'versionbundles' folder altogether:

  1. In Finder, right-click the Team Bundle and hit 'Show Package Contents.'

  2. In the folder 'versionbundles,' find the Version Bundle named in the alert.

  3. Move the Version Bundle from the Team Bundle to a local folder. Removing the Version Bundle entirely removes the corresponding files from PostLab. This means the work will be lost instead of returned to an earlier version.

Repeat the first or second procedure for every Version Bundle mentioned in an alert until the Team Bundle opens.

I can't upgrade my Team Bundle because PostLab is saying that there are team members working in it. How can I proceed?

This message shows when you start an upgrade of a Team Bundle, but team members are actively working on the Team Bundle or have unsaved work. Makes sure they save all their changes and they close PostLab. The list of team members should clear and you can start the upgrade. This will take a few seconds

If you are sure that no one's working on the Team Bundle, then it means there are some sync files not properly deleted when changes were made to the Team Bundle. This is usually caused by a network hiccup or a crash.

To continue the upgrade process, follow these steps:

  1. Make sure that no one is working in the Team Bundle.

  2. Quit PostLab.

  3. Download and open “Unlock PostLab Team”.

  4. Select your last opened Team Bundle and click Continue.

  5. Open PostLab.

You will now be able to upgrade the Team Bundle.

PostLab is showing an "Upgrade in progress" alert, saying that someone is upgrading the Team Bundle. How do I proceed?

This means that someone on the team is upgrading the Team Bundle. Pleas wait until you get notified by that user that the upgrade is finished, this usually takes seconds.

Sometimes this message shows when when the upgrade is already done. In this case there is an upgrade file stuck in the Team Bundle because of a syncing issue or a crash. To unlock the Team Bundle, do the following:

  1. Make sure nobody is actually upgrading the Team Bundle.

  2. Back up your Team Bundle.

  3. In Finder, right-click and hit 'Show Package Contents'.

  4. Go to the 'migrations' folder.

  5. Inside, you'll find a file called `migration.json`. Remove the file.

This will get you back into your Team Bundle again.

Why is PostLab asking me to "Close Final Cut Pro" when I'm saving my changes?

This message has to do with macOS permissions. These can be a bit of a pain and sometimes stubbornly ignored if already granted. Check the following:

  1. Make sure you’re running the latest version of PostLab (PostLab > Check for Updates)

  2. Go to macOS System Settings > Privacy & Security > Accessibility and ensure PostLab is present and turned on.

  3. Go to macOS System Settings > Privacy & Security > Automation and make sure Final Cut Pro is turned on in the PostLab dropdown line.

Everything already turned on? If so, turning these permissions off and on again while rebooting after each steps should force the permission settings. Sometimes it also helps to manually remove PostLab from the Accessibility settings, reboot, add it again, and reboot.

Why are there events missing in my imported Final Cut Pro Library?

In rare occasions, PostLab will skip some Events during imports from Final Cut Pro backups, or exported FCP libraries from PostLab Classic. We are uncertain why this happens and actively investigating. The following workarounds should get you on your way.

In case of a Final Cut Pro backup:

  1. Rename the FCP backup Library.

  2. Import this into PostLab.

  3. Continue working.

In case of an exported FCP Library from PostLab Classic, or when the renaming workaround didn't work:

  1. Create a new Library.

  2. Copy the events from the exported or backup Library into the new Library.

  3. Import the new Library into PostLab.

PostLab is telling me "You haven't made any changes to this document" after I worked in my Final Cut Pro Library and wanted to save my changes. What should I do?

Although rare, this can happen on imported Final Cut Pro backups or imported FCP Libraries from PostLab Classic exports. We aren't sure yet why this happens, and we're actively investigating. For now, this workaround will get you on your way:

  1. Create a new Library in PostLab.

  2. Open this new Library next to the original Library that’s already in PostLab.

  3. Copy the events from the original Library into the new Library.

  4. Save the changes to the new Library in PostLab.

  5. Open the new Library again to check if all changes have been saved.

  6. Discard the changes on the original Library which can then be safely trashed.

Last updated