As of about 2-3 weeks ago, I have not been able to convert a .mov (animation 100% quality) of over 2GB file size in Media Encoder to H.264, not even by bringing the video in to Premiere and exporting it from there in H.264 format. The video stops at around the 2GB mark and renders a still image of that frame for the rest. Does anyone know if this is related to the end of Quicktime support or something else? Never had this problem before, it just recently appeared. Same issue in both AME CC2017 and CC2018, Windows.
Which leads to the question: Is DNXHD my next best option for high-quality (near lossless) intermediate output for Full HD with audio?
Thanks Tero, I'll look into using those instead. I am quite in the dark about what the issue about "Quicktime support ending" means in practice. I thought Quicktime is a container format, not an encoding format, so what's that got to with the price of fish? For example GoPro Cineform options are under Quicktime presets, so I would expect it to still export a .mov file, right? I guess I'll have to do some testing with a variety of file formats to see if that is even the issue.
[Kalleheikki Kannisto]"I am quite in the dark about what the issue about "Quicktime support ending" means in practice"
Apple stopped developing Quicktime so instead of keeping on using the 32-bit not-secure legacy stuff developers have made their own Quicktime decoders/encoders. This means dropping support for some of the older codecs.
Hi Dave, the problem is with AME not reading a .mov file of over 2GB but stopping and rendering a still frame for the rest. This is happening with a .mov file encoded as Animation, 100% quality. Been doing that happily for ten years, now in the last two or three weeks it has suddenly ceased to work on both AME CC 2018 and 17. I'm working with other encodings for the time being. At least DNxHR and Cineform as suggested by Tero still work fine.
The drive is NTFS formatted. It seems to only affect Quicktime with Animation codec (that I've noticed so far). Other codecs are working fine with over 2GB file sizes. This also happens on exporting a file from Premiere (both CC18 and CC17) to that format. Haven't done any extensive testing to determine if it is a consistent problem, it seemed more sensible to switch formats than to get stuck on it. Just wondered if anyone else had run into the same issue recently.