Copy link to clipboard
Copied
Hello, here's my problem:
i need to work with my pc (premiere pro cc 2018 installed) on a sequence that i began in avid, using a macbook pro. initially i converted my avid sequence in a aaf file. I tried to import it in premiere: the program seems to start opening the file, the loading bar appears, but at the end of the process nothing happen.
Same with xml. It seems to work, but nothing happens.
Ok, so avid exports corrupted aaf and xml?
No, because i tried to open the same files with premiere pro cc 2018 and another macbook pro, and it worked fine.
To me the logic consequence is that there is an issue with aaf and xml files between pc and mac.
Or is my pc, that is also my main workstation, that's having issues with aaf and xml?
How can i fix this problem?
I thank you in advance for your answers,
and i apologize for my poor english.
Copy link to clipboard
Copied
I had the same problem with 2018, imported the AAF, the loader seems to be doing something, then nothing! I imported the same AAF with no issues in Premiere 2017! That worked...
Copy link to clipboard
Copied
After synchronization in pluraleyes. Premiere pro does not import XML. It also does not work to import one project into another. Nothing happens.
Copy link to clipboard
Copied
I have the same problem exactly! Opened the AAF in 2017 version fine, however I am unable to relink the audio files as the names dont match up in locate footage!
Copy link to clipboard
Copied
There is a bug in Premiere 12.0.1 with the "Allow Duplicate Media during project import" check box in Preferences>Media. If you have it checked it thinks that its duplicate media and will not import the media for both AAFs and XMLs. I've found that if you toggle it off, it will import your AAF.
I would be wary of using AAF import in CC 2017 if you have DF Timecode it sets it all to NDF Timecode. At least for my setup.
I have reported both bugs to Adobe.
Hope this helps.
Copy link to clipboard
Copied
Thank you so much. The same problem was solved with the import of projects.
Copy link to clipboard
Copied
Thank you!!!
Copy link to clipboard
Copied
Hi. I am having a similar problem with the migrating an XML sequence from FCP 7 to Premiere Pro.
I found the "Allow Duplicate Media during project import" button in the media preferences window.
I tried clicking to enable the function as well as disabling the function. Unfortunately neither worked. My results were nothing appeared in my project window.
Are there any other thoughts on a fix for this? Is project or sequence size the problem here. I am able to open up smaller sequences that have like 1 or two clips in an xml file but that is a horrible if there turns out to be a limit on the size of sequence you can import from XML.
Taking all suggestions and following all leads.
Copy link to clipboard
Copied
Hmmm, if you can open smaller projects with xml then it might be a different problem. I would roll back to Premiere 12.0.0 and try that, you won't lose much functionality from 12.0.1.
You could also try exporting sequence from FCP as xml instead of the whole project.
Copy link to clipboard
Copied
Hey thanks for the reply. So the whole time I've been exporting the sequence. Not the project. And the sequence is what is not opening up in Premiere.
Can you share the process for utilizing the earlier 12.0.0 version? I have a Creative Cloud subscription.
Copy link to clipboard
Copied
Are both PP and AE 2018 ?
Copy link to clipboard
Copied
yes.
Copy link to clipboard
Copied
Brand new install of CC 2018 and Avid and I have the same issue. Importer reports a generic error. Tried the duplicate media thing and it still doesn't work. 😕
Copy link to clipboard
Copied
The bug (Duplicate Media check box) I mentioned earlier in the post doesn't report a Importer Error. Your problem may have to do with the footage you're trying to import not the XML.
Copy link to clipboard
Copied
Are You using Apple 10.13.4 Sierra release?
Copy link to clipboard
Copied
Windows 10.
Copy link to clipboard
Copied
Think it's to do with diff video codes on same track... will have to break it out and see, but this maybe the prob.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now