Media Encoder Error...

[Jedd - HOGG Animation]

I am creating an Animated Film for School and I tend to export my animations using the Media Encoder.

All of a sudden, any time I  try to go about exporting my animations an Error message tells me, "Adobe Media Encoder has encountered an unexpected error and cannot continue."

I work on PC and render at 1920x1080p/when last frame is reached.

I have tried exporting my animations without Media Encoder, though any animation with a lot of movement becomes fairly pixelated and unappealing looking.

Fellow animators will know the amount of time it takes to create detailed, dynamic animations, and this being a school project, I am very limited to the time I have left to complete my film, so I would REALLY appreciate any help!

[Colin Holgate]

Any chance you have uninstalled QuickTime? It's needed as a go between, Animate makes a SWF, then records that to an MOV. After you have the MOV you don't have to go through media encoder. For example, if it's to go to YouTube you can upload the MOV that you already have by then, without involving media encoder.

The MOV should play in perfect quality, but it is high data rate, and might skip frames.

[Animachristi]

This is very helpful! I had the same problem last month and never did figure out what was going wrong--this explains it. Thanks!

[Jedd - HOGG Animation]

I have double checked and have not uninstalled QuickTime.

It only started to happen today, all of a sudden with an animation I had just finished in Animate CC, it told me that it could not be encoded with the Encoder, then after restarting my computer and the programmes I am just given that error message any time I try to use it. Before you may think that the animation is maybe too large or something along those lines; that's not the case, as I even tried exporting animations I have previously successfully exporting using the Encoder and I am shown the same error message.

I was thinking of getting in contact with Adobe so I can speak to someone over the phone, as this is a very major problem for me - although thank you for your concern Colin and I'm glad this could assist you Animachristi!

[Colin Holgate]

Had another thought. I've heard of animations that failed to export as video because of the audio that was being used. Go into Publish Settings and set both audio types to Raw, 16 bit, 44.1 kHz, stereo. Ideally your library sounds would be 16 bit, 44.1 kHz too.

Is there anything unusual about your sounds?

[Jedd - HOGG Animation]

That's the thing.. the animations I am exporting have no audio as I am adding it in the process of editing!

[Colin Holgate]

Are you able to export video from a new FLA? If you can you could then set a lot of layers in your animation as Guide layers, and try again, until the export succeeds. Just as a way to find out which elements are causing the problem.

Just remembered another problem case, which was with JPEGs that have a CMYK profile, those can cause issues too.

Is the animation top secret? Could you post your FLA online for me to try?

[Jedd - HOGG Animation]

Oooh... that could be the issue then; the one about JPEGs, - though the animations I tried re-rendering don't contain JPEGs and I was still having the same issue.

No, not at all, how would I go about posting one online?

[Colin Holgate]

Do you have your own server, or access to DropBox or Google Drive? Anything like that. Make the FLA be a zip file to reduce the size a little, and upload the zip file somewhere.

If the zip isn't too big you could also click on my avatar icon, and then use the Message option to send the file to me.

[Jedd - HOGG Animation]

Ok I have compressed the FLA file to a zip.

went to message you on this though I didn't see the option for file attachment? Maybe you could message me your email address and I could send the file to you that way, as I do not have Google Drive or anything along those lines.

[Colin Holgate]

I sent you my email address.

[Colin Holgate · Accepted solution]

After some back and forth Jedd came to realize his Animate wasn't up to date, and an update solved the orginal problem.