HELP!!! I can't import a project into Premiere Pro anymore.

[PeterThomason]

Hello I updated Premiere Pro. I can open a project, but I can no longer import the entire project. It allows me to select how I want to import (sequences, entire project etc) and it does not do anything. Help! Help!

[Stan Jones]

It may influence it, but does not provide a workaround.

WIn 10; PR 12.0.1 Since I've now updated to 12.0.1 on my restored PC, I can't go back to confirm the desired operation on 12.0.0.

As described in earlier post, and to emulate the other poster's issues, the project to be imported ("Original") has one title in a sequence. So when it imports, it imports "Title 01" and Sequence "01."

Create a new project ("Second"), import a video, create a sequence with it.

From previous tests, trying to import Original into Second using "Create folder" results in no import (with or without Allow Duplicate).

Importing via media browser as "Import Entire Project" and none of the 3 options at the bottom (Create folder, Allow duplicate, and Do the same) results in import to root bin. Importing a second or third time adds nothing.

Starting with just the Second project video and sequence, using Allow Duplicate (without Create Folder) now results in No Import! I could swear it allowed it before.(Same if importing from project panel.)

Back to the first test above (without allow duplicate). After import one, create bin and add the import to it. Try import with "duplicate not selected." Did not import anything.

Try import with duplicate selected. Imports to root bin. Create bin "Import 2" and move import 2 into it.

Add title sequence from Import 1 to the sequence with the video. Add the other title sequence from Import 2. In timeline, double click title sequence from import 1 and then select the title. Modify text. Modified text shows in title/title sequence from Import 2.

Undo.

Open title from Import 2 from project panel, and modify. Both titles show the change.

Undo back to point where bin for Import 2 was created. (So Import 1 is in a bin and Import 2 is in the root.) Add title sequence from Import 1 to the sequence with the video. Add the other title sequence from Import 2. In project panel, open title itself from Import 2. Edit text. Change does not show in either title on the timeline.

Edit text from Import 1: change shows in both title in timeline.

[Stan Jones]

First import works only if no create folder and no duplicate. Subsequent imports work when selecting "create folder" and "allow duplicates."

Because the issue was posed regarding titles, I was using legacy titles as a quick option. I added a video asset to the sequence to be imported.

My tests indicate that the title reference is to each previous import. So the title in imported project/sequence 3 is to the title in imported project/sequence 2.

Video assets, however, behave differently. Open clip from nest sequence in source monitor. Add a marker. The marker appears in all sequences. (This is as expected if they are all the same original clip. I do have save xmp to clip.) Change in/out point; appears only in actual sequence being worked in. (Also as expected, since this is saved as part of sequence.) But they are not treated as independent clips.

These issues may not be issues when importing different projects.

[PeterThomason]

Hi Kevin-Monahan​

Please tell the engineering team that "Allow duplicate media" is exactly what is NOT working. While it does allow for a re-import of the project. The associated Nests of the re-imported project are disconnected. The newly imported project is simply using the associated Nested Timelines of the 1st project. As a result any updates to the newly imported Nested timelines does not affect the final timeline.

Nested timeline changes to titles or source media of the 1st imported project affect all subsequent imported projects. I really do appreciate the time and effort to fix this. I have been an Adobe Premiere user for over 20 years. Even when it was not "Pro".

[PeterThomason]

Wonder how long until there is a fix for this. It's mind boggling how a version of Premiere Pro can be released like this. Any work Kevin-Monahan​?

[Kevin-Monahan]

Hi Automono,

Any work Kevin-Monahan ?

My apologies, "any word," do you mean? If so, yes. I brought it up at our tech meeting this week. It appears to be a known issue. At this stage, filing a bug with precise repro steps, and then asking your peers do the same, is the best thing you can do.

One thing that was suggested by a QE as a possible workaround was to import items from other projects via Media Browser and not by dragging or using the new File > Import dialog box. Can you try that? See that the Media Browser's option for "Allow Duplicate Media for Project Import" is disabled, as well.

Please report back if this workaround is working for you.

Wonder how long until there is a fix for this. 

As far as development goes, I can not really ever give you a time estimate on issues engineers are working on, sorry. Keep in mind that I'm in support and am not a dev.

Thanks,
Kevin

[Stan Jones]

Ran more tests based on this:

One thing that was suggested by a QE as a possible workaround was to import items from other projects via Media Browser and not by dragging or using the new File > Import dialog box. Can you try that? See that the Media Browser's option for "Allow Duplicate Media for Project Import" is disabled, as well.

In my previous tests, I could not get a project to import (from media browser or project panel) if I had new folder selected. I thought I tried with allow duplicates checked and unchecked. Now, I can import the first time if I have duplicates UNCHECKED. But it works in either import I used (media browser or from project panel - right click, import).

Subsequent imports of the same project (with create folder selected - not helpful if not) work only if allow duplicates is checked. But again, works whether with media browser or project panel.

The first import bin is the name of the project. The second import bin is named with an "02" added - "[Project Name] 02".

Subsequent imports that fail "use" the next number, so, for example, if import 2 is successful (and is assigned "[Project Name] 02" and import 3 and 4 are unsuccessful, a successful import 5 is named "[Project Name] 05."

Regarding one user's thoughts, as I found previously the unsuccessful imports are not in the project. Creating new bins or whatever does not make them appear. Looking at the unzipped project file does not reveal the assigned name.

The deal breaker is that any method still results in an asset in import 2 being dependent on the asset from the first import. Import 5 (with 3 and 4 being unsuccessful) is dependent on import 2.

Getting one project in is no problem. I have no found a workaround for users who are trying to bring in multiple versions of the same project.

[Jonathan Lutjens]

I'm having the same issue. No matter what configuration I choose under import settings, I get nothing.

Can't even import an EDL of a sequence from another PP project.

This is pretty frustrating

[PeterThomason]

Yeah....no solution provided yet. Typical new "feature" that just breaks the way a lot of editors do things.

[Jonathan Lutjens]

I was able to troubleshoot by opening up on my macbook pro via external drive and doing my import project and save new project there.

Something simple like this gets broke and yet we still don't have a basic function like "consolidate footage" or "reduce project" ala AE.

I wonder how large the group of actual editors/motion folks who give input on features is.

[PeterThomason]

Hi Kevin-Monahan,

Thanks for bringing this up with the engineering team. However I am a little disappointed that QE suggested we try the media browser. This is the first thing I did at the very beginning of this problem. It does not work.

It makes no difference. At least on a Mac. Maybe other folks on this thread would like to give it a go on their PC. Again, it looks to me like this new "feature" has left a lot of folks scrambling.

Me and other fellow editors have filed a bug report a few days ago. I get that mistakes will be made, but not having a timeline for something that is pretty crucial for some of us kinda sucks. This is for sure a feature that was not tested correctly, it does not work right.

Thanks for the help.

[PeterThomason]

I've come to the conclusion that these forums are completely useless for the working professional. Adding "features" while breaking some things seems to be ok.

While I appreciate Kevin-Monahan​ for his efforts, it's evident that the engineering team is still patting themselves on the back for the new "feature" of opening multiple projects at ones and all those great "import options".

Love how they suggested some of the things to try, it's clear that they did not try them before suggesting because they would clearly see that none of those things work.

Thanks Adobe.

[Stan Jones]

Automono, I understand the frustration. I think part of the disconnect was produced by some helpers (and perhaps staff) not seeing the problem under the conditions they were using. (And, for me, the problem was not that a sequence/project won't import, it just won't import in the way it used to and with/without duplicates.) First round, I screwed up my tests, believing that something didn't work that did, and misunderstanding the actual problem that remained.

Anyway, I focus on the fact that "it" has been acknowledged as a known issue, which means that engineering has been able to reproduce. I'd love that process to be more transparent, but hasn't been for as long as I recall.

It's also part of why I recognize the value of Kevin, an experienced editor on multiple platforms, as an advocate.

[johnb64974657]

I agree 100%. I like to create my title/Text over video presets and save them as project files. It used to work perfectly to add the entire project allowing for duplication, now with this issue; it is a complete pain in the A** never copies to my new project. I was on with Adobe support sharing my screen, and the support guy was useless didn't seem to think that this is a problem and that I just didn't know the program SMH. His suggestion was just to copy the files within the project file, which really just causes a mess in the project.

FCP is looking inviting at this point.

[giralg30378478]

Hi there folks.

Have the exact same issue on mac.

But I've find one thing that can maybe get us closer to a workaround :

trying importing a project on a new clean/blank project WORKS.

Still can't import that new project on my "WIP project" but well... i was still able to import a project into another so I think there is somethings to do.

Another thing that could work (EDIT : works well for me / EDIT 2 : Import everythings in double) :

- Open the project you work on

- Open the project that you want to import in "WIP project"

- Create a new bin in your "WIP project"

- Copy the things you need from your project and paste it in the bin you've created in your "WIP project"

I'll try to keep you guys posted with my further tests.

[farshidk32183183]

I have the same issue

[Shivangi_Gupta]

Hi there,

We're sorry for the trouble. Which version of Premiere Pro are you using? Were the faulty projects created on the same version?

Let us know. We're here to help.

Regards,

Shivangi

[Au42zh]

It's 2024, and I am also having the same issue in a newly downloaded (i.e. TODAY) version of Premeire pro.

A Project I was working on had forzen on select frames of the project, and trying to import it onto different, saved , new and copied versions of the project had all fallen flat in rectifying my issue after trying every single forum (offical and unoffical) toubleshoot. A known Iissue since 2018, and AI was intigrated before it was solved?

[Au42zh]

Edit: Changing the label colors to classic has fixed my source monitor issues.