cc 2018 won't render .mov H.264

[donbarrum]

CC 2018 and Media Encoder both refuse to render .mov H.264 files, even if quicktime is installed and can be selected. THe render just crash every single time. I hope this will be fixed Quickly!

[Mylenium]

Without any actual info about your system, your project, exact settings etc. this is not going anywhere. Sorry, but your post is mostly useless.

Mylenium

[donbarrum]

Well, Ill try my best then and hopefully Adobe will as well...

Project is a reguar After Effects project made in After Effects CC 2017. No plugin used, only still images moved, so no imported video. After installing all the CC 2018 softwares I cannot render H.264 wrapped in .mov anymore. I have the option to do so but a get a compressor crash emidiately after I hit render.
Same happens if I send it to Adobe Media Encoder as well, but without any warning or error.

My Hardware is Windows 10, cpu 16 core threadripper, 128 gb ram, 3tb SSD and 15gb HDD., GTX 1080Ti gpu.

Dunno what else I can give of information ?

[Dave_LaRonde]

donbarrum  wrote

...I cannot render H.264 wrapped in .mov anymore.

You may not like reading this, but that's no great loss.  Quicktime's implementation of the H.264 codec was always lousy.  Really stunk the place up.  If you want to keep H.264, Use Adobe Media Encoder to make an mp4/h.264.

[donbarrum]

Maybe so, but a lot of clients I have wants the .mov H.264. Also, Adobe Media Encoder stunk my place up, a lot of the time it just stays on "connecting to Dynamiclink server" and never seems to render.

[Dave_LaRonde]

Hmmm... I forgot about those pesky clients.

Do you have QT Pro?  Render out your stuff in a good, intermediate QT codec, open it in QT, and export the h.264.  Yeah, it's a pain to to add another step, but you should be good to go.  It can't be any worse than AME giving up on you.

[donbarrum]

thanks yeah I guess that can work...for a short while, but it definatately isnst a long time solution. Actually the whole AME problem is even more worrysome. I dont seem to be able to render anything from AE 2018 to AME, time to revert I guess

[Dave_LaRonde]

Yeah, I would never, EVER touch an initial Adobe release -- just too many bugs!

There have been a couple of posts from Adobe guys saying in essence, "Um, folks, we found another bug.  Here's a link to the patch."  In just two day, mind you.

Which would you rather do -- waste your time patching buggy software, or keep working in the current version until there's an announcement of a big bug fix?

But Caveat Downloader! Big bug fixes may not solve YOUR particular AE problems.  But feel free to roll the dice.

[donbarrum]

Yeah, sadly though, it is announced as a finished product. But currently it doesnt really feel like it. I'll keep that in mind for the future, thanks!

[P.M.B]

donbarrum  wrote

Yeah, sadly though, it is announced as a finished product

You must be new.

[donbarrum]

nope, just always hopeful

[P.M.B]

Ohh.   Well then you should know that Adobe has been releasing unfinished buggy software for a long time.

Fool me once, shame on you.

Fool me twice, shame on me. 

[donbarrum]

Yeah I know, and very often they never even fix it, so you have to find ways around it anyway

[radarcanon]

I am having the same problem on MAC OS 10.12.6 black trashcan with Adobe Bridge CC 2018.  Displays fine in Adobe Bridge CC 2017.

[RH_BO]

I am having an issue as well. After editing in Premiere ( A ProRes file), I sent it to Media Encoder to ouptut an h.264, but in the M.E. preview, all I see the the media missing screen, even though it shows fine in Premiere. I am stuck.

I am on a Mac Pro, High Sierra OS and of course latest 2018 Adobe. (dumb move I guess)

I'm going to try to render out as ProRes and see what happens...

[RH_BO]

Mine is fixed (sorry I was using premiere - wrong forum - apologies!). I talked with a rep on the phone and he remoted into my system and wiped my media encoder preferences in the library folder. That seemed to fix it once I re-opened the app.

If you guys go this route, be sure you backup any of your custom presets first.

[Rick Gerard]

Render an MP4 using H.264 not h.264 in a MOV container. Apple does not and never did really support h.264 in a QuickTime container and they never did.

[sethe65874835]

it's still not working .

[alexandrer49502434]

Você tem que mandar renderizar o arquivo Mov no disco de sistema. Só assim que funciona.

Se você mandar renderizar o Mov em que qualquer outro disco que não seja o do sistema, não funciona, dá "erro".

Descobri, depois que mandei renderizar no disco de sistema na pasta de Documentos ou de Vídeo. Funcionou perfeito !!!

Espero que tenho ajudado.

Alex

Belo Horizonte/Brazil

[robinj28565293]

This aint working for me either anymore, and I have the same 6-core Xeon I had the last 2 years.

[elenaf68552420]

Can't Import MOV to After Effects? See Solutions Here.

[donbarrum · Accepted solution]

About my initial problem, It has come to my knowledge that Quicktime for Windows has a limitation of not being able to render on any CPU with 16 cores or more. I recently upgraded my CPU to AMD THreadripper 1950x (16 core) and apparently haven't rendered any quicktime h.264 since then - so I didn't know until recently.

Of course this is a disappointing move from Apple, but since Quicktime for windows will never be updated ever again, it's safe to assume this limitation will never be fixed. Time to find other codeks and workarounds I assume.

[ICONOFX]

Try putting Ryzen in gaming mode.

[donbarrum]

Thanks yeah that works. THough it cripples my Threadripper to only using half the cores. But, for rendering .mov its good.

Sadly though, after effects performs A LOT slower with my new threadripper than it does with my other machine where I have an 4.4 GhZ 6 core CPU. But that's another discussion I guess, just proves that Adobes shift to a better performing After Effects is far from here

[Randombell]

I remember having a similar problem last summer where Premiere would not let me export an .h264 in a .mov extension. I'm an editor for a video production company and had a client that requested these settings for their final output (the video was going to play on TV).

After some research, I found the reason why this is happening is because there's an issue with Quicktime exporting with the .h264 codec on Windows machines with more than 16 processing cores. Turns out there's a temporary fix you can do to your machine (basically temporarily disabling a few of your cores long enough to let Adobe render it's files out).

Here's the link to the article:

“Error compiling movie” warning or hang in Premiere Pro

It's a real easy temp fix, only takes changing a setting in MSCONFIG and restarting your machine. Render your stuff off, change the setting back and restart. Back to normal. There's no noticeable affect on your machine after disabling the cores and no repercussions.

Hope this helps!