Footage that is right clicked/replaced keeps linking back to the old files when my colleges load up the project. Even though the new files and old files have different names too.

So for example, if there is a preview stock clip named "StockX-preview" in a PP sequence and I right click/replace footage with the purchased high res version "StockX" it will change out the footage on my computer and everything works as expected. Though when any of my teammates open the updated project, the project will link back to the old "StockX-preview" files instead of the correct "Stock X" files. Also something to note, for some reason it will still show the old names when they are trying to linking broken media instead of the correct high res videos.

This also happens when switch out a dynamic linked AE project by offlining and relinking to the an update AE project. So going from "AEProject01" to "AEProject02" works fine on my end though when they open the project it links back to "AEProject01" and doesn't even show the "AEProject02" when relinking broken media.

This is happening when going back and forth between PC and Mac.

When Reassociating a selected sequence in a project within a Production, currently you have to open one [media] project at a time and for all sequences in each [editing/sequence] project.

What would be nice is if we could open a project full of sequences, select them all and then 'Reassociate Master Clips with All Open Projects". That way we could have open already our media projects (which we can open all at once) and then do a big 'reassociate' all in one go. (open to even more simplified suggestions like 'Reassociate with all projects in the Production' or a function like this at Production panel level - e.g. highlight a bunch of projects and choose 'Reassociate projects with all other projects'

-Additional info:
I'm working on a large documentary with footage shot over several years. The project got too big to handle and there are now two people working on it simultaneously so we broke down the project into a production Sith 7 Media projects and several Editorial projects containing sequences of compilations, assemblies and various iterations of the master edit. Breaking down the original project into smaller parts causes ALL the sequences to lose their associations with media because they think they are still in the original oversized project. If you 'reveal in project' any clip in any of the sequences, it asks for the original project. So you Reassociate Master Clips, in our case, 7 times for each project containing sequences! - you can see why this would be handy to be simplified for anyone making a documentary that grows larger than initially expected - good doco's always do!

Thanks for your consideration.

At my work we export a fair amount of XMLs. When I receive a Premiere file from a coworker and open it on a different computer, it gives me the missing media popup every time I open the project, even if all the other media is online.

The "offline media" is FCP Translation Result .txt files, and the file path is always "/Users/(username)/Documents". There's no "Clip Name" displayed, since they're not stored in the project panel, or anywhere user-facing. This happens anytime the Premiere is unable to locate these .txt files.

It's not a big deal to just Offline All and move on with your day, but it is an annoying and unnecessary step.

Would it be possible to have these missing Translation Results not appear in the Missing Media popup window, or perhaps just have them not linked at all in the Premiere Pro project after exporting the XML?

Hello All,

We experience big issues between Mac and PC. Mostly with big projects (keep in mind we are on big network storages). When we try to open a Mac project on a PC, most of the time we get network timeouts, we get into an infinitive loop. And can take hours before the locate window appears . SO If adobe could make that timeout way faster would be a good step or There should be a Mac to Windows path statement that can be entered somewhere in Premiere or After Effects. For example a Mac created a project with media located @ /Volumes/mysandrive/myrootfolder/myprojectfolder/mymediafolder. That path won't exist in a Windows environment.It would look like this: G:\mysandrive\myrootfolder\myprojectfolder\mymediafolder.
All of the suggestions listed above may work if you have production machines connected to the internet. Volume of work, security of your content and un-aired content may make those suggestions non starters.
Furthermore, Adobe building in Mac Windows shared inter-operability ensures editors aren't spending time re-linking instead of editing.

We also have a problem here with reassociating master clips
In our case an external editor has edited a sequence outside of our production in Final Cut Pro X. Hes's given us an XML (converted with XtoCC). I've tried several ways to tie this edit into my production:

1 - Create a new projekt in my production
- import XML and leave all footage offline
- reassociate clips in timeline to Masterclips which is in a seperate footage project inside of our production

2 - Create a new projekt in my production
- import XML and link footage to local footage
- reassociate clips in timeline to Masterclips which is in a seperate footage project inside of our production

3 - Create a new projekt in my production
- import XML and link footage to local footage
- copy sequence to a new project in our production
- reassociate clips in timeline to Masterclips which is in a seperate footage project inside of our production

4 - Create a new standalone projekt OUTSIDE of my production
- import XML and leave all footage offline / link all footage
- Add that project into my production
- copy the sequence to a new project in my production
- reassociate clips in timeline to Masterclips which is in a seperate footage project inside of our production

The clips always refer to the master clips in the imported project, not my footage project. If I move the import project to the Trash before reassociating I get the error message "The project with this media can't be found" as soon as I try to reveal a clip in the project.

The Editor has used the same Files as we have here. I was wondering if it had anything to do with XMP Metadata. So I did everything again, deleting my footage project and re importing one time with XMP and one time without. Still no luck! It just wouldnt reassociate in both cases.

Reassociate worked well though when adding a local project from which we needed a sequence that was edited before we switched to productions.

It would be really helpfull if there was feedback as to which clips did get reassociated and which didn't, also with a reason why id didn't get reassociated. Now it's like fishing in the complete dark.

Thanks

Andy

What the **** is going on? Since I got this paid license, there's nothing but trouble. I AM the owner of the TEAM Project. I made the last changes yesterday evening. Now, I got an automatic Premiere Pro update (both the beta -15.4 buld 19 and the regular app) 15.2 build 35 -) and now It says it is an "Unsupported Project Version", claiming that the project was edited in a newer version.... That's insane! Yesterday there was the beta build 18, and now, with the newer version, premiere pro says this nonsense. I REALLY need to get my project back on the tracks.

I desperately wished Premiere's "Collect Files and Copy to New Location" feature would have an option to preserve the folder structure of the original files when copying them to the Destination Path.

Unfortunately tapeless workflows have made proper media management practices a total nightmare, especially when working with outside editors or clients who do not have sensible media management systems in place. This often results in media with duplicate filenames, etc., and as a conformist/colorist, I need to be able to determine the type of media (original camera format, shoot date, proxy/original transcode status etc) based on the information in the original folder paths the media was located in.

But if you "Collect Files" on a sequence, Premiere will just dump all the files from that sequence into a single folder without the original source paths. So you lose all references to where that media originally came from, which is important information to know for both troubleshooting and many other tasks.

Right now, I will either use Davinci Resolve (whose Media Management tool allows you to collect media while preserving original source paths), or a custom command-line shell script which does the same thing based on an XML export of the timeline. However, I hate having to make Premiere editors have to download, install and learn how to use Davinci Resolve just for this simple task. If you were able to do this, simply by ticking a checkbox in the Project Manager window, that would be a huge workflow win!

Subclips should be traceable back to Masterclips. If you can track duplicate clips across projects in Productions, then surely it is possible to create a link between the source master clip and subclips. It seems that forums and even Adobe staff are recommending against using subclips and nodes does seem to be using them for this terrible reason. While on this subject the behaviour of subclips and the Project Manager is a nightmare - every subclip (or sequence clip) in a project results in a another copy of the underlying media. So single promo made out of 100 clips from the same taste clip results in 100 copies of the same media if sent to the Project Manager.