Steps to Reproduce Bug:
Open a Project
Open another project
Look at your screen
Multiple projects are open and it is very difficult to understand which project is which. It is much too easy to close the wrong project or affect an asset in the wrong project. Many users complain that the workspaces also change when if this is a workflow you want people to use then the workspace should stay the same throughout. A few suggestions:
Let the user disable this feature. It does not make sense for all of your users.
Make the highlighted/active project very obvious. Drop the other project into the background by maybe greying it out.
A more obvious workspace.
While we are not considering removing this long-requested feature, we hear you on the room for improvement.
Thank you for your feedback
Lara Pretorius commented
I like anf fully agree with Cameron:
"Personally my vote would be for an independent window to open with each new project, with the full Premiere UI. Yes, you would have to switch between windows to access each project, but it would be much more intuitive which project you were in at any time. And you could still have the option to float any panel out of that window if you want to drag and drop between projects, keep certain elements in view, etc. (perhaps combined with some of the visual clues others are suggesting, to make it obvious the panel is from a different project)"
It would be amazing to have the option to work with two completely different projects in completely separate windows. Most of my projects are not related, and so only having the option to open a 'project within a project' often feels like it's more confusing.
Personally my vote would be for an independent window to open with each new project, with the full Premiere UI. Yes, you would have to switch between windows to access each project, but it would be much more intuitive which project you were in at any time. And you could still have the option to float any panel out of that window if you want to drag and drop between projects, keep certain elements in view, etc. (perhaps combined with some of the visual clues others are suggesting, to make it obvious the panel is from a different project)
James Kolb commented
Lol how good is your hearing? No one said remove, we’re all just sick of lazy implementation on features we have no control over.
Michael Gyori commented
Agree. No one is asking for it to me removed. It certainly comes in handy, even in it's confusing implementation.
I'd just like to disable it until some thought and alteration has been made to the interface. It's frustrating that this feature was added with no interface changes. When two large projects are loaded, it's a spaghetti mish-mash.
Darren Manden commented
@Josh - I was thinking the same thing. I couldn't remember anyone saying that it should be removed either. Just the ability to disable it for those who don't use it.
Reg Santo Tomas:
What??? No one is asking for the feature to be removed. Just an option to toggle it off.
Trevor Gauthier commented
I lke #2. Its really tough figuring out when you are trying to pull something from an older version of a project.
Michael Gyori commented
Yes. I always lose a couple of seconds figuring out which project is which. Which panel is for what.
"2. Make the highlighted/active project very obvious. " This sounds like an easy applicable solution to this problem. Maybe by color coding the active project or something like that.
david bliley commented
I wouldn't mind being able to turn on an option to color code each project that is open. But you can keep it subtle if you wish... or outright garish if that's your thing. Again, keep it an option.
I'm just glad that we CAN open multiple projects now. That's a HUGE upgrade over the previous way we had to move things around.
"20/80" solution (not ideal but helpful and very easy to implement): When multiple projects are open, have bins and timelines tabs' include the project's name. So "Bin: Card001" becomes "Game of Thrones s9e3: Card001".
If it reverts to the typical tab title, it can be a subtle UI cue whether there's one or multiple projects open.
Other windows are either slaved to bins & timelines or deal with clips, so there's a smaller chance of confusion with those.
I also like the idea to group tabs by project, with a small divider between the groups. (In timeline window and in windows containing multiple bin tabs).
Color-coding will turn the UI into a mess rather quickly.
It's a good idea with terrible implementation. Shocker. How to fix:
- make it optional
- make it off by default
- match sequences by color (could be just the tabs or the whole window, make it subtle)
- group sequences by project, not order of opening (perhaps a user setting)
- allow 'solo project' -- hides or fades all projects not solo'd (perhaps like AE's shy layers?)
- allow 'close all projects except this one' (or something like that)
- clicking on a sequence tab switches project window to matching color
I would definitely use multiple projects if it were like this. As is, it creates confusion. It disrupts -- rather than enhances -- workflow.
Come on, Adobe. You're so close with this one. Get back out there and step on the plate.
Jim Simon, Sometime i need to compare projects side by so it is very useful to have multiple projects open. Also good for copying and pasting elements from one to another without having to import the whole project into another one like the old days.
please link the project in the project panel with the correct timeline sequence so selecting one selects the other (you can have an unlink/link button if you like)
Steven THOMAS commented
I can't remember why, but having multiple projects open in FCP7 didn't cause the confusion that Premiere does.
Darren Manden commented
I would love the ability to disable this feature. I've since created a close all projects shortcut which I use before opening a new project.
In saying that, I would love to be able to just hit a checkbox which simply disables the open multiple projects at once functionality.
From time-to-time it might be useful, but certainly not as standard operating procedure.
@Jim Simon: That's actually the workflow I use, however Premiere eventually freezes after I close all projects and then try and open an existing project. IMO, the problem isn't solved.
The bad thing about this application is that having multiple open projects mix the sequences in the timeline. If they managed to make the sequences independent of the corresponding project, it would be very useful.
A good solution for this is that when clicking the window of a project only the sequences corresponding to it remain active.
Maybe highlighting the sequences that are in the same project when you select different sequences would work? Or at least when multiple projects are open there's a way to look at the sequences and know which project they belong to such as color coding or text. Maybe even dividers so at least when there are 12 sequences open from 3 different projects they are separated.