Pluraleyes 2 is giving me an error "XML file does not contain a project" when I try to open XML exported out of Pr CC 7.1. Has anyone else encountered this and can anyone suggest a workaround?
[Thread title changed for clarity.]
Message edited by Jim Simon
I'm using Pluraleyes 3, but I had the same error, so this might work for you. If not, I apologize. I was running Pluraleyes externally from premiere, so I would export the .xml and import it and receive that error message. What I did to work around that was to install PluralEyes through the Adobe Extension Manager CC and integrate the program with Premier. It totally works now and is even a little better I believe. Here is a link to install Pluraleyes as a plug-in: http://www.redgiant.com/support/faq/product-specific/pluraleyes/277/
Hope that helps
I'm having the same problem, but have not found a workaround. PluralEyes 3 has never worked well for me, so I'm not interested in that. PluralEyes 2 has always been golden, but it seems Adobe has made some sort of change to the XML process. (And I thought 7.1 was supposed to have its own built-in sync, but it seems that feature didn't make it through.)
(And I thought 7.1 was supposed to have its own built-in sync, but it seems that feature didn't make it through.)
Premiere Pro has had that feature since CC (7.0):
I have also experienced this error. Apparently Premiere Pro 7.1 doesn't save FCP 'project' attributes when selecting a sequence and exporting it. 7.0.x worked well and just creating enough XML project info around a single sequence if that was all that was selected when choosing export. My workaround was to deselect the sequence and then chose xml export in the menu. That will probably export all the sequences in the project, like pre PPro 7 used to do but at least Pluraleyes can open the file. Jeeze.
I'm with you. I have never been able to get 3 to work, but using 2 externally with an FCP XML has worked great. Now with 7.1, I'm getting the same error message. I put in a bug report, but in the meantime am going back to an old installation of CS6 and exporting from there and importing the xml into CC. Sucks, but that is plan until they fix it.
The problem with the new 'syncronize' feature is that it is really bad at syncronizing which defeats the point. Atleast Plural Eyes 3 tells you when it can't find a match and doesn't just muddle up your footage. 'Syncronize' also messes around with the audio tracks and just seems overall really limited and buggy.
Plural Eyes can also do more than two clips at once.
Has 'Syncronize' been road tested with more than prestine video and audio recordings?