x264 encode messed up

[SameSelf]

Aargh! I wish I had the money for a decent authoring tool like dostudio or scenarist and I could ditch this sorry excuse of an authoring tool.

It was a while ago and I can't remember what the problem was. But my workflows admittedly were a mess then. I will run some tests tonight to see if I get the same problems again.

[jagabo]

Just use720p and double the frame rate with ChangeFPS(). The exact duplicate frames will take hardly any additional bitrate compared to --pulldown double. Though x264 is frame rate aware and will use slightly higher average quantizers for the double frame rate video. You can make up for that by selecting a CRF value ~0.5 below your usual.

[SameSelf]

Well, I did a small test last night and sure enough Encore was able to handle the 1080 --fake interlace. But, Encore is super slow with it. I know I would experience serious problems with longer timelines. That is ok though. I have no qualms with encoding my 1080p content as 720p. I don't harbor any fantasies that my video has 1080 lines of resolution. Sometimes, ease of the workflow trumps everything else.

jagabo, thank you, that sounds like a good strategy. I naively assumed that --pulldown double did the same thing. My video encodes with ~85% 3 consecutive b-frames (the optimal number when I encode for the web is around 6 or 7), so duplicate frames as you said should not significantly increase the bit rate.