Skip to main content
J
Jack5C65
Participant
January 8, 2021
Question

Large Team Project doesn't load/crashes

  • January 8, 2021
  • 2 replies
  • 322 views

Our Current Workflow:

I'm working on a very large Team Project with 5 other editors. We're working from afar, each with our own identical local drives running sync thing to sync to the server and using team project media management to connect to media. It was running smoothly when the project was smaller and there were fewer editors (not sure which of those is the factor, maybe both?). Now it takes about 46GB of RAM to load the project, 42.5GB from Premiere and 3.5GB from "Team Projects Local Hub". The project gets hung up loading, or loads and soon crashes, or crashes when I try to share or take changes. Other users with slower internet and less spec'ed out stations aren't having problems...yet. I've tried multiple Adobe IDs and multiple work stations. 

 

Potential Solutions we've thought of:

1. Switch to Productions and Parsec/Teradici in to on-site stations accessing the same server, bypassing Team Projects altogether.

2. Break the Team Project into smaller ones (with fewer people in them).

3. Adobe implements Media Management in Productions so that we can keep using our local hard drives (please).

This topic has been closed for replies.

2 replies

R Neil Haugen
R Neil Haugen
Legend
January 15, 2021

The entire Team Projects process must run with only the owner of the project using the 'traditional' media mangement via the MediaBrowser and Project panel. Any Team projects collaborators must use the Edit/Team Projects/Media Management process.

 

And my understanding for Productions is that all users need to either be on the same server, or have an identical folder-tree setup within their own system. I'm working with Mo Moolla of SA to test out the LucidLink service for completely online storing of both Team Projects and Productions processes. But we've just started.

 

Neil

Everyone's mileage always varies ...
R Neil Haugen
R Neil Haugen
Legend
January 9, 2021

Where that sort of issue comes in is when the project files have so many assets to them. Premiere has to load all internal meta about every asset in the project file into RAM/cache, and that is the reason Productions was created.

 

The way to "fix" this in a Team projects workflow is to break the project into separate sub-projects within the total project. They call these "Linked Team Projects".

 

You can create LTPs from either the file menu or right-clicking in the Project panel, New Item, Linked Team Project.

 

Do that with parts of your project, and move the assets from the main project file to the linked ones. And see if by simply loading one of those you can get work going better.

 

Neil

Everyone's mileage always varies ...
    J
    Jack5C65Author
    Participant
    January 12, 2021
    We ended up going with a different approach from the one you recommended:
    we migrated the Team Project into a Production. But now playback is
    unbearably stuttery--less than 1fps. Any ideas? If it means anything, this
    is for a major studio film, so any advanced help would be most welcome.

    Best,
    Jack
    R Neil Haugen
    R Neil Haugen
    Legend
    January 12, 2021

    In a Production, what was one project or maybe a major project with a couple linked projects should probably have maybe 20 different project files or more inside the Production. For a large major film with thousands of assets, you may have many, many different project files. You might have 50-100 just for storing media!

     

    The entire point of the Production model is to break the total project up by the subfolders within the Production, and then within subfolders using project files as you would previously have used bins within a project file.

     

    So rather than even having all your media in one project file, using multiple project files within a Media subfolder for different parts or types of the media.

     

    You have a different folder setup for say sequences, with project files that may only have one or two sequences in them.

     

    This way, Premiere doesn't have a bazillion Master Clip references to load into cache/RAM, as each say sequence project with a single sequence has very little to load. It can reference the media from their project files without needing to load that project into cache/RAM either. And editing should be able to proceed smoothly without the stuttering you're having.

     

    It sounds like you are still using LARGE "centralized" project files.

     

    Neil

    Everyone's mileage always varies ...
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices