Skip to main content
Friendly_brain0101
Participating Frequently
March 8, 2022
Answered

Blank Error when exporting video files

  • March 8, 2022
  • 2 replies
  • 2321 views

I'm working on an animation and I noticed when trying to export it (regardless of scene length, or even moving frames) I get a blank error upon the media encoder popping up. No exported file appears, just the blank error. I've tried resetting prefrences, running older versions of both the encoder and animate, but no luck.

 

I've tried to export in quicktime and that sort of worked (horribly choppy quality) and I would prefer to export it in a usable format.

 

I've exported stuff successfully years ago but this is a different computer, with different windows, and different versions of adobe programs.

 

Any help would be appriciated, Thanks!

This topic has been closed for replies.
Correct answer Mario_CR

No, no luck changing between either settings for preferences.

 

I'm pretty much convinced it's an AME issue at this point, since exporting with quicktime bypasses it and while the render is missing like 80% of the frames and is choppier than a stop motion rendition of tetris, it still exports it.

 

Trying other exporting settings just results in a blank error per usual.



I'm pretty much convinced it's an AME issue at this point, since exporting with quicktime bypasses it and while the render is missing like 80% of the frames and is choppier than a stop motion rendition of tetris, it still exports it.


 

The quicktime export is frame based so it doesn't actually drop any frames, it's just that, since it's a lossless format, is too heavy to be viewed on a video player in realtime. You can take that Quicktime MOV and transcode it to a compressed format like MP4 by dropping it onto AME which is a common workaround.

2 replies

n. tilcheff
Braniac
March 10, 2022

Export a PNG sequence and then assemble that into MP4 in Premiere:

https://community.adobe.com/t5/animate-discussions/export-issue-stops-mid-export/td-p/10424361

 

Nick - Character Designer and Animator, Flash user since 1998 | Member of the Flanimate Power Tools team - extensions for character animation
Friendly_brain0101
Participating Frequently
March 10, 2022

Thanks for the suggestion but to be completely honest it seems like an overly complex workaround and would take up more time then I'm willing to spend on exporting a single scene let alone 20+.

 

I could just transfer the files to my 2013 macbook and export them from that, but would rather avoid that for obvious reasons. I posted here to see if I can get this error resolved and in the process help anyone else that runs across the same issue in the future.

kglad
Braniac
March 8, 2022

untick start ame render queue immediately to see if you can get the source into ame without an error.

Friendly_brain0101
Participating Frequently
March 9, 2022

Just tried it, unfortunmatly the blank error still comes up.

Friendly_brain0101
Participating Frequently
March 10, 2022

not that i know of.

 

try resetting your preferences.

 

make something custom, if there's nothing custom now. (eg, a keyboard shortcut)

reset the preferences, https://helpx.adobe.com/animate/using/set-preferences.html

confirm your custom setting has been removed.

 

if that fails, uninstall animate including preferences, restart your computer and then reinstall.


So I tried to reset the preferenecs but the instructions on the page are so unclear (I dont' even see a button to reset to default (see attached image) and tried the Ctrl+Alt+Shift on launch but no luck. So I went ahead and reinstalled the app and made sure to NOT keep the preferences so it would be a fresh install (which greeted me with another error that sometimes pops up, but goes away after I close it like 12 times). Unfortuantly I still got the blank error when exporting (I've already tried a fresh install in the past, as well as using older versions of Animate and the Media Encoder with no luck). Can it be an issue with the Multimedia encoder? I'm honestly stumped. I hope I dont have to reinstall windows to fix this issue. Or even worse, reinstall it and still get the same error.