Well, as stated, the reason for using H264 is size. We are sharing proxies, and everything else about the project other than full footage, via cloud storage. In order to use ProRes 422 Proxy and get it anywhere near the same size, since the only way to control bitrate with that format is to adjust the size, is to cut the scale by 40%. Since I was already cutting the scale down to 1364x720 (for 17:9 size), that brings me down to roughly 720x380 to be comparable in size. But it doesn't look comparable till it's the same size, but the proxy format is nearly double (183%) in filesize. At this size, btw, I'm using a bitrate of approximately 10Mbps and using 10bit for H.264. Proxy is either 8bit or 16bit. I also wasn't aware of the Premiere Proxy workflow requiring parameters to match. That's a Huge pain in the butt, because if your footage has an odd audio format, or No audio, then unless you make your own proxy format for that footage, it won't work. The funny thing is though, it does work....Once. Premiere will send the footage over to AME, render it, and bring it back as the proxy file. But if the path changes, it won't let you choose it as a proxy file. I'm primarily working out of Premiere at the moment, but quickly figured out, if you have more than a few pieces of footage to make proxies for, Premiere is the place to do it. AE is Much slower, and you have to do one at a time. In Premiere I can select 100 files at once and send to make proxies. Then you just copy the footage and paste it into the AE bin and it comes over with the proxies defined. Of course, a few things break if you go back and forth, like Lumetri color Luts paths don't work so you have to repath them all. Thanks for letting me know that AE has a way to just cut the resolution sizes by fractions. It's just too bad that AME doesn't have that because AE is MUCH slower at rendering. I'm not sure the differences in how they render, but its a shame I can't just check a box and tell AE to make whatever sacrifices premiere is making to render more quickly for previews. Something like a title block should render in real-time or faster for previews, but every time a title block, or other AE file comes up, things just Drag. Are there some good points as why ProRes 422 Proxy is so much better than H.264? The things I've seen is, better color, and less CPU intensive. But since I'm shoving the resolution down to something close to 720x1280, it seems like even if CPU usage doubled, going from 5% to 10% of a single thread CPU usage would hardly be a concern, right?
... View more