Inspiring

Answered

cc 2018 won't render .mov H.264

Forum|Forum|8 years ago
October 19, 2017
7 replies
39851 views

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!

Import and export

This topic has been closed for replies.

Correct answer donbarrum

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.

B

briant80972747

Participant

I realize this thread is two years old, but for the sake of others who stumble across this same problem: If you have access to a Mac, use Final Cut Pro X or the Compressor app to export a .mov file with H.264 codec. In the Compressor app, use the "Up to 4K" preset in the "Publish to YouTube" folder. Not only can you export a mov. file with an H.264 codec, you can also choose PCM audio.

elianac57697270

Participant

Hola buen día! Tenía el mismo problema para exportar en H264 en after effects, lo que hice fue lo siguiente:

- Exportar el video en formato Quicktime

- Abrir el archivo en Adobe Premiere

- Exportarlo en formato H264.

Quizás no sea lo mejor, pero me sirvió, ya que adobe Premiere CC 2018 si permite exportar en ese formato. Saludos!

C

CHIAGAMER REVIEWS

Participating Frequently

HOLA,

Yo estoy intentando exportar un vídeo con H264 por temas de aceleración por hardware para aprovechar la GPU del procesador y así poder hacer otras cosas mientras hago el render pero solo exporta el audio solo el vídeo, sabrías por qué????

Randombell

Participant

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!

R

Rick Gerard

Community Expert

It is still important to know and work around the insolvable problem that can be created with you try and widely distribute MOV files encoded with H.264 compression. This is not supported by Apple, not being worked on, no plans exist to improve anything and to reason to expect that any solution is anything but a 3rd party hack to fix the problem.

The fact is that nobody should be delivering h.264 encoded MOV files to anyone. If you want to use h.264 compression, the most universally accepted MPEG compression for anything, it needs to be in an MP4 container. Anyone with a machine that was made in the last decade can playback the file on any device that will playback video. Broadcasters and streaming services rely on H.264.mp4's for their delivery and until a new standard is adopted it is the gold standard for public consumption. Unless you are trying to match a specific specification, you should stick with mp4.

If you have a client that has issued you a spec calling for an H.264 Quicktime then it is your job to talk to them about it and educate them. Without specific language in a contract for services that absolves you of responsibility for incompatibility due to known and disclosed problems with the format, you may be liable for damages that could run into very big money. I do not know exactly how many jobs I have turned down over the years because clients wanted me to deliver product to them that would not meet my delivery standards but it has been about one a year since 1969 and some years it was a lot more.

donbarrumAuthor

Inspiring

Yes, I agree we should all avoid using .mov as much as possible. the fact that Applewill never update quicktime for windows and has never supported even encoding of ProRes for Windows should not force the users to buy Macs, but make .mov obsolete. That would be the best scenario.

Though, some of my clients still wants .mov. Particularly some that uses Qlab and Catalyst on Mac (old and bad programs I know) for show/entertainment screen AV. I have tried giving them .mp4 with H.264, but they claim it stutters and perform worse.
For almost any other client, I deliver mp4.

Currently I have shut down my CPU to 12 cores every time I render H.264 through a .mov container. Its not an ideal situation, and I know it will never be fixed from Apples side and its annoying having to reboot to render the videoes and than revert the CPU back to 16 cores.
I will try the plugin called AfterCodecs for After Effects, they apparently seem to be able to export Prores, .mov of any kind and even mp4 with faster and better encoding than the native ones. So, maybe their plugin can export .mov on 16 cores as well.

But in an ideal world, as you say, any Apple codec should be replaced with something that is supported properly.

On a side note, I find it ironic how Apple a few years back under Steve Jobs, wrote a full page on how he hated Adobe Flash and was going to do everything in his power to kill it by never let it run on iOS. Simply because the lack of dedication and support from Adobe -and something that so many people use shouldn't be developed under one ownership. While at the same time Apple do the exact same thing with ProRes and Quicktime.

donbarrumAuthorCorrect answer

Inspiring

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.

I

ICONOFX

Participant

Try putting Ryzen in gaming mode.

donbarrumAuthor

Inspiring

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

elenaf68552420

Participant

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

R

RH_BO

Participant

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...

R

RH_BO

Participant

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.

R

Rick Gerard

Community Expert

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.

Mylenium

Legend

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

donbarrumAuthor

Inspiring

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 ?

donbarrumAuthor

Inspiring

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.

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!

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded