Hi, the topic explains it. The export button is greyed out with a message I cannot figure out, see the screenshot here.
I copied the files to the usual location as per below ...
Pluraleyes ...
Copy the file "PE4Vegas14.dll" which is in the folder .. C:\Program files\Red Giant\Pluraleyes 4\
then paste it to ... C:\ProgramData\Vegas Pro\Application Extensions\
or ... "PE4VegasLoader14.dll" rather than "PE4Vegas14.dll"
I don't think this is a dll issue it's a workflow issue.
The best way to use it these days is to start in Vegas, arrange video and audio with a unique track per device and then send to PluralEyes. PE will then sync and overwrite the Vegas project. Unsynced clips will go to the end.
I just used PE 4 last week for an interview with VP 18 and it worked well.
It's working now. Looking at the file location in the screenshot, that's odd, OneDrive. It could explain it, I may have accidently saved to that location. I now made sure that I loaded and saved the project to a D; test file location and it works.
I just tested it and it doesn't work to go from PluralEyes to VP 18. It requires starting in Vegas, using the PluralEyes extension, and roundtripping to Vegas.
You can swap audio files though and replace camera audio if you choose to save new video files.
@RogerS Maybe I didn’t give a clear enough forum post. I wasn’t syncing completely outside of VP.
I loaded the test files into VP, saved the project, then selected Pluraleyes from within VP, and then the Pluraleyes module appears. After syncing, within the Pluraleyes module, I couldn’t select the export button in the Pluraleyes module (it was greyed out with a message explaining the issue, which I couldn’t figure out) to send the video, now synced, back into VP.
I later saw that the initial project .veg saved location was on Onedrive, which I don’t normally use. When I later avoided using Onedrive for the .veg, the problem went away.