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!

[R Neil Haugen]

Ok ... so if you aren't, try this ... create a new project in the new version. Using the Media Browser in PrPro, navigate to the prproj file for that project, right-click, and "import" ...

Neil

[T_Williams]

This is still not working. Any other ideas? Have you tried it?

[R Neil Haugen]

I've not been able to replicate on my Winn10 PC. Importing part or all of projects of both current and previous versions works as expected.

So I'm as puzzled as you. Kevin-Monahan  ... Any ideas?

Neil

[Kevin-Monahan]

Hi Neil,

I've not been able to replicate on my Winn10 PC. Importing part or all of projects of both current and previous versions works as expected.

So I'm as puzzled as you. Kevin-Monahan   ... Any ideas?

I would not discount this report, we should file bugs on these types of things. I have seen plenty of weirdness with my personal updated projects, which should not be a problem for a point release.

Thanks,
Kevin

[T_Williams]

They import fine, but if they are the same project and have nested sequences, Premiere gets confused and can't distinguish which nested sequence belongs to which version of the project.

[Ann Bens]

I dont think you are suppose to import the same project twice.

[T_Williams]

Why? We've done this countless times in the past...

[Ann Bens]

Things might have changed under the hood due to be able to open multiple projects.

[T_Williams]

We can only hope this was an oversight and not intentional.

Fingers crossed.

[Ann Bens]

Double click in the Project window,

Select a xxx.prproj

and you should get this window:

[Prafful5C25]

i used to get this , but now i am getting file format not supported, anu sugesstions

[PeterThomason]

Not working on a Mac! Here is a better example. I made a cool title effect with several nested timelines that I now want to use several times. It simply does not work when I want to import it several times. It also does not allow me to open it again. 

[T_Williams]

Yes. This is totally screwed up in the latest release of Pr.

I import a project with multiple nested sequences, then I try and import the same project again to have a duplicate, and it doesn't work.

I even duplicated my project on my hard drive and renamed it. Yet, when I import the second (renamed version) if I update media in one nested clip it updates in the other original non-renamed version.

This is insane!

[T_Williams]

Anything on this guys!? This is a huge problem.

[PeterThomason]

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.

[PeterThomason]

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]

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_Williams]

How'd you restore your Premiere to 12.0.0?

Thanks for your help!

[Kevin-Monahan]

Sorry about this, T. Williams. Please download 12.0 from the Creative Cloud application. You may want to check Advanced Options to retain any previous versions of Premiere Pro, if you need them.

Thanks,
Kevin

[Stan Jones]

I make periodic system images (Win10), and one happened to be just before I did the 12.0.1 update. Time machine on Mac?

[Kevin-Monahan]

Hi Automono (and others),

Please file bugs on this issue here.

Thank You,

Kevin

[PeterThomason]

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-Monahan]

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

[Stan Jones]

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.