Known Participant

Question

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

Forum|Forum|8 years ago
January 30, 2018
15 replies
10332 views

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!

This topic has been closed for replies.

farshidk32183183

Participant

I have the same issue

gupta shivangi

Legend

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

PeterThomasonAuthor

Known Participant

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

Community Expert

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.

PeterThomasonAuthor

Known Participant

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.

Jonathan Lutjens

Known Participant

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

PeterThomasonAuthor

Known Participant

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

Jonathan Lutjens

Known Participant

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.

PeterThomasonAuthor

Known Participant

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 J. Monahan Jr.

Community Manager

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

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio

Stan Jones

Community Expert

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.

PeterThomasonAuthor

Known Participant

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".

PeterThomasonAuthor

Known Participant

Hi Kevin I have just finished filing the bug report. The core of the problem is that duplicating a timeline will never duplicate the associated timelines. Which is why must editors (not just me) are pretty used to importing a project multiple times so that the correct hierarchy is respected. Now Adobe broke this. Projects with multiple nested timelines such as Title cards, Billboards, Lower-thirds, etc. Nothing will work anymore unless I go through the painful process of duplicating all associated Nests.

Once again Adobe creates a new "Feature" that breaks entire workflows apart. It's almost like they talk to the wrong people when deciding these things.

This sucks.

Kevin J. Monahan Jr.

Community Manager

Automono,

Hi Kevin I have just finished filing the bug report.

Cheers, thank you!

Nothing will work anymore unless I go through the painful process of duplicating all associated Nests.

Engineering asks, "I wonder whether the Media Browser's "Allow Duplicate Media During Project Import" pref, influences/impacts the behavior...?"

Can you try it? Let us know the results. I will try it as well when I get a moment, however, I wanted to get that question to you and others on this thread quickly.

Regards,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio

Stan Jones

Community Expert

The duplicate media did not influence whether or not it could be imported. I'm still testing whether any option produces assets that can be independently edited. Originally it appeared that they could not.

An option that may have worked is to create a folder and move import one into it, then import the project again. I am still testing, but a title from import 2, that is not in a folder could be edited without changing the same title from import one.

Kevin J. Monahan Jr.

Community Manager

Hi Automono (and others),

Please file bugs on this issue here.

Thank You,

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio

PeterThomasonAuthor

Known Participant

Say I create a lower third with some animated mattes on a nested timeline. Surely importing this same lower third project into an existing project is a normal situation since you want to reuse this lower third for several talking heads. This normal workflow for a lot of people. Simply saying that we are not suppose to import a project twice sounds kinda crazy to me. Kevin-Monahan What do you think? Can you talk to some powerful Adobe people for us? Maybe this is a mac issue, since Neil reported it is working fine for him. How can we roll back on this update?

Stan Jones

Community Expert

I can reproduce Automono's issue. EDIT: Windows 10.

Two issues here: 1) cannot import even the first project and 2) cannot import same project multiple times and maintain independence (of, for example, titles).

Due to troubleshooting unrelated to Adobe, I had to restore my system to just before updating to 12.0.1. Tests with 12.0.0 behave as expected. (I can import the same project into a new project multiple times and the elements appear independent, whether with the same or different names.)

In 12.0.1, I cannot import a project IF I set the option for "Create folder for imported items." If I do not select this, the items come into the same directory. Whether I move them into their own directories or not, changing one item results in the same change to other items with that name. And changing the name does not change this: changing one item results in a change to any item that originally shared the name.

No telling what subtleties may affect this. I made a very simple project with one title, placed the title into a sequence and modified the opacity. So the imported project has a sequence and a title.

T

T_Williams

Inspiring

How'd you restore your Premiere to 12.0.0?

Thanks for your help!

PeterThomasonAuthor

Known Participant

Yes, T.Williams is right. I have a project that I use frequently. If I import the project twice to have two working versions of it, the second imported project reads from the first imported nested sequences. Completely ruining my second import. What is worst is that if I choose not to duplicate it will not import (which I am guessing it is ok since it has the same project name).

Checking the allow duplicate the check box, will import my second copy of the project but as I said before it will read from the first import nested sequences.

Needless to say. This sucks.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded