![pluraleyes 4 premiere slow pluraleyes 4 premiere slow](https://www.soundsnap.com/blog/wp-content/uploads/2019/05/Group-4.png)
#Pluraleyes 4 premiere slow pro#
Final Cut Pro has tried to make an interchangeable format see here XML files are human-readable but unfortunately, it’s markup tags doesn’t always follow an interchangeable format, making the file incompatible with other programs. XML files are normally associated with a program or website settings/data. At present, it’s still the most reliable way of reading and writing the editing program’s timeline rather than importing and exporting an XML file into the standalone program. The extension creates a temporary type of XML file only Pluraleyes understands and when Pluraleyes is finished processing another temporary XML file is created for the extension to make a new sync EDIUS timeline. Version 2 had an extension plug-in that communicated between EDIUS timeline and Pluraleyes. The core of Pluraleyes program seems to only read and write XML files.
![pluraleyes 4 premiere slow pluraleyes 4 premiere slow](https://i.ytimg.com/vi/d2N3IG-hmTM/maxresdefault.jpg)
But at present (July 2016) they have not reintroduced a Pluraleyes extension plug-in for EDIUS 8 similar to the old version 2 that worked with EDIUS 6.5 (back then Pluraleyes was owned by Singular). Red Giant have a Pluraleyes extension for Sony Vegas and Adobe Premiere which works better than using the standalone program (explain later). It was always a hit and miss importing a Premiere’s XML project file into EDIUS, especially when the video clips are spread over spanned files (found on memory cards). On July 2016 Red Giant release Pluraleyes 4.1 which supposedly now supports EDIUS but no longer supports Avid’s AAF project files.