Skip to main content
wallacewhite
Inspiring
June 18, 2025
Answered

Circular editing locks on all sequences

  • June 18, 2025
  • 2 replies
  • 498 views

I have a team of four editors on a Team Project. We just finished a very similar Team Project without difficulty, but this new Team Project has run into immediate trouble. I would appreciate help from @Udo_Pawlik or anyone. Udo, I can invite you to the Team Project if you'll please tell me how.

 

The problems: 

  • Premiere is showing editor 1 that editor 2 is editing every sequence in the project—but it's showing editor 2 that editor 3 is editing every sequence, a nonsensical circular ring of locks. No editor would be intentionally editing every sequence. Even if someone goofed with media mapping or relinking, as I've seen happen before, I don't think that every sequence would be affected.
  • Last night Premiere showed me that one editor was editing everything, but now it shows me that a different editor is editing everything. 
  • One editor reported that he had only just opened the Team Project for the first time when Premiere showed a "Save A Copy" dialog: "You have 1100 sequences with unpublished changes that were edited by your collaborators. Your unpublished changes will be saved as new sequences." He exited without publishing, tried again, and got the same warning. On the third try, there was no such warning, but (as in my first bullet) all sequences were being editing by another editor.

 

The project:

This project, like our last, has a large number of sequences (1100) but not a particularly large total length of video (600 minutes). Within the Team Project are essentially 100 little projects. Each has a main sequence with nine sub-sequences, one multi-cam sub-sequence, and two clips that are each three minutes long. The successful previous Team Project was organized identically and worked well. I created both from the same template by using the excellent Automation Blocks. When I click on Premiere's cloud sync icon in the middle of the title bar, it shows me a green check: "Project saved and synced. Last synced 4 days ago." 4 days ago is when I created the Team Project, but it's an oddly long time ago given that the four of us have all accessed the project in the last day and Premiere is showing locks. In Creative Cloud's notifications, I only see that each editor "has joined" the Team Project; it doesn't list that anyone has "shared changes" to it.

 

The environment:

All of us are using Premiere Pro 2024 v. 24.6.3 or higher but not 2025 (I've waiting for the other editors to confirm their specific versions) on a mix of Macs and Windows machines.

 

Thanks for any help,

Wallace

Correct answer wallacewhite

3rd update: Adobe says they've corrected the bug in the Team Projects service. No details were provided.

2 replies

Udo Pawlik
Community Manager
Community Manager
June 27, 2025

Hi @wallacewhite
The most common cause for un-intentional edits are due to issues regarding re-linked assets and automated features.
If you get into a state where you constantly are asked to publish changes or get duplicated sequences it might help to start fresh via 'File > Save As' and keep following items in mind. 


- Each collaborator should be on the same version of PPRO
- Turn off 3rd party plugins that automatically edit a sequence or asset
- Turn off the Audio preference – “Auto-tag audio types in the timeline”
- Collaborators should re-link media by creating a machine specific media mapping via the Media Manager (Edit > Team Project > Media Management...) and bypass/cancel the 'Relink Media' dialog when it presents itself

- Break up a project with many sequences into multiple, smaller linked Team Projects and avoid having too many backup sequences in your project [_v1, v2 etc.] 

-Udo


wallacewhite
Inspiring
June 27, 2025

Thanks, @Udo Pawlik.

 

I can't rule out the possibility that an editor accidentally re-linked, but the team has all used media mapping and should have known not to. On our first Team Project, I did experience that an editor had mistakenly re-linked instead of mapping, but the symptoms of that were clear and quite different from the experience that I posted about here. And Adobe support did say there was a bug that has been resolved, though with no details. My case number was ADB-40430517-F3T8.

 

Thanks for the guidelines as well. I'd like to use Team Projects again on some future project if I can do so with confidence.

 

Wallace

 

wallacewhite
Inspiring
June 19, 2025

Update: I gave up on Team Projects for now.

 

I chatted with Adobe Support (a test of patience). They didn't identify a cause and I wasn't confident in their suggestion that I simply try a new Team Project and see if the problem recurred. The features of Team Projects are perfect for my purposes, but I couldn't take chances on having more problems and lacked the time to investigate Productions, so I found an admittedly awkward, old-fashioned way to divide the project into one project file per editor until a final integration step.

wallacewhite
Inspiring
June 19, 2025

Further update: Adobe called and confirmed that this is related to a bug affecting multiple users. They're working on it.

wallacewhite
wallacewhiteAuthorCorrect answer
Inspiring
June 26, 2025

3rd update: Adobe says they've corrected the bug in the Team Projects service. No details were provided.