• FAQ

• Forum

• Troubleshooting

• Video Tutorials

• Request Help

"It didn't sync"

If you are sure it should have synced, then try the sync options as described in the how to pages for each product.

"Got NULL for XML document root"

1. Make sure you have the latest updates for the version of Final Cut Pro that you using (currently 5.1.4, 6.0.6, and 7.0.2).
2. If your are using FCP 7, please try the beta of v1.2.
3. This can also occur in situations where there is a large number of clips, sometimes over a thousand, in the project. Note: It is the number of clips in the whole project, not just the pluraleyes sequence, that matters. When PluralEyes requests the project information, Final Cut fails. We have not determined exactly how many clips is the maximum. A couple of hundred clips is OK; 1200 clips is not. The workaround is straightforward: it is unlikely that you are trying to sync a thousand clips, so create a copy of the project that has just the clips you want to sync.

"No media file found for"

This happens when there is an item in the pluraleyes sequence that has no associated media file. Examples are:

• slug
• text from a video generator
• nested sequence

Remove any such item from the pluraleyes sequence (it doesn't make sense to sync them anyway) and run PluralEyes again.

"Do you have write access to the folder with the media files?"

1. Note: This error was being reported in situations where write access was not the problem. This has been addressed in the beta of version 1.2.
2. PluralEyes needs to write some temporary files to the same location as the media files. If those media files are in a readonly location, this message will be displayed. Update for 1.2 beta: If write access is not available in that location, PluralEyes will ask for an alternative location where the temp files can be placed.

"No projects are open in Final Cut Pro"

We've had a couple of reports from people who get the error message "No projects are open in Final Cut Pro" even though there is a project open. In all cases, they were using Final Cut 6.0.x and the problem went away by updating to the latest version, which at the time of this writing is currently 6.0.6.

PluralEyes is in "Analyzing..." for a long time and then it crashes.

There is a problem in version 1.1.8 where there is a conflict with Final Cut if auto render is on and FCP is rendering when PluralEyes is trying to communicate with it. This is fixed in version 1.2 (beta is available here). Or you can just ensure that auto render is not turned on in FCP.

PluralEyes creates a multiclip, but there is a problem with it.

Please report the problem to us (). Multiclips are complicated for programs to create but we are determined to get it right, so every problem report helps us. In the meantime, here is a workaround. In the synced sequence that PluralEyes creates, trim the clips so they have a common in point (or out point). Drag them to a bin in the browser, right-click on that bin and choose Make Multiclip....

It can happen that there is no single point that can be used as a common in or out point. In that case, you can use the synced sequence information to add auxiliary time code to the clips and create a multiclip in Final Cut based on that. To add auxiliary timecode, use the Modify > Timecode... menu item and add timecode at the beginning of each clip based on their location in the synced sequence.

"There was an error getting the project information"

The error message in the subject line is pretty rare but it has shown up in situations where there is a large number of clips, sometimes over a thousand, in the project. When PluralEyes requests the project information, Final Cut fails. We have not determined exactly how many clips is the maximum. A couple of hundred clips is OK; 1200 clips is not. The workaround is straightforward: it is unlikely that you are trying to sync a thousand clips, so create a copy of the project that has just the clips you want to sync.

"The daemon is taking too long to respond"

Re-install the *full* version (not just an update) and reboot.

"The license manager is taking too long to respond", or you press the activate button and nothing happens

That error message indicates that a service that PluralEyes needs isn't running. A fresh install and reboot usually clears it up. (You can re-install using the trial version. The trial version and the purchased version are identical once the license key is entered.)

If that doesn't take care of it, follow these steps:

1. Repair disk permissions using the Disk Utility. This is a good thing to do once in a while anyway because disk permissions tend to get mangled over time and they can prevent applications from installing properly.
2. Re-install PluralEyes.
3. Reboot.
4. Try entering the license key again.

How do you uninstall PluralEyes?

To uninstall PluralEyes do the following:

1. Move the PluralEyes application (/Applications/PluralEyes) to the Trash
2. Move the PluralEyes License Manager (/Applications/PluralEyes License Manager) to the Trash
3. Move the PluralEyes startup item (/Library/StartupItems/ProTecVb) to the Trash
4. Reboot

I am doing dual-system audio with a Canon 5D Mark II and the clips drift out of sync.

See this blog post.