Project folder and Sequence locations issue

It seems a lot of people liked the old / simple one.

I;ve been working IN premiere since Premiere 4.2. And this actually only started bugging me when the created that new project set up screen. I was like wow, finally. But it seems useless or only half finished.

I'm usually working on up 4 different projects.
It's not that I want all the files to be in my project folder, but when I set up a project directory, it would be nice in premiere actually used that directory instead of making you navigate all over you hard drive and network.

Project 1/Footage , Project 1/Export
Project 2/Footage, Project 2/ Export

Right now you set up a new project for Project 2, point it to the project 2 folder, your footage is a 'footage'subdirectoyr in the project 2 folder.  Then you click import and it goes looking in the last directory you imported from in last prject which could be Project 1/Footage or Project 8/Assets or wherever. Then you have to go searching for the project folder you just created to import footage from.

Or, you make a new sequence in your new project 2 and the default export path is the last project, like Project1/export, Desktop, wherever. if you have multiple clients, you need to be really careful where the default sequences are sending files. If you working late or tired it gets really frustrating when you go to the export folder and it's not there.

What is the use of the project set up screen at all?

I realize that different folks have different workflows but after 24 years in post production on both coasts and across a variety of clients from major ad agencies to boutique production companies to major editorial brands, I can tell you that .. there has almost never been a workflow in which I or any post supervisors would want my media in the same directory as my project file.  My project files live in project folders, my media in media folders.  So I would consider remembering the last location where I had media is, if not a feature, at least a reasonable default posture than changing the default to whatever the new project folder is.  That said... while your workflow is unique relative to my experiences, it is surely valid, and I would absolutely not mind having an option to set the default to wherever the user would like.

In fact, I would very much like to be able to set default folder(s) for scratch disks (ie: where preview files, auto saves, etc end up). As it stands, new projects always default to the project file folder or to user documents, but I virtually never want either of those locations used, and would love an option to set the default to a third location on my RAID.

So... whatever one's workflow, the ability to set these defaults (to one fixed location, to the project folder, or to the documents folder, would be make all of us happy.

I'm pretty sure it's not a 'bug' but it is a feature request. Before you opened the new project, IE: you were working on the last one - it seems to have been working just fine for you. Only when you finished and were starting to work on the new project was there a (temporary) issue.

and indeed it would be good if they fixed the folder opening locations.