So its probably that we’ve installed third party codecs in AME to allow this ( I know we’ve added cineon and BMD so an additional H264 isn’t out of the question). It would answer the question as to why we don’t see the problem that others are seeing (our colleagues as well) when trying to do larger or multipass H264s or 265s through AME.
As I’ve mentioned in other posts on this topic (which seems to be at an epidemic level these days), we tend choose either QT Pro itself or FFMPG long before we’ll fire up AME to do a 264 crunch. But that’s purely for ease of use and speed of compress. With the exception of dedicated hardware boards nothing we’ve found beats FFmpg for speed.
But still my advice remains – do the compress AFTER you have output a clean file from AE. I really don’t understand the desire to do it in one pass. It takes longer, plus you don’t get to see the AE output before you compress (it could have issues) and you can’t tweak the compress on the clean master file after the fact because AE is doing it for you. If the initial compression values aren’t good enough you can always crunch it again, which always takes less time than running even just the clean master file out of AE again, let alone re-rendering AND compressing.
Does this make large (even huge) clean master files coming out of AE? You bet, but drives are dirt cheap these days and even a boring vanilla size is now 750gb+. Animation Best is a great QT format to render your clean master in. While technically compressed, it is compressed with run-length encoding, so nothing is lost. A noisy movie will be a similar size (in mb) to a truly uncompressed file, but anything with solids or where elements don’t change that much will be massively smaller. Minute long alpha channels rendered in Animation Best can be less than 500k and will be just as perfect as an equivalent uncompressed monster at over 14 gb.