Premiere Team Projects giving me "View only" even though I am the only editor online

[evanf37738972]

Hello,

I've been encountering this issue where Team Projects puts me in "view only" mode for all of the sequences in my Team Project even though I am the only editor online working at that time and all of the changes from my collaborators and myself are up to date and published. I also receive this even when there is another editor online, but they are working on a different sequence from me. I know Premiere locks sequences with "view only" modes so that two editors don't create conflicts within the same sequence, but it comes up for me even though my collaborators are working on a completely different sequence from me. It seems like Premiere is booting me from editing the sequence because I am editing it...  ._. Very frustrating because I can't do any work!

I am running Premiere v25.1 and Mac Sequoia 15.1.1. Anyone else having this issue? Thank you!!

[Udo_Pawlik]

Does it mention which collaborator Premiere thinks is working on the sequence? Either in the 'Changes' column in the Team Project panel (list view) or at the top-right when opening the a sequence in the timeline. Can you make sure the this collaborator has published all pending changes?
In the meantime you could duplicate the sequence to get work done.

[evanf37738972]

It usually starts by saying "Evan (me) has edited this sequence" and then it goes into "view only" mode. Then all of the sequences become view only. Sometimes it even happens when there has not been a collaborator that has made any changes to the project. I've tried publishing my changes when this happens and it remains in "view only" mode. Tried troubleshooting with my collaborators having them publish all their changes, updating on my end, and having collaborators closing all the sequences in their project and still persists.

Duplicating the sequence does work as a workaround for now thanks!

[evanf37738972]

Addendum: I'm being shown also that the source file is also read-only. First time ever encountering this, not sure why.

[Udo_Pawlik]

Thanks for the additional info. 
We recently addressed an issue that fits your description. If you get the chance you might want to try the  PPRO_25.2_Beta build which can be installed side-by-side with the release version via Creative Cloud Desktop.

[evanf37738972]

The beta application seems to have fixed the View Only issue in the sequences. But now I am still encountering a "read-only" issue of the source clip itself. Any workarounds for this ?

[evanf37738972]

Update - even in the beta Premiere Pro it started doing the view only issue in the sequences again.

[khadgapa]

Have you noticed that "audio gain" doesn't work on clips in the timeline? It seems to have no effect anymore?

[Tyler297020287rlk]

Yes, I'm seeing that audio gain issue within timelines that are marked View Only.

[Kcaudill]

This has been DRIVING ME CRAZY today. I basically have a team project that is inoperable due to this. Sequences seem to be fine, but clips (audio, video, music, etc.) start to display read only several seconds after getting into the project. My theory is that, somehow because of this, I can no longer adjust the clip gain in my timeline or set audio channels. In fact, the "Audio Channels" option is grayd out on clips in my timeline. (The timeline is not read only and I can make other changes...)

I was trying to do a finish pass on another editors cut today, and everytime I wanted to adjust the gain or set audio channels I had to restart Premiere, adjust a few clips... then it stop letting me do it, so I'd restart again and get a moment or two of proper functionality. Don't get me started on the solo and mute buttons not working anymore either. This is killing everyone on my team.

@Udo_Pawlik any updates on this?

[Udo_Pawlik]

When an asset is being used in sequence which is currently being edited by someone else, you won't be able to modify clip properties (add markers, attach/detach proxies, modify gain, color or metadata). Sure, looks like a bug especially when that clip status shows as 'Up to Date'.

[Kcaudill]

Are you saying this is intended behavior? We've been using team projects with multiple editors for a long time now. This is a problem in version 25 (and the beta). Not being able to modfy the gain of a clip in a sequence is a new problem and a quite necessary feature. The sequence I'm working in is not locked or read only.

[Udo_Pawlik]

I'm not aware of intentioanl changes or behavior in this area in recent releases. 
I can edit audio gains of a clip in a sequence if the sequence is not being edited by someone else or if I'm the one editing it.
However, I am able to get into a state where my sequence status is incorrectly shown as 'Up to Date' although it's being edit by another collaborator (close and re-opeing the project refreshes the sequence status).

• When you open the sequence, does it show 'Up to date' in the timeline and 'Changes' column in the Project panel when in list view and does the it show the same after closing and re-opeing the project?
• Are you able to modify audio gain if you're the only one in a team project (Create a Team Project don't invite others)?

[Kcaudill]

The sequence shows as up to date.

Restarting Premiere and reopening the project usually allows me to edit the clip gain or use the solo buttons correctly for a few seconds, then I appear to be locked out again. The sequence shows up to date.

If I'm the only one in the project, I can then change the gain and the solo buttons work.

Unfortunately, my company now has several different projects that we can only work in if we're the only editor. So basically, we've completely lost the ability to work in our team projects collaboratively. 

[khadgapa]

This is the same for us on our team. Premiere Teams is no longer a usable option. We can only have dependable functionality working within a team project if all the other team members close their project. So basically, Adobe Teams is only good for saving the trouble of sending someone a project file. 

It's sad because we advocated hard for Teams on this project and many of the editors are now swearing they will never touch Premiere again if they can help it. This release is a disaster for Teams. Like literally, you can't work. It would be like opening your toolbox at work and your hammer has become a spoon, and your chisel is suddenly a spatula. Craftspeople reaching for their tools so that they can perform their craft, only to find that the makers of the tools have turned them into useless imitations of their former utility.

I used to scratch my head at how long Avid would take to do anything new with their software, but I kind of wish I had just become a big editing house avid editor all those years ago instead of doing the indy route with FCP 1.0-7.0 & X, Premiere 10.0-25.0, Da Vinci etc.

When an Avid editor reaches for a chisel, they find a chisel, when they reach for a hammer, they can drive a nail. This level of software failure on the most basic editing tasks is maddening and an insulting failure of the contract between a craftsperson and their tool vendor.

[Kcaudill]

The sad thing for me is that, we've been using Team Projects for years, and there is ALWAYS a problem, but we're usually able to figure out how to work with that problem and around that problem. I'm the lead editor and I manage post, so I've always solved these issues for my team and made it work. I guess if you have a problem solver on your team you can make it work... at least until version 25. We're now stuck.

@khadgapa I feel you, because I too have always pushed for Team Projects, but just recently after onboarding a new editor to an inoperative project, I'm embarrased for my company and my post department. I'm sick of trying to tell editors to "trust me" that it will work and now, it just doesn't.

[CiscoLC]

I’m also experiencing this exact problem. I was nesting something in the sequence, and when I opened the nested sequence, it immediately showed as “view only.”

Usually, if I’m the only one online working on the project, quitting and reopening it makes it editable. However, now that someone else is working on the project at the same time, that trick doesn’t work anymore.

What’s even weirder is that now, when I reopen Premiere, the entire nested sequence appears to be offline, with no file path. You can’t even relink that file because, how do you even relink a nested sequence? It’s not a file in itself.

[CiscoLC]

I think the reason it appears as “view only” when I create a nested sequence is that any audio clip I had on the timeline was read-only for some reason.

This is very confusing and frustrating.

[Shapeshifter12]

Yes, I am having it now on my last few projects. Really infuriating when on deadline and I have to keep copying sequences, making notes so team uses the right ones. Replaying the "view only" sequencies and really causing a lot of confusion. I'm on 25.1 and on Monterey.

[Kcaudill]

While the insane amount of sequence duplicating in Team Projects that started happening in past versions of Premiere seems to have been fixed, it still happens sporatically (probably for different reasons) and it's still dibilitating once Premiere gets into a cycle. I also don't understand files being marked read only just because another user might have it in a sequence (a camera original, music track, graphic element). That just will never work. It really feels like the "Teams" part of Team projects needs a major overhaul and rethink based on professional workflows.

Long story short, we're now on local projects for most of our work awaiting major improvement.