Re: Team Project Running Slow

PeterELee · ‎Mar 18, 2019

Linking Team Projects lets you break a large project into smaller pieces, while still having a master project that links to all of the pieces. The links act like aliases/shortcuts. Double-clicking on a link will open that Team Project alongside the Team Project that contains it. The main reason to use linking is that opening and auto-saving are faster in smaller Team Projects, even if you have a few of them open at once. Linking (and having multiple Team Projects open at once) currently works only in Premiere Pro. Links appear as offline placeholder items in After Effects. Here's an article that describes how to create and use linked Team Projects: Create a Team Project

PeterELee · ‎Mar 14, 2019

I would certainly suggest splitting things up into separate, smaller Team Projects. You can use linking to create a master Team Project that lets you quickly navigate to each sub-project. I don't know how your media is organized, but you might also see performance benefits from splitting your bins into a few separate Team Projects as well, then importing the footage needed for each episode into the Team Project for that episode. After three months of intense editing, the auto-save history for the Team Project may also be getting quite large. I would consider doing a "Save As" of the main Team Project so you can start with a fresh auto-save history. You can always access the shared versions and auto-saves from the original Team Project as needed via the Media Browser, or by opening it directly. I know you say you're skeptical to update, but the versions of Premiere and After Effects that will be released shortly contain a number of bug fixes and performance improvements specific to Team Projects. I would strongly consider looking at them when they become available.

PeterELee · ‎Mar 07, 2019

It's hard to say precisely what's causing the system to stall like this. My best guess would be that there's something in your unshared changes that has caused things to become stuck. If you go back to an earlier auto-save, or create a copy of the Team Project from the last-shared version, are you able to open those? You can try either option by opening a different Team Project, or even a standalone Premiere project, then opening the Media Browser panel. In the Media Browser, look under "Creative Cloud/Team Projects Versions" for your Team Project and click on the name. In the right-hand window, you will see tabs labeled "Versions" and "Auto-Saves." A slider on the far right of the window lets you scroll back to previous versions (the ones that were shared) and auto-saves (incremental changes saved to your machine). If you scroll to a version you want to open, you can right-click the name of the Team Project on the left and choose either "New Team Project From Version..." (if the Versions tab is open) or "New Team Project from Auto-Save..." or "Make Auto-Save (...) the Latest..." (if the Auto-Saves tab is open).

PeterELee · ‎Feb 25, 2019

Does this project contain a large number of media files? AE opens all of the media files in a Team Project when the Team Project is opened, instead of bringing them in as "pending" and relinking in the background once the Team Project is open, as Premiere does. This can cause AE to become unresponsive for a long time when opening a Team Project with hundreds or thousands of media files. We're working to improve this, but for now the best option is generally to create a simpler Team Project containing just the media that will actually be needed in AE. AE also makes DynamicLink connections to Premiere at that time for any Premiere Sequences in the Team Project, which can also be time consuming (this is also on our list to improve).

PeterELee · ‎Feb 25, 2019

Since it sounds like this behavior happens in a standalone project, the prproj would probably be the best file to send to Vinay. prmsdc2 is not a standard filename created by Premiere Pro, as far as I can tell. Is there a clip or media file in your project with a similar name? Perhaps there's something about that piece of media that is causing Premiere to update the cache so often. The best way to send him the prproj might be to upload it to Creative Cloud Files, Dropbox, or a similar service, then send him that link via DM.

PeterELee · ‎Feb 25, 2019

I don't honestly know, but it seems surprising. I will ask around on the Premiere Pro team to see if anyone knows more. Thanks for conducting all of these tests.

PeterELee · ‎Feb 15, 2019

Fixing these issues is one of our team's highest priorities. In every case we have seen so far with Premiere CC 2019, they have been triggered by copying assets from a Team Project to a standalone Premiere project, and only manifest in the Premiere project, usually after quitting and relaunching Premiere. The problem also occurred sometimes in Premiere CC 2018 when saving a Team Project as a standalone project. We believe the project conversion bug is fixed in the current Premiere CC 2019 build. We have identified the source of the copy/pasted/import problems in CC 2019 and earlier, and are working on a fix for the next version of Premiere, as well as code to let Premiere handle media from project files that already have damaged file paths. In the mean time, the best approach is generally to either work entirely in a Team Project or a standalone project file. If you need to move selected assets between a Team Project and a standalone project, first upgrade to the latest Premiere build, then use a two stage process of copying the selected assets into a new Team Project, then converting that Team Project to a standalone project file. That approach seems to be working reliably.

PeterELee · ‎Feb 07, 2019

I'm not sure if this is what you're describing, but if you import two files into Premiere with the same name, but from different locations, references to the old file will not automatically be replaced with references to the new one. That's true in either standalone projects or Team Projects. The best way to make a clip point to different footage is probably the "Replace Footage..." command, which works in either kind of project. To swap file locations without using Replace Footage, you would want to use the Media Management dialog to find the old directory, and create a new media mapping that specifies the new directory. In a standalone Premiere project, you would use the Link Media... dialog instead, but that is disabled in Team Projects since each collaborator may be have their media on different drives, and "Link Media..." doesn't allow that flexibility. If you click on that "Site Cutaways" directory in the Media Management, do you see a list of the files that are offline? If so, creating a new media mapping to the new footage directory should hopefully bring all of the new media online.

PeterELee · ‎Feb 06, 2019

I notice that your folder "Collab Test" is listed as online, but a subdirectory ("Collab Test/Beal Homes/Footage/Site Cutaways 050219") is listed as "Offline: Unusable Media Mapping." Can you verify that the second directory is present on your system? If so, does it contain the expected files? If that footage has moved, you can click on "Site Cutaways 050219" in that dialog and choose "New Media Mapping..." to specify the new location. Any media that was in that folder originally should come on-line from the new location.

PeterELee · ‎Feb 05, 2019

I'm not sure what would be causing this. If you close any Team Projects and import the same media into a standalone Premiere Project, do the drives still get scanned? This is only happening when Premiere is open, right? Does it happen if you create a new, empty Team Project with no media?

PeterELee · ‎Jan 31, 2019

If you go into the Team Projects Media Management dialog, is any media listed as being off-line? The Team Projects service does periodically scan all mounted drives for missing media. I wouldn't expect the scanning to be constant under normal circumstances, though. What OS are you running? Is there anything unusual about how your media drives are configured?

PeterELee · ‎Jan 16, 2019

The owner will need to share the media with you, or proxies. They can share the media in a variety of ways -- Creative Cloud Files, Dropbox or any similar file sync service, ftp, a cloned hard drive, etc. Once you have access to the media, Premiere will either find it automatically and bring it on-line, or you will need to locate it using the Team Projects Media Management dialog. With Team Projects, only the project data is stored in the cloud. In order to get access to the Team Project itself, the owner will need to invite you via the email address associated with your Creative Cloud login. Also, you must both have Creative Cloud Enterprise or Creative Cloud for Teams licenses. Team Projects are not currently available when using an Creative Cloud for Individuals license.

PeterELee · ‎Jan 11, 2019

I'm afraid I don't know the answer. You might have better luck in the "File Hosting, Sync, and Collaboration" forums, since this sounds like an issue related to file sync, rather than the Team Projects feature specifically. File Hosting, Syncing, and Collaboration.

PeterELee · ‎Jan 11, 2019

To be clear - the auto-save warning is just a warning. The auto-save operation will continue running in the background, even while the warning dialog is displayed, and the auto-save will normally complete eventually. The best thing to do when the warning dialog does appear, though, is to choose "File/Close Team Project..." and wait for the resulting progress dialog to go away. Auto-saves that runs when closing a Team Project are generally faster than the ones that run in the background while you edit, because the former are allowed to use more computer resources, and can't be interrupted by further edits. I'll PM you to see if we can narrow down what be causing auto-saves to be so slow in your Team Project, in case it's something other than importing or changing many media files at once.

PeterELee · ‎Jan 10, 2019

Did you relink using the Team Projects Media Management dialog, or by using the traditional Premiere Link/Locate feature? The Media Management dialog can be found under "Edit/Team Project/Media Management...", and any changes you make there should affect every clip that uses the underlying media. Traditional Premiere relinking is normally disabled in Team Projects, except for files that you've explicitly marked as offline. I'm not sure, but I suspect it could cause the sort of issue you're seeing, unless you selected all of the affected clips and relinked them all at once. If you did make the clips offline then use "Locate," you can go back to the previous state by browsing your auto-saves in the Media Browser, then choosing an auto-save from before you relinked the footage to make the latest (right-click on the Team Project name in the Media Browser and choose "Make auto-save (...) the latest"). That should restore the media associations to their original state. After that, the Media Management dialog should show you the files that are off-line, and let you add a mapping to the new folder location.

PeterELee · ‎Jan 07, 2019

Yes, I suspect you need to have had that option checked when you imported the media. I can't say for certain, though. If you don't have that option checked, I think its possible that some file formats will already have embedded XMP clip IDs, depending on how they were ingested. If the ClipID fix doesn't work for you, and you have standalone projects with this issue, PM me. I have a script that can correct the issue in many cases.

PeterELee · ‎Jan 03, 2019

Great find! We're still working on a fix for the underlying problem, but we've just tested your workaround in-house and confirmed that it works for most files that we tested. When only "Clip ID" is checked under "Matching Properties," the Locate code will search the XMP metadata of your media files, looking for one with the same Dublin Core "identifier" field as the clip had when the project file was last updated.

PeterELee · ‎Jan 03, 2019

That's very interesting. So far, I've only seen this issue when importing at least a few hundred pieces of media. It could also happen if were editing without taking a break for several minutes after doing a smaller import. In that case, closing the Team Project should allow the auto-save to complete, uninterrupted. Please PM me if you're willing to enable some additional logging in Premiere to see if we can figure out what might be happening on your system.

PeterELee · ‎Jan 03, 2019

Can you tell me more about your Team Project? Roughly how many media files are there? If you import or modify several thousand media files, the first auto-save after that can take a very long time to complete. This is especially true if you make any edits before the auto-save completes, or if any slow network drives are mounted, even if they don't contain media. We're working to improve performance in those situations, but for now we suggest using linked Team Projects to split up large productions into smaller chunks. Importing files in smaller batches (e.g. a few hundred at a time), then waiting for auto-save to complete before importing the next batch can also help. If you attempt to close the Team Project after a large import, that will also cause the auto-save to run faster in most cases, though it may still take several minutes if a large number of files were imported or modified.

PeterELee · ‎Dec 24, 2018

In theory, that dialog shouldn't prevent you from saving. It's just a warning that auto-save is taking much longer than usual. Auto-save will continue in the background while that warning is displayed. Of course, it's possible that there's something else going on, but most serious errors will result in an error dialog, and an error message in the event panel that includes an error code. Can you look on your system for the directory %APPDATA%\Adobe\Team Projects Local Hub\2.0\logs, zip up the contents and PM them to me? I'll see if there are any error messages being logged there. A dump file from the Task Manager might also provide some clues.

PeterELee · ‎Dec 21, 2018

In theory, at least, when you copy a sequence from one Team Project to another, the only items that should be duplicated are the ones that are different between the two Team Projects. That's what I see in my simple tests, too. For example: Team Project A contains a sequence and two clips, which are used in that sequence. Team Project B is initially empty When I paste or drag the sequence from A to B, the sequence and clips are duplicated in B. If I then edit the copy of the sequence in the Team Project B and paste that back into Team Project A, the sequence is duplicated in A, but the clips are not, since they were not edited. If I rename a clip or change other metadata in B, then a new copy of that clip will also be made when I paste the sequence, since the original copy of the sequence still refers to the old version of the clip, and we don't want pasting a new sequence to change the contents of an existing sequence. When footage or nested sequences are duplicated due to edits, though, there aren't really many tools to manage the duplicates yet. I think that's an area we need to look to see how we can improve things. I'll file a Feature Request to see what we can do. For now, I can think of a few workarounds for updating the Master Team Project, though none of them are ideal: 1. If there aren't too many segments, share the Master project so there's a named initial version, then delete everything but the links from the Main TP and re-import and reassemble the linked sequences. You can use the version history to get back to the original assembly as needed. Repeat as needed, sharing before each version. 2. Render the linked sequences and only import the rendered footage into the Master Project. 3. Store only bins at the top level of the Master Team Project, and quickly put any duplicate items into a new bin each time you update the master. This is because any duplicated footage or sequences are always put at the top level of the Team Project, so if you don't normally store footage or sequences at the top level, you can quickly spot the duplicates and move them to a better location. You can quickly separate the bins and links from the footage and sequences in the Team Project panel by enabling and sorting by the "Media Type" column in that panel. Unfortunately, I can't think of a more elegant solution at this point, though I'd be happy to hear if anyone has a better procedure. As I'll said before, I'll make sure we're tracking this issue if we aren't already.

PeterELee · ‎Dec 20, 2018

You have a couple of options for bringing everything together. The first steps, either way would be something like: 1. Create a Master Team Project that contains no media, only links to your other Team Projects. 2. When you create a new Team Project that holds footage, add a link to that in the Master. "File/New Linked Team Project..." lets you either select an existing Team Project to link to, or create one and link to it at the same time. 3. When you create a segment, create a new linked Team Project for that segment and import whatever footage you need for the segment into the segment's Team Project. It will ultimately contain a small number of sequences, plus the footage they reference. 4. When you're done creating segments, your Master Team Project will contain links to all of them, and to the footage "bins." Now you have a couple of choices to assemble everything: 5a. Render each segment individually, then import and assemble the rendered segments in the Master Team Project (or a new sub-master Team Project). or 5b. Create a sub-master Team Project and import the sequences from each segment into the sub-master. You can import sequences by dragging and dropping between Team Project windows, or using copy and paste. Importing a sequence will also import any footage or sub-sequences it uses. Assemble and render using the imported sequences and footage. or 5c. Skip the sub-master and just import the sequences into the Master Team Project. Does that make sense? Ultimately, if you only anticipate using a few thousand pieces of footage in the final product, you could just divide the raw footage / selects into a few Team Projects, plus one additional Team Project to hold all of the segments plus the footage that's actually being used. That way you won't have to worry about keeping a second copy of each sequence in sync between two Team Projects.

PeterELee · ‎Dec 19, 2018

Basically, yes. I find it easiest to think about linked Team Projects like aliases or shortcuts. If you split a project into multiple, smaller pieces, links help you organize and find those pieces. For example, if you normally organize your footage in bins, you could create a separate Team Project for each logical grouping that you would normally put in a bin (by day of shoot, camera, interview subject, what have you), In your master Team Project, you would create links to each of these footage projects. Now, when you're ready to create a segment of your program, you can create a new Team Project for that segment, dragging in the footage that you need for that segment from the "bin" projects. There are no hard and fast restrictions on the size of Team Projects, but opening and auto-saving is generally much faster in smaller Team Projects, with, say 2,000 or fewer assets. The biggest factor for auto-saving and getting latest changes is the number of new or updated items since the last save or sync, especially media files.

PeterELee · ‎Dec 19, 2018

Thanks for the info. I can't remember whether or not linked Team Projects were supported in 12.1.2. I think they were, but I'm not 100% sure. There are a number of stability and performance improvements for Team Projects in Premiere 13.0.2. While I understand that it can be risky to upgrade in the middle of such a large project, I would strongly suggest having an editor experiment with 13.0.2 when you have a chance, perhaps with a smaller Team Project or a copy of this one.

PeterELee · ‎Dec 19, 2018

When you say "it takes the other computers a very long time to update those changes," do you mean the time it takes for the "Get Latest Changes" button to light up, or the time they spend waiting in the progress dialog after actually getting the changes? If a bin is created, then the number of items in the bin will be a factor on that initial sync, especially if they reference many separate media files (as opposed to subclips from the same media file). A few other questions - roughly how large is the Team Project? Are you using Premiere Pro, After Effects, or both in the Team Project? Are you using the latest Creative Cloud release (Premiere 13.0.2 and AE 16.0.1)? If the project size is causing performance issues, I'd recommend splitting it up into multiple, smaller Team Projects. In Premiere, you can have multiple Team Projects open at once, so it's fairly easy to copy and paste between them. Premiere also allows you to organize a collection of smaller Team Projects by linking them. See Create a Team Project for more details. AE does not yet support multiple open projects or linked Team Projects, but you can still import assets from other Team Projects via the Media Browser.

PeterELee · ‎Dec 19, 2018

Good to know. As mentioned above, speeding up the initial auto-save after importing a large number of files is an area we're actively working on. It's tedious, but you might also have better results if you import the files in smaller groups, say a few hundred at a time, then wait for the asterisk in the Premiere title bar to go away, indicating that all changes have been auto-saved, before importing the next batch. The background processing that goes on when a media file "comes online" after an import can cause the auto-save operation to restart, so the more files there are, the longer it takes before an uninterrupted auto-save can succeed.

PeterELee · ‎Dec 18, 2018

taylorp67545410 What version of Premiere Pro are you using? Also, roughly how many media files are in your Team Project? One situation I know of where auto-save can take more than 5 minutes in the current release (Premiere Pro 13.0.2) is when you import or make metadata changes to a couple thousand media files at once. In those cases, it's usually advisable to let it keep churning along, and the auto-save will complete eventually once it has inspected all of the new or updated media files on disk and updated the database. We're working on improving the performance in those situations. You can force the auto-save to move faster by attempting to close the Team Project. The auto-save code normally does its best to stay in the background so as not to interfere with your editing, but if you close a Team Project it will put up a progress dialog and work more aggressively. In earlier versions, importing specific types of clips from other Team Projects or standalone projects could prevent auto-save from completing. Certain merged clips and multicam sequences were especially problematic. All of those issues that I'm aware of have been fixed in 13.0.2.

PeterELee · ‎Dec 18, 2018

In fact, it looks like the version of Premiere that contains the Team Projects label color fix has gone live. Are you still seeing label color issues in Premiere Pro 13.0.2, with labels applied using that version? If so, please let us know. The issue I was referring to is known to occur in Premiere Pro 13.0.1 and earlier. Version 13.0.2 was released a few days ago.

PeterELee · ‎Dec 18, 2018

Yes, sadly that is a bug for Team Projects in Premiere Pro. As mentioned above, we have a fix for the bug in-house that will be in the forthcoming Premiere Pro release, due shortly.

PeterELee · ‎Dec 17, 2018

Very interesting. The fact that you can import sequences via the Media Browser implies to me that there's a problem with a single asset, or maybe a small number of them. Have you tried creating a new Team Project and just importing everything from the main project? If that works, I would close the new project and make sure that it can open successfully, but perhaps that will get you past the block. I'll reach out via DM to see if we can isolate the problem further.

PeterELee

PeterELee

Activity

Re: Team Project Running Slow

Re: Team Project Running Slow

Re: Cannot Open Team Project?

Re: AE stuck opening a brand new Team Project

Re: Media drives never stop spinning

Re: Media drives never stop spinning

Re: Linking LocatorID error

Re: Adobe Team Projects - Media Management not sho...

Re: Adobe Team Projects - Media Management not sho...

Re: Media drives never stop spinning

Re: Media drives never stop spinning

Re: How do I share the media?

Re: Team editor deleted local sync files and now ...

Re: Team Projects: Issues with Auto Save and Shari...

Re: Lost Markers When Relinking in Team Projects

Re: Linking LocatorID error

Re: Linking LocatorID error

Re: Team Projects: Issues with Auto Save and Shari...

Re: Team Projects: Issues with Auto Save and Shari...

Re: Team Project won't save

Re: Long Update Project Items Time

Re: Long Update Project Items Time

Re: Long Update Project Items Time

Re: Long Update Project Items Time

Re: Long Update Project Items Time

Re: Team Project won't save

Re: Team Project won't save

Re: Label colors not preserved in Team Projects?

Re: Label colors not preserved in Team Projects?

Re: Team Project stuck on "Processing loaded asset...