Highlighted

Premiere Connecting to the Wrong Media after using Replace Footage

Participant ,
Oct 06, 2019

Copy link to clipboard

Copied

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:

 

https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/38734459-premiere-connectin...

 

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

TOPICS
Error or problem, Import, Performance

Views

303

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Premiere Connecting to the Wrong Media after using Replace Footage

Participant ,
Oct 06, 2019

Copy link to clipboard

Copied

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:

 

https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/38734459-premiere-connectin...

 

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

TOPICS
Error or problem, Import, Performance

Views

304

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Oct 06, 2019 2
Adobe Community Professional ,
Oct 06, 2019

Copy link to clipboard

Copied

Are you using a Shared Project process and project structure?

 

Neil

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Oct 06, 2019 0
Participant ,
Oct 06, 2019

Copy link to clipboard

Copied

Hey there Neil,

 

Nope to Shared Projects. We never use that functionality at all.

 

After saving the project, the user would either quit Premiere completely, or close the project, and only then would it be opened on the other system.

 

The other user is opening the same project file, so the structure, etc, is the same (I may have misunderstood this part of your question though 😛 ).

 

Cheers,

 

Darren

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Oct 06, 2019 0
Adobe Community Professional ,
Oct 06, 2019

Copy link to clipboard

Copied

Use the blue reply button from the too post or this forum nests them.

 

I don't understand why you're not using the Shared Projects process. With each user having their login name, and any part in use automatically locked, it makes for a very handy and safe process. And is built to do exactly what you need, easier and safer than everyone opening up the same project with unknown bits saved locally and not on the server. Which I suspect is at issue here.

 

In my experience "shared" changes are pretty solid too.

 

Neil

 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Oct 06, 2019 0
Participant ,
Oct 06, 2019

Copy link to clipboard

Copied

Hahaha, we gave shared projects a go a while back, and ran straight into trouble, and have been pretty gun shy since 😛

 

 

Regarding locations, that's the thing, none of these files are stored locally. They're most commonly saved right next to the original files. Sticking with the music example earlier, let's say that we have our standard project folder structure on the server, we'll have a music folder, and the licensed file is saved right into there next to the demo track (different file name, and different extension, of course).

 

I wish that it was a case of the file being saved locally, but it definitely isn't. Thinking about it, even if it was a case of something saved into the wrong place, wouldn't that trigger the "reconnect media" dialog? It should be looking for a file with a different name, so I really don't know why it would be reverting back to an old file.

 

This is something we have only seen since introducing both Macs and PCs into the environment.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Oct 06, 2019 0
Participant ,
Oct 06, 2019

Copy link to clipboard

Copied

Adding a bit more info - I just remembered another bizarre bit of behaviour:

 

When we replace the footage, save, and close, and then open on OS B, the timeline will show the updated filename, but will definitely be using the wrong file.

 

If we reveal that clip in project, it shows the correct file in the bin, however if we reveal in Finder/Explorer, it takes us directly to the incorrect file.

 

So, yeah. Weird. Premiere will be showing that it's using the correct file, but heading to the actual file shows that things are not right in Denver.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Oct 06, 2019 0
Adobe Community Professional ,
Oct 06, 2019

Copy link to clipboard

Copied

I really do think the problem is the wrong project format. Individual projects assume they are saving things locally. You got by on one OS probably after a fair amount of experimentation.

 

But individual projects are not coded for how you are using them.

 

Shared projects are coded differently assuming all critical files are on the server. Try the Shared project system and see if it works better. I'm pretty sure it will.

 

Neil

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Oct 06, 2019 0