Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Media Encoder H.264 always fails

  • H.264 always fails

    Posted by Kris Sheehan on September 16, 2015 at 2:22 pm

    I am trying to export a project from Adobe Premier as a h.264 file. Every single time, no matter the project, I get the same thing. It completes with warnings and the file size is only 1kb. I have no issue exporting as any other file type.

    This is the same thing in the log that I get everytime:

    09/16/2015 08:58:37 AM : Queue Started

    – Source File: C:\Users\aeksa\AppData\Local\Temp\2016 LVPF Intro Video_9.prproj
    – Output File: S:\Million Dollar Vegas Producer Forum\2016\Videos\00013_1.mp4
    – Preset Used: Custom
    – Video: 1920×1080 (1.0), 29.97 fps, Progressive, 00:01:55:21
    – Audio: AAC, 320 kbps, 48 kHz, Stereo
    – Bitrate: VBR, 1 pass, Target 10.00 Mbps, Max 12.00 Mbps
    – Encoding Time: 00:04:48
    09/16/2015 09:03:32 AM : File Encoded with warning
    ————————————————————
    File importer detected an inconsistency in the file structure of 00013_1.mp4. Reading and writing this file’s metadata (XMP) has been disabled.

    Adobe Media Encoder
    Could not write XMP data in output file.

    Does anyone have any ideas? I’m at a total loss.

    Kris Sheehan replied 10 years, 5 months ago 3 Members · 5 Replies
  • 5 Replies
  • Michael Tamony

    October 19, 2015 at 7:55 pm

    Any solution to this? All of a sudden I am getting this error in CC.

  • Kris Sheehan

    October 19, 2015 at 10:10 pm

    I haven’t found a solution. I’ve reinstalled the software and updated to cc2015 and still have the same issue. I’ve also tried it on a second machine and run into the same problem.

  • Michael Tamony

    October 19, 2015 at 10:43 pm

    I actually solved it by saving to my desktop instead of an external drive.

  • Sam Lanes

    November 26, 2015 at 12:14 pm

    All of our team are having the same issue at the moment, which is something we never used to encounter.

    We are exporting to a network drive, and are currently resolving this by exporting to the desktop. However, this isn’t a viable long-term solution, as we often export multiple files, which then need to be moved into the shared storage.

    I think there is some kind of issue writing metadata or some such onto the files. It is very frustrating as it only fails in the final, final stage of encoding.

  • Kris Sheehan

    November 30, 2015 at 2:04 pm

    Yeah, my solution has been to save to the desktop and then move to the network. This is not a long-term solution but it is getting me by for now.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy