The following symptoms indicate that there is a communication problem between PluralEyes and Final Cut Pro:
- FCP crashes after a sync
- There is an error message from PluralEyes that says it is having trouble communicating
- Error messages like "Got NULL for XML document root" or "Is Final Cut Pro running?" are seen
- The project and sequence lists in PluralEyes are blank
PluralEyes communicates to Final Cut Pro using operation system services (Apple Events). It does this at startup to get the project and sequence information, and after processing is complete to send the sync results back to FCP. This normally works well but can fail if
- The project has a large number of clips and sequences in it
- FCP is busy and can't accept a communication
- Apple Events aren't working
Some solutions are
- Remove unneeded items from the project (be sure to back up the original project)
- Wait till FCP isn't busy doing other things (like rendering)
Workaround Starting with PluralEyes v2.1 there is another workaround for problems like this. You can do the communication manually by exporting and importing XML files. Here's how:
- Export your FCP sequence to XML. To do this, go to FCP and select the desired sequence in the Browser. Choose File > Export XML....
- In PluralEyes, click the File button and choose the exported XML file.
- Sync with PluralEyes and import the resulting synced XML file into FCP using the menu item Import > XML....