Can no longer import Folder with Project as a Bin

[MaFt]

Apologies if I'm not using the correct terminology.

Up until I updated to PremPro 2018 this was my work flow:

Create new project

Drag all video files from Windows Explorer to Library - files appear in Project Library

Drag my 'Standard Stuff' folder  from Windows Explorer to Library

Select Sequence from the options for each project in the Standard Stuff folder

New folder / Bin created in Project Library containing contents of Standard Stuff folder

NOW since updating to 2018 version I can't bring in the Standard Stuff folder - it asks me to select the project sequence etc, the blue line goes to the end then nothing happens. I can drag in other folders to create Bins in the project but any that have PremPro projects in it do not work. It doesn't even create teh Bin with everything else, it just does nothing.

I've tried using import from the Media Browser but that does exactly the same.

Is this a bug or can you no longer import projects into other projects?

[excited_Genie16B8]

The best method for importing other projects is to navigate to the project file on the hard drive using Media Browser.  From there, you can import any part or even all of that project.

[MaFt]

As per my initial post, already tried this and does the same.

Also, please explain why this is "the best"? It's fiddly and awkward. For me, it's much easier to drag the files/folders from Windows Explorer.

[Stan Jones · Accepted solution]

There does appear to be a problem. See thread below. Try importing without selecting the "create folder" and "allow duplicates" options. After one import, it may work for others.

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

[MaFt]

Yes, this seems to work. Having the "create folder" ticked or unticked made no difference. The "allow duplicates" was the issue. It only works if that option of off (regardless of if there are any duplicates)

I did a support chat and screen share with Adobe and they helped get to this resolution. Hopefully they've now got a good visual example of the issue too.

Cheers!

I'm back up and running!