Skip to main content
P
posy134
Participant
July 2, 2020
Question

Team project changes not syncing

  • July 2, 2020
  • 2 replies
  • 2435 views

A colleague and I are working on a Team project. This is our second Team project, so we are still fairly new to the workflow.
I worked on the project last night and shared my changes. My colleague recived my changes, and today she's made and shared some changes, and I received notification of it. When I open the proejct, the sequence is showing white pencil status, even though I don't have unshared changes that I know of since I shared last night. I go to Team Project -> Get Latest Changes, see that the asset (our main sequence) has changed as expected, and choose "Take the shared version. The shared version replaces your version". Premiere Pro chugs for a while, but I end up not getting her changes, and my sequence still has the white pencil icon.
In the hope of starting with no local changes, I tried renaming my "Team Projects Cache" and "Team Projects Local Hub" and opening the Team project again. Although new Team Projects Cache and Team Projects Local Hub folders are created, I'm immediately in white-pencil status again as soon as the project/sequence opens, and I don't see my colleagues latest shared changes.
I'd be grateful if someone could point us in the right direction to get out of this situation. I'm looking to throw away any local changes I have, and to be in sync with the latest shared version. She's on a Mac, I'm on a PC, and we are both on the current release.

 

[Moderator note: moved to appropriate forum.]

This topic has been closed for replies.

2 replies

U
Adobe Employee
Udo_Pawlik
Adobe Employee
July 7, 2020

Hi,
You could try to have your colleague use 'Save As...' to create a new version of her Team Project state and invite you as a collaborator. If the issue persists it would be great if you could invite myself (upawlik@adobe.com) to that team project as well so I can try and reproduce the issue on our side.
Also, do you use any 3rd party plug-ins in this Team Project?

Regards,
Udo

    P
    posy134Author
    Participant
    July 20, 2020

    Hello Udo,
    Thanks for the response. We did end up creating a new project from a prior version which got us around the issue. As I mentioned in my response above, it's sometimes not immediately clear whether the other person's changes have been successfully received or not. I'd certainly like to figure out what's going on so we can just avoid getting into this situation in the first place!
    We do use one third-party plugin, IR1 Convolution Reverb by Waves (https://www.waves.com/plugins/ir1-convolution-reverb).
    The issue happened again this week. I could not sync her changes despite choosing "Take the shared version. The shared version replaces your version". I've invited you to have a look at our 20200719 project.
    Her last changes before handing the baton to me were v27.  I ended up not being able to sync all her changes, and ended up doing them all again. My changes are v28 and onward.
    To avoid conflicts we've been working entirely serially (i.e. her during the day, and me in evenings), but still we're running into this sort of trouble. Any thoughts would be much appreciated!

    Thanks,
    Bruce

    R Neil Haugen
    R Neil Haugen
    Legend
    July 3, 2020

    The US based Adobe staffers are on holiday through Sunday, sadly. We typically get one of the lead TP engineers helping with this sort of issue. I'll give a few idears for you to try.

     

    First, just dump the cache/cache database files for Premiere in general. Premiere will rebuild anything it needs as it needs to.

     

    Second ... have you tried using the TP version history process to revert to an earlier version of the project, that doesn't show the pencil ... then syncing that one?

     

    Neil

    Everyone's mileage always varies ...
    P
    posy134Author
    Participant
    July 20, 2020

    Thank you. I'll try dumping the cache files to see if that helps.
    We have used the "make a new project from a previous version" feature successfully for a similar issue, but without explicit communication each time it's difficult to know if we've received all the changes. I'd hoping to eventually learn what we are doing that lands us in this situation so we can avoid it. I'll reply below to Udo as well. Thank you again.

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