Changes between Version 25 and Version 26 of Encode/H.264


Ignore:
Timestamp:
Sep 25, 2012, 6:43:20 PM (7 years ago)
Author:
rogerdpack
Comment:

add QT Player note

Legend:

Unmodified
Added
Removed
Modified
  • Encode/H.264

    v25 v26  
    138138
    139139=== Will two-pass provide a better quality than CRF? ===
    140 [http://doom10.org/index.php?PHPSESSID=okj08qe73ictdtv532augv8nu7&topic=267.msg2071#msg2071 No], though it does allow you to target a file size accurately.
     140[http://doom10.org/index.php?PHPSESSID=okj08qe73ictdtv532augv8nu7&topic=267.msg2071#msg2071 No], though it does allow you to target a file size more accurately.
    141141
    142142=== Why is `placebo` a waste of time? ===
     
    151151
    152152No. libx264 doesn't use them (at least not yet). There are some proprietary encoders that utilize the GPU, but that does not mean they are well optimized, though encoding time may be faster; and they might be [http://phoronix.com/forums/showthread.php?50697-Test-tool-for-snb-h264-encoder-in-libva-git&p=205580#post205580 worse than x264] anyway, and possibly slower. Regardless, FFmpeg today doesn't support any means of gpu encoding, outside of libx264.
     153
     154=== Encoding for QuickTime Player ===
     155
     156You may need to use -pix_fmt yuv420p for it to work in newer versions of QT Player. Oddly.