*offizielles deutsches flaskmpeg & dvdtoogm board* (http://www.flaskmpeg.info/index.php)
- *codecs* (http://www.flaskmpeg.info/board.php?boardid=9)
-- => Wissenswertes rund um x264 <= (http://www.flaskmpeg.info/thread.php?threadid=5138)
Zitat: |
VDM kann nur mit VCM codecs arbeiten, und das steht im Gegensatz zu native modes. native h.264 geht im augenblick mit mkvmerge nur von MP4, nicht von AVI. |
Zitat: |
Changelog: 0.1.1 nach 0.1.2: - Aufbau des Frontends hat sich geändert - weighted prediction ist wieder da |
Zitat: | |||||
Deblocking strength is controled by values called alpha & beta. These values are computed for each macroblock according to the quantizer of this macroblock, the quantizer of its neighbour, and the offset you set ( the famous value that range from -6 to +6 ). Here are the tables for alpha & beta, indexed by 'quantizer + offset' :
The higher these values, the stronger the deblocking. When one of these is null, there's no deblocking on the macroblock. As you can see, when 'quantizer + offset <= 15', both alpha and beta are null, so no deblocking is applied. Alpha is used to determine whether the frontier is blocky or if it's actually a detail. It works like a threshold. Beta also works as a threshold, but is used to insure that on both side of the frontier, the picture is homogenous enough ( once again, to separate detail from blockiness ). Once you've decided whether or not to filter the frontier, alpha is used to decide the strength ( in fact, the maximal allowed modification to a pixel ). beta can slightly modify this strength, is the macroblock is flat enough. So in the end, foxyshadis' description is a bit too simple. Both offsets decide which blocks, and the first one influences the bluriness the most. |
Zitat: |
Changelog: 0.1.4 nach 0.1.5: - Neue Features: trellis, rdo für b-frames, bidirektionale ME für B-Frames |
Forensoftware: Burning Board 2.3.6, entwickelt von WoltLab GmbH