[samtroy]

OK, thanks for your replay.

Correct me if I'm wrong, but from what I've read is x264's 'faster' preset placed between 'fast' and 'veryfast' and not between 'medium' and 'fast'.

From x264 wiki:
---------
ultrafast: subme 0, ref 1, me dia, b-adapt 0, partitions none, trellis 0, bframes 0, weightp 0, no-mixed-refs, no-mbtree, no-scenecut, no-deblock, no-cabac, no-8×8dct, aq-mode 0

veryfast: subme 1, ref 1, me dia, partitions i8×8,i4×4, trellis 0, weightp 0, no-mixed-refs, no-mbtree

faster: subme 4, ref 2, weightp 1, no-mixed-refs, no-mbtree

fast: subme 6, ref 2, rc-lookahead 30

medium: No changes -> BD Rebuilder's default High Quality

slow: subme 8, ref 5, me umh, b-adapt 2, direct auto, rc-lookahead 50

slower: subme 9, ref 8, me umh, b-adapt 2, direct auto, rc-lookahead 60, partitions all, trellis 2

veryslow: subme 10, ref 16, me umh, b-adapt 2, direct auto, rc-lookahead 60, partitions all, trellis 2, bframes 8, merange 24

placebo: subme 10, ref 16, me tesa, b-adapt 2, direct auto, rc-lookahead 60, partitions all, trellis 2, bframes 16, no-fast-pskip, slow-firstpass
---------

And since the encoding time difference between x264's 'fast' and 'veryfast' is up to 5 hours on my Core i5 system I thought 'faster' *may be* be a good compromise..

Cheers, S.