I'm currently working on a project for a client. We shot on a Canon C300 Mk II and at 25 and 50p. We had our sound guy send us the dailies and synced them using Tentacle Audio Studio, then importing the .xml into Premiere. The SyncMap sequence was 50p. After selecting the good footage I made a subsequence that was 25p and began building the edit.
The issue is that when the project is saved and then reopened, all the audio gets shifted along, losing the sync completely, and some clips are blocked out with the danger (diagonal) lines. They can't be made offline and relinked, as the lines just remain on the clip. I'm currently working on the project collaboratively and a colleague has the same issue when opening the project on his system. So I have had to leave my project open and leave my workstation on, until we can find a solution.
Has anyone seen this issue before?
I'm editing on a 16-inch 2019 Macbook Pro with Mac OS Big Sur, 2.4GHz 8-Core Intel Core i9, 64GB DDR4, and an AMD Radeon Pro 5500M 8GB.
The issue occurs when import/ingest is done improperly with certain cameras. Cameras that generate media files to certain card based media like yours need extra consideration. The heart of the problem: these cameras generate clip names that are identical. Clips are also "spanned" and are rejoined in Premiere Pro with the assistance of metadata. So, when it comes to solving the issues of identically named clips and spanned clips - Premiere Pro requires their metadata.
For Premiere Pro to differentiate between identically named clips, it needs their metadata. For these cameras, the editor must ingest the footage via Media Browser so that the media can carry the metadata that was generated when the clip was originally recorded. Otherwise, if the clips are merely imported via dragging or File > Import, that metadata is then not brought along, is lost, and remains in the folders with the other metadata. It is then not referred to and will cause issues in relinking, especially if the media is further manipulated or moved from one drive to another.
Since Premiere Pro uses that metadata to differentiate between one media file or another via imported metadata that comes along with the clip, and if the metadata was never imported, the file has no information to differentiate it from another one with the same name. Whomever is handling your clips really needs to know this information or the situation you are in occurs and must be fixed manually, which is very time consuming. Most clips must be relinked properly one at a time.
At the outset, this issue does not present itself until multiple storage systems are used and the media is moved from one system to another. Here then, identically named media files are introduced into the media move. Premiere Pro becomes confused between multiple clips named the same things (there might be multiple instances of "Clip 001," for example), and without the additional metadata the media file carries by a proper ingest, Premiere Pro throws up its virtual hands and says, "I don't know if Clip 001 goes here or Clip 001 goes there - you figure it out - here's some hash marks showing your where I had problems."
I think we are missing some crucial pieces to the story and there may be further complications if you intend to pass the project back to audio post. Audio post used a tool to sync your second system sound. How was this done precisely? Was the footage already ingested by you or the audio post house? Have you used this tool successfully in the past? Did it create your clips based on merged clips or with multicamera sequences? If you are interacting with audio post, and you plan to collaborate, it should be the latter.
I would say that many people get themselves into this situation, and I'm sorry it happened to you. It is difficult to fix issues like this, so, sorry about that. Let the product team know about your pain on the User Voice sight. Add any requests for future workflows there.