Skip to main content
Participant
October 26, 2017
Répondu

Pluraleyes with Premiere 2018

I recently updated to the new Premiere 2018, and am having trouble with Pluraleyes. I installed the Pluraleyes update, but it still isn't working properly. When syncing media within Premiere with Pluraleyes it didn't work at all... so I synced media within Pluraleyes and exported into Premiere but that didn't work. I tried importing other XML files and the window pops up as though it is importing but nothing ever imports.... please help!

    Ce sujet a été fermé aux réponses.
    Meilleure réponse par excited_Genie16B8

    You're probably better off contacting Red Giant for this one.

    16 commentaires

    Participating Frequently
    August 7, 2018

    @Part7. So, I did some test and I had to downgrade to Version 12.0.0 for Red Giant to work. The 12.1.1 had some issues with the sync where it had "zebra lines" on the video and audio clip. When I went back to 12.0.0 it was working fine.

    Inspiring
    May 16, 2018

    Just had issues with Plural Eyes and came to this post hoping for answers. Didn't get the ones I was looking for as I already had the box unchecked in premiere preferences that says "allow duplicate media during project import" BUT I did get around it so I figured I'd share.

    Anyway, I felt like I should report that when I import the xml into premiere it hangs on that import progress box (not moving) for a few minutes actually, until it pops in and all is well. So, if others have this issue, perhaps just wait it out. It doesn't look like it's working, and you can even tap that progress box and it switches to that "not responding" look where it looks as if premiere is gonna crash, but sure enough within a couple minutes or so of waiting (at least on my PC which has top 2015/16 specs and over 100 video clips and 100 audio clips) the sequence(s) do import properly and all is well.

    However, this time the reason I came to this post is because after waiting a few minutes, that progress box disappeared and nothing imported. I closed premiere and Plural Eyes a few times and even restarted my computer with no luck. Finally, I deleted that sequence with all the clips, made a new sequence, dropped all those clips on there again and sent it to plural eyes and it worked. Still took the few minutes to import the XML but at least it came through this time.   This might not help anyone but figured just in case I'd share it in hopes that it helps someone one day. Cheers.

    Participant
    March 16, 2018

    I contacted Red Giant and they replied back. It is not the issue from their end. Premiere Pro is not allowing XML to be imported back in.

    Participant
    February 24, 2018

    Due to issues with PluralEyes and problems with importing projects Im rolling back to PPro CS6. Everything was stable back there. I'm paying for CC now and experiencing issues.

    Thanks for the suggested workarounds, youve made my day.

    juliap51060363
    Participant
    February 19, 2018

    Feb 19, 2018

    Just spent an hour on phone with Adobe. I contacted Red Giant (Pluraleyes) first with no luck. I was creating xml sequences both in and out of Premiere and trying to import them with no luck. Just wouldn't import. Not even an error code. 

    The problem is, go to setting in Premiere > Preferences > Uncheck "allow duplicate media during project import"

    This might create duplicate media in bin, but hey, there was no other way of fixing the problem. And I need to get to work.

    Hope this helps!

    Participant
    February 20, 2018

    I tried the uninstall and then reinstall.  That didn't work.  But unchecking "allow duplicate media during project import" worked like a charm. 

    phil_lid
    Participating Frequently
    February 15, 2018

    Carried out a full uninstall of PluralEye 4 and then re-installed.  This resolved my problem and all is good now.

    Participating Frequently
    February 10, 2018

    Yep having the same problem. I haven't found a fix yet but I will try a fresh reinstall of Plural Eyes. Red Giant blames Adobe and Adobe blames Red Giant. It's another case of software companies scapegoating each other. It's clearly and XML issue and this problem started when I upgraded to CC 2018. I'm not a software engineer but I think this is an Adobe problem. Infuriating.

    Update: Fresh install of everything didn't work. My workaround is that I downloaded CC2017 again. Plural Eyes and Premiere work together again. This is beyond frustrating and I hope it's fixed soon.

    Inspiring
    February 9, 2018

    This has been a huge issue for us for many months. Sometimes it brings the synced timeline back into premiere but most of the time it doesn't. Red Giant blames Adobe in their support emails. Who knows. I wish they would get this figured out.

    Participant
    January 29, 2018

    1.Delete C:\Users\User\Documents\Adobe\Premiere Pro\12.0

    2.Start C:\Program Files\Adobe\Adobe Premiere Pro CC 2018

    Ok!

    Participating Frequently
    November 21, 2017

    I don't know how it worked at the end of many technical upgrades and troubles. It did. But only for about a week. Then my computer started to restart in loop after a screen flickering and freezing moment.

    I finally decided to make time machine backup taking the oportunity to do it on a kind of recovery mode.

    I totally format the hard disk to make a clean Mac Os X El Capitan installation.

    I am not sure if this will be ok now, and if it will be better for Adobe Premiere, Photoshop, AfterEffects, inDesign and Plural Eyes than MacOS Sierra High.

    Mac OS X El Capitan (10.11) compatibility FAQs | CC

    macOS High Sierra (10.13) compatibility FAQ | Creative Cloud

    The problem now is how to open projects under MacOs Capitain that I've created on Adobe Premiere 2018 (using Plural Eyes the lastest upgrade) under MacOS Sierra High.

    The following lastest Plural Eyes version worked well when I managed to use Adobe Premiere under MacOs Sierra. Red Giant | We are Ready for MacOS High Sierra

    I think what was crashing my computer was inDesign.