An almost daily task for me is syncing footage and audio up in Plural Eyes.
Workflow is like - Added footage to timeline, export timeline XML, open in PE, Sync, export from PE, Open new XML in Premiere. No problem.
But so far in 2018 unless I make sure "allow importing duplicate media" is checked in the import project dialogue box the XML won't import. It just bring in empty folders. It used to work just fine, it would bring in the synced up sequence and just rely on the media already in the project.
Now though it re-imports the media that was in that sequence. It's a total pain. Add that to the other dumb things Adobe broke with this update and I'm pulling my hair out.
I have the same issue.. Please, let me now, if you found some fix for it.
Use the Premiere Pro plug-in for PluralEyes, rather than the stand alone app.
This issue still occurs for me when whether I'm using the Premiere Pro plug-in for PluralEyes or the standalone app.
Went back to CC 2017, no issue. Seems like a CC 2018 problem.
This is a real pain...
yep, still haven't found a solution. The only work around I have right now, which isn't really a work around at all is to import the XML and then replace the footage in the now synced sequence clip by clip with the footage already imported into the project and then delete the duplicate media. It's a total pain. The best answer I got from Adobe was to "file a bug report"
I've always had this issue where it would occasionally duplicate some audio files after syncing and used your solution. But it has never duplicated video files. And replacing 50+ video files at a time is something I don't have time for. I've reverted to CC 2017 until this gets resolved. Sounds like it is an issue related to all XML round tripping, not just PluralEyes.
Hopefully they will resolve this issue soon.
yeah, I filed a bug report so we will see what happens.
It's not just plural eyes, correct. Even when I export an XML and then re-import that same XML file it duplicates all the media.
Does the Extension work for you in the 2018 build of Premiere?
I have re-installed the latest version of Plural Eyes and the extension still does not show up in my Premiere Pro Extensions.
Also, I cannot get Plural Eyes to Import XML from Premiere Pro.
Hope Adobe resolves or someone figures out a solution here...
wonderful. I've filed a bug report and look forward to the issue getting fixed.
Looks like the issue has been addressed in version 12.0.1
Can anyone confirm this also resolved the issue while using PluralEyes?
three years later and this is still happening!
XML round trip AND premiere plug in, Plural Eyes duplicates at least some of the media. Today it was all of my audio files. Last week it was everything. Very frustrating.
Just flagging this as still an issue in Premiere 14.4.0 (build 38). Duplicates media when importing an XML (from Pluraleyes for me) even if the checkbox for "allowing duoplicate media" is unticked. I was having this issue using the Pluraleyes extension, so tried the standalone application and it's the same.
PS bug report also filed
This bug persists. I experienced the issue recently while working on a feature documentary. After migrating all 125 days of footage into a single RAID, I created a new project and, in the process of bringing old sequences into the new project, encountered the duplication bug. Importing XMLs created duplicate footage and importing via the Media Browser created duplicates. Deleting those duplicates results in the same clips in the associated timelines being deleted. The "Consolidate Duplicates" function doesn't seem to resolve it either. The only workaround I have found is to open both projects—the old and new—relink all footage to ensure that both are pointing to the exact same directory, and then copy the contents of the old sequences into new, empty sequences one by one. Would love any updates on this issue. Thanks!
Hi, one workaround I have found useful is to open both projects like you say, and then just copy the required sequences from one to the other project. This seems to avoid the media duplication, but agreed it is a pain that the system still has this bug