Premiere Connecting to the Wrong Media after using Replace Footage
Hey there,
We are running into a really frustrating bug.
The basic problem is this: When working in one OS, if you replace an asset, save the project, and open the same project in another OS, the "replace footage" command will have been forgotten, and you will have reverted back to the old asset. Pretty scary if you're working in a team, and all of a sudden the next person dealing with the edit is inadvertently working with incorrect media.
I've posted this to UserVoice here:
A bit more detail on the issue:
In our office environment, we edit off of a server, and have done so for a long time now, without issue.
All systems used to be Macs, but we've started introducing some PC systems into the mix, and now we're starting to run into complications.
This is one of the more gnarly complications. To recreate the bug, we just follow this simple procedure:
1) Create a project in OS A (could be Mac or Windows), and then edit something.
2) Replace an asset in the timeline.
3) Save the project.
4) Open the same project in OS B (the opposite of whichever you chose in Step 1).
5) Marvel as your clip (replaced in Step 2) is linked to the old media.
Please note that the file name for the new media is completely different to the original, and often the codec is different as well.
A typical edit sees us using watermarked music in the early stages, and then once the client has approved the music, we will license the track, and replace the watermarked asset. So, it's not uncommon for the file names to change like this:
"demo_music.mp3" changes to "final_music.wav".
This only seems to happen with media that has undergone the "Replace Footage" treatment, and this never used to happen when we were only using the single OS.
Update (19/10/10):
One thing which I haven't previously mentioned is that this wasn't happening before the most recent update.
We've tried testing with Shared Projects as we were advised that this could help, but we had no luck, and ran into the same issues.
We also tried brute forcing our way around the issue, but unfortunately failed again. I'll explain, using the music example again.
When replacing demo music, instead of putting the licensed file into the same folder as the demo track, create a new folder, and put the licensed track in there. Within Premiere, use the replace footage command to link to the licensed track in the new folder. This should make Premiere look for 1) a new filename, and 2) a new folder.
No luck, unfortunately.
System Information:
All systems are running the latest Premiere release (13.1.5)
PC:
Windows 10 (1903)
Intel i9-9900X
64 GB RAM
Nvidia RTX 2070 (431.36)
Mac:
OS 10.14.6
iMac Retina 5k, 27-inch, late 2014
4 GHz i7
32 GB RAM
AMD Radeon R9 4GB
If you need any further information, please don't hesitate to ask. I'm happy to provide whatever might be needed. This is definitely something that is concerning us.
Cheers,
Darren
AdChoices