Selur's Little Message Board

Full Version: Hybrid frame interpolation works only for 2pass encoding
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
  • What Hybrid version did you use?(Windows/Mac/Linux 32/64bit + versions number):
    "Windows" Hybrid rev 2019.03.14.1
  • What did happen? If an error message came up what did it exactly say?
    No error appears on the screen. After encoding on 1st pass encode (if you selected average bitrate 1pass) it will stop and deleting .stats and .stats.mbtree will just be waiting and waiting.
  • What did you do to get to the bug? (best thing is a detailed step-by-step guide so that I can reproduce the problem)
    Selected the 1pass encoding option on x264 for quicker encoding.
Please, read the 'Infos needed to fix&reproduce bugs,..'-sticky before you post about a problem.
send you a link to my current dev version via PM, in case that doesn't help, create a debug output level 9 of the job processing and share that with me.

Quote:Selected the 1pass encoding option on x264 for quicker encoding.
which do you mean?
Quote:Encoding modes:

constant quantization (1pass) is a one pass encoding process which encodes each frame at a specific constant quantizer. Using constant quantization is mainly ment for fast encodings or testing specific features or then used with lossless encoding.
Side note: disables adaptive quantisation, since the quantizer would otherwise still be modified and though not constant (command line match: --cq X)

constant ratefactor (1pass) aka. (average quantization), compared to constant quantization, varies the quantizer on a block-by-block and scene-by-scene basis, so it is a 1pass encoding mode which working similiar to 2pass encoding, tying to keep a constant quality, but unlike 2pass encoding it does not care about the filesize, so it's mainly ment for people who know the want a specific quanity level but do not care about the filesize. (command line match: --crf X)

specific filesize/bitrate (2pass) is a two pass encoding mode ment to for people who aim for a specific filesize/bitrate and still want the best quality. (command line match: --pass 1 --bitrate X; --pass 2 --bitrate X)

specific filesize/bitrate (1st pass) and specific filesize/bitrate (2nd pass) are just the two passes from specific filesize/bitrate (2pass) separated.
-> Don't use them separately unless you know what you are doing! <-
The 1st pass always needs to be run befor the 2nd pass and the 2nd pass needs to know the .stats file of the 1st pass. The first pass is ment to collect some analysis data of the file and the 2nd pass does the encoding with the help of the data collected in the 1st pass. (command line match: --pass 1 --bitrate X)

average bitrate (1pass) is a one pass encoding mode for people who just want to get an average bitrate as fast as possible. Unlike 2pass encoding the average bitrate mode tends to fluctuate more qualitywise. (command line match: --bitrate X)
Side note:
If you want to stream you encoded material make sure to adjust the vbv-settings accordingly. (command line match: --bitrate X)
using specific filesize/bitrate (1st pass) without filesize/bitrate (2nd pass) doesn't make sense,..

Cu Selur