Overwrite file command not adhered to.

[UCKG5FD4]

When I send any file to the queue from Pr or AE after I specifically told the programme the file needs to be replaced, Media Encoder does not respect that decision and adds "_1" behind the chosen file name for a newly created video file.

How can I tell Media Encoder to stop doing this?

[David Arbor]

There's an option in the AME prefs under General > Output called "Increment output file name if file with same name exists." Uncheck this and you should be good. 

[ricar2]

Hi David. When I use this option, ME usually fail to render. Might be a windows permition thing, is there a way to force it to always overwrite the prev version?

[David Arbor]

Interesting. When AME fails it notes the failure in the log. You can hit Ctrl+L or click the "Failed" text on the right of your job in the Queue to open the log. What is the error? I've never had this happen before with the pref enabled, and permissions are certainly a possible cause here.

[ricar2]

Hi David this is what I got from the log

------------------------------------------------------------

Encode failed because the file D:\Dropbox\Manga_\WMCCNNGM202208301439 - ACDELCO\02. PRODUCAO\03. AFTER\adelco_AME\Confianca.mp4 can't be overwritten.

- Source File: D:\Dropbox\Manga_\WMCCNNGM202208301439 - ACDELCO\02. PRODUCAO\03. AFTER\adelco_AME\tmpAEtoAMEProject-Confianca_1.aep
- Output File: D:\Dropbox\Manga_\WMCCNNGM202208301439 - ACDELCO\02. PRODUCAO\03. AFTER\adelco_AME\Confianca.mp4
- Preset Used: Match Source - High bitrate
- Video:
- Audio:
- Bitrate:
- Encoding Time: 00:00:00
08/31/2022 12:45:13 PM : Encoding Failed
------------------------------------------------------------

Encode failed because the file D:\Dropbox\Manga_\WMCCNNGM202208301439 - ACDELCO\02. PRODUCAO\03. AFTER\adelco_AME\Confianca.mp4 can't be overwritten.

------------------------------------------------------------

In this case I just ticked the option on preferences and add any comp I'm working using "add comp to adobe media encoder queue..." , after the comp rendered, I sent it again to render trought AE's same menu

Let me know if you need more info 

[David Arbor]

Ah, I bet you were right about permissions and I think it's because of Dropbox. I can see how Dropbox might not allow this kind of behavior because of syncing. I'm willing to bet it will work if you overwrited a file that wasn't in Dropbox, though.

[ricar2]

Nops, you lost the bet unfortutatelly, I tried rendering with a aep on my desktop (redacted my folder name down there out of paranoia) and on my D:

The log:

Encode failed because the file C:\Users\***\Desktop\teste_AME\Comp 1.mov can't be overwritten.

- Source File: C:\Users\***\Desktop\teste_AME\tmpAEtoAMEProject-Comp 1_3.aep
- Output File: C:\Users\***\Desktop\teste_AME\Comp 1.mov
- Preset Used: Apple ProRes 4444 with alpha
- Video:
- Audio:
- Bitrate:
- Encoding Time: 00:00:00
08/31/2022 02:39:28 PM : Encoding Failed
------------------------------------------------------------

Encode failed because the file C:\Users\***\Desktop\teste_AME\Comp 1.mov can't be overwritten.

------------------------------------------------------------

Encode failed because the file D:\teste_AME\Comp 1.mov can't be overwritten.

- Source File: D:\teste_AME\tmpAEtoAMEProject-Comp 1_1.aep
- Output File: D:\teste_AME\Comp 1.mov
- Preset Used: Apple ProRes 4444 with alpha
- Video:
- Audio:
- Bitrate:
- Encoding Time: 00:00:00
08/31/2022 02:40:58 PM : Encoding Failed
------------------------------------------------------------

Encode failed because the file D:\teste_AME\Comp 1.mov can't be overwritten.

------------------------------------------------------------

[David Arbor]

Huh, indeed I did. What happens if you created a file with the same file name and extension in two different places and, ignoring AME, tried to overwrite one with the other? Permissions could still very likely be the issue here, especially given AME's error. AME isn't failing because the encoding had an issue, it's explicitly telling you the file can't be overwritten.

[ricar2]

Hi David, sorry to take so much time to reply, got a busy end of week.

Anyway, out of spite, I changed my entire D ownership to my specific user just to see if that is a windowns permission or something. Still the same error unfortunately. Also tried another drive with that permission thinghy (https://www.youtube.com/watch?v=6thv2JXFkKE&t=190s&ab_channel=SandeepSingh) and even did specifically on the damm file, still no change.

I'm out of ideas, hopefully you guys can thign of something.

Cheers

[David Arbor]

Sorry this is still happening, I don't have many more ideas. Have you tried uninstalling (while trashing preferences) and reinstalling Premiere and AME?

[ricar2]

I did, actually this is a issue that bothers me since AME launched. You mean that thats not a issue you have as well?

[David Arbor]

Correct. I recently enabled the checkbox and overwrite renders all the time with no issues.

[ricar2]

Tks for letting me know, I might be cursed haha. I'll keep messing over here and try to figure out what's up.

[David Arbor]

I recommend writing up post in the Bugs section of this forum with as much detail as possible (following this guide), including the troubleshooting steps you've provided. Getting this in front of the team might help them identify trends that could be causing the issue.

[LittleGreenDog]

Sorry, I know this is an old thread, but I can confirm this exact issue is happening in Media Encoder 2024. It will not overwrite an existing file. It either creates an incremental save when the option is enabled, or it fails when the option is disabled.

It's been very frustrating because I have to be sure to delete existing files every time I run the batch.

[eckiAMETeam]

I just tried to export a sequence using Export Mode in Premiere Pro. The panel will create a new name if the old one already exists. If you want to overwrite, delete the "_1" and hit "Replace" in the dialogue. AME will correctly replace the file. I tested this on macOS using AME 24.4.0.46. Note that this was done withe the increment option on. It replaced the target file as expected.

[Kris Hunt]

I just encountered this bug as well. Turning off the increment option results in the export failing. I'm on a Mac using Premiere Pro 24.5.0.

[Falk2000]

Same here, extremly annoying.