Skip to main content
Liveshots
Inspiring
October 11, 2022
Question

Export via Media Encoder fails to write XMP

  • October 11, 2022
  • 2 replies
  • 6435 views

What the - is going on? For months, every time I have tried to batch render a bundle of live music videos, I keep getting this error;

- Source File: C:\Users\Del_7Pro\AppData\Local\Temp\Both Acts Multicam.prproj
- Output File: D:\Render Bucket\FreeFoundation_FHD#1.mp4
- Preset Used: Custom
- Video: 1920x1080 (1.0), 25 fps, Progressive, 100 (63% HLG, 51% PQ), Hardware Encoding, Nvidia Codec, 00:09:08:04
- Audio: AAC, 320 kbps, 48 kHz, Stereo
- Bitrate: VBR, 1 pass, Target 16.00 Mbps
- Encoding Time: 00:19:57
10/11/2022 10:48:40 PM : File Encoded with warning
------------------------------------------------------------
File importer detected an inconsistency in the file structure of FreeFoundation_FHD#1.mp4. Reading and writing this file's metadata (XMP) has been disabled.

File importer detected an inconsistency in the file structure of FreeFoundation_FHD#1.mp4. Reading and writing this file's metadata (XMP) has been disabled.

File importer detected an inconsistency in the file structure of FreeFoundation_FHD#1.mp4. Reading and writing this file's metadata (XMP) has been disabled.

File importer detected an inconsistency in the file structure of FreeFoundation_FHD#1.mp4. Reading and writing this file's metadata (XMP) has been disabled.

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

 

I have got my mp4 file which plays in Windows Media Player, but it leaves a '.m4v' on the side in the render folder - the same file size as the video.
Export direct from Premiere one-by-one suffers no problems, but it can't seem to communicate with AME any more. What's this XMP all about, is it essential? I thought XMP was to do with website building (Extended Media Protocol)

 

Mod note: Profanity removed. Please refrain from that. We have minors reading here.

This topic has been closed for replies.

2 replies

New Participant
January 23, 2023
Screenshot_2.png
Adobe Employee
June 22, 2023

You mentioned a pretty old custom preset. Does it also happen with system presets? Also what are the metadata settings? What happens when you disable metadata creation?

R Neil Haugen
Brainiac
October 11, 2022

First thing I noted was the # character in the filename. Do NOT use those type characters in the filenames ... can cause issues.

 

And may be the cause. Dump your cache files. Change the filename, and try again.

 

Neil

Everyone's mileage always varies ...
Liveshots
LiveshotsAuthor
Inspiring
October 11, 2022

Thanks for that input, but I've just exported #1 direct within Premiere. No errors or odd files, so I'd call that an AME bug.

Community Expert
October 12, 2022

the problem with reserved characters is that it's difficult to predict when they'll cause problems... So try removing the # and see if that makes a difference.