Skip to main content
peidshjt
peidshjt
Known Participant
January 28, 2025

Team Project - View-Only / Read-Only multicams that are "Up to date"

  • January 28, 2025
  • 5 replies
  • 611 views

Mac M1 Max

OS - Sequoia 15.2

RAM: 64GB

 

Premiere Pro 2025.1

 

In the team project... multicams are showing as view-only / read-only...

 

No other collaborators are altering the sequence, the tracks are locked. All collaborators have published/updated the project and that does not correct it. The asset is showing as up to date, with none of the collaborators working inside of the asset (typically, you see the collaborators icon next to assets they are working on)

 

This is specific to multicams. When it is read-only, it does not allow you to lay in markers / adjust gain in a sequence where the MC lives / lock tracks in a seq where the multicam lives / set in and out in the multicam that is showing as read only.

 

Occassionally a restart of the project solves it, but inconsistently. Occassionally a restart of the system solves it, but also inconsistently.

 

This is a huge speed bump, and I've seen others posting about this same issue on other forums.

Please patch.

    5 replies

    A
    Andrew C. Brinsmead
    Inspiring
    October 28, 2025

    In my current production project, often when I match frame from an edited multicam clip in my timeline to load the source multicam clip into the source monitor, the clip name is showing as "(read only)", and I can't add or change mark in or mark out, alter markers or camera angles.

     

     

    I'm working in a production project, and my multicam source clips are stored in a different project to my edit project, but I'm the only person accessing this production project, and there is no indication that any project is locked

    Tech specs

     

    MacBook Pro (16-inch, 2021)

    Apple M1 Max

    64gb ram

    Mac OSX 15.3.1

    Premiere Pro 25.1 / 24.6.4


    I'm not the only person to report this - here's another person reporting this problem in January 2025: 


    https://community.adobe.com/t5/premiere-pro-bugs/team-project-view-only-read-only-multicams-that-are-quot-up-to-date-quot/idi-p/15117617?utm_source=chatgpt.com

    A
    Andrew C. Brinsmead
    Inspiring
    October 28, 2025

    Source window markers keep defaulting incorrectly

    I'm working in a productions project, and I've found that very frequently my markers in my source monitor will keep defaulting to a previous marker point. I'll add a new marker, and it will disappear and be replaced by a marker at a position which I've marked previously. 

    Deleting my system preferences doesn't fix this (I'm deleting my system preferences several times per day at the moment, which is very time consuming to reset afterwards; there's a few problems that keep occurring - the markers defaulting to other positions, and both my text window disappearing transcripts and my marker window not showing markers)

    I've noticed that this problem seems to be happening when I've match framed from a clip in an edited sequence back to a (multicam) clip in the source monitor; one work around that I've found is to find the source clip in my project, load it and manually match the timecode (which kind of defeats the purpose of having match frame as a function).


    I've attached a video to show the problem.

    I'm editing in a production project; I'd love to know if there's a way to reset the master productions project if that's the problem

    MacBook Pro (16-inch, 2021)

    Apple M1 Max

    64gb ram

    Mac OSX 15.7.1

    Premiere Pro 25.5.1

     

    J
    jesseJTtodd
    Participant
    March 4, 2025

    Based on @Udo_Pawlik description, I was able to find a very temporary solution:

    1.  Close out of all sequences in the timeline window.
    2.  Publish changes using the Publish button in the project panel.
    3.  Quit Premiere Pro and open again.
    4.  Do not open your main editing sequence, but you should be able to open your multicams in the timeline.

    Obviously not an ideal solution, it's still a bug that needs to be fixed. This gave me the ability to change what I needed to for this project though. Hope that helps!

      U
      Adobe Employee
      Udo_Pawlik
      Adobe Employee
      January 30, 2025

      Hi @peidshjt,
      Sorry for your troubles, I'm able to reproduce the issue on my end. 
      The problem seems to occur when the multicam source is being used in any other sequence which is currently being edited. I'll create an internal bug for this issue. 

        K
        Kcaudill
        Known Participant
        January 27, 2026

        Is Adobe actively working on this or is a fix in the pipeline? We continue to face this issue even using the most recent Premiere version.

        peidshjt
        peidshjtAuthor
        Known Participant
        January 28, 2025

        Yes. All up to date. Only on multicam.

        IanB_360
        Community Manager
        IanB_360Community Manager
        Community Manager
        January 28, 2025

        Hi @peidshjt 

         Thank you for taking your time to file a bug report. We would like to help figure this out with you. Are all users on the most current version of Premiere Pro and Creative cloud suite? And is the issue only with the multicam sequences ? 

        Thank you

        Ian

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices