The following lines were added (+) and removed (-):
<big><big>Fails on Two Pass: The 2-pass encoding error remains unresolved</big></big>Currently, on "Initializing the compression" during the second pass, "_TranscodeProcess() : The DVD could not be converted." It seems that FairUse is passing something invalid to the internal 264 codec. This is an unresolved issue. This is likely a glitch in the FairUse software. Up the file size and use one pass or use alternative software if you are set on using two pass encoding. * DVDfab -* DVDFab Platinum 8.1.7.8* FairUse Wizard -* FairUse Wizard 2.11b== Create H.264 Single File Output ==# Open DVDfab# Screen 1## Choose DVD Copy, Main Movie (as opposed to full disk)## Source: the DVD drive## Target: the path where you want the output files saved. IMPORTANT: You must click the icon with a paper and blue circle on it that is to the right of the folder icon. This is the '''CREATE ISO IMAGE''' icon. Now choose a path and name for the ISO.## Choose the movie track to rip, typically the longest. Chose the audio channel, (deselect one of there are more than one selected) Some audio tracks may contain unnecessary crap like director commentary. Best guess, try the first track first.## Subpicture: rip subtitles as they will be needed later even if you don't care about subtitles, some movies have [Forced Subtitles] and therefore all must be obtained from the DVD.# Screen 2## mostly defaults here. copying make sure DVD-Video is checked. Give it a volume label. DVD5 is typical.## click START == Create H.264 Single File Output With FairUse Wizard == # Open FairUse Wizard# Screen 1## Create a new project. Type in a project name. ## click next# Select DVD Drive popup dialog, click BROWSE and navigate to the ISO image. Select the ISO image and click OK.# Screen 2## mostly defaults. Cache the selected program chains (multisession) should already be selected. ## click next# Screen 3## wait while FairUse Wizard does "Building program chain index..." This takes around 2-5 minutes.# Screen 4## There's a lot to do on this screen. First, use the slider below the video preview to find a good video frame which is nice and bright, making the dimensions of the screen area fully apparent. ## In the Cropping Region area click the Auto Set button. wait for it to calculate. Now make minor adjustments so that the crop area doesn't exclude any of the video. ## Frame Range - you can leave this or you can choose to cut out any studio stuff in the beginning. Some people cut out the credits at the end. If you do cut credits, do it after the main characters are named.## Check Include Subpictures, Show forced subtitles only, and extract subtitles ## click next# Screen 5## For field combination simply click Auto Detect. It will almost always choose IVTC mode. Whatever it auto detects is what you want to use.## click next# Screen 6## For video encodings choose x264## Choose the Size radio button and check <del>Two pass</del> (''only one pass or constant quantizer seems to work in this version. two pass crashes'').## The base file size default is 700mb. A huge file is not necessary with [[H.264]]. If you are looking to produce a 2gb out file or larger, then XviD will work just as well as H.264. Where H.264 shines is with higher compression. It is recommend you target a file size between 600mb - 900mb depending on the size of the movie. 700mb is good for a 120 minute movie. But there is more on how we recommend you select what file size to use, below in the fine tune file size...## Now to fine tune the file size, --- Use the up arrow clicker to increase the file size one MB at a time. While you change the file size observe how it effects the Resolution settings below, specifically, the Output Video Size and Bits/Pixel. It is recommended that you increase the MB until the Output Video Size = 640x288 and the Bits/Pixel = 0.200. You can adjust the MB up and down until you hit this key target.## Encoding Speed - always choose Quality over speed. Slider should be all the way to the right.## Audio is MP3 128kbps## defaults for the rest. (Files 1 unchecked)## click next (''it may seem like nothing happened when you click next, just wait a bit'') The process of encoding will begin after the delay. == Constant Quantizer versus 2-Pass == When dealing with H.264 video, 2 pass is recommended when targeting an output size. It is also believed to produce a superior quality output stream. Some argue the output is nominally better or the same. The [http://www.mplayerhq.hu/DOCS/HTML/en/menc-feat-dvd-mpeg4.html MEncoder documentation] saysThe problem with constant quantizing is that it uses the given quantizer whether the macroblock needs it or not. That is, it might be possible to use a higher quantizer on a macroblock without sacrificing visual quality. Why waste the bits on an unnecessarily low quantizer? Your CPU has as many cycles as there is time, but there is only so many bits on your hard disk. akupenguin, the x264 author:"CRF and 2pass are at the same point on the CBR-to-CPSNR continuum, because they have the same target bitrate distribution. 2pass just ends up slightly closer to that target.)" "benchmarking the existing implementations of crf vs 2pass on several movies. Result: 2pass was better by anywhere from .01 to .12 dB (equivalently, up to 2.5% bitrate at the same psnr). This includes both the effects of ratecontrol (smarter I-frame qp decision) and the fact that direct=auto only really works in 2pass." "x264 keeps track of the "complexity" of each frame, and then determines quantizer from that using the ratecontrol equation (rc_eq) and a quantity called "rate_factor". Assuming an ideal rc_eq, then constant rate_factor would be optimal perceptual RD (not constant quality, but allocating a little more quality in places where it doesn't cost much).ABR and 2pass use the same rc_eq, the primary difference is in how they determine rate_factor. In ABR, we only have statistics about the past frames, so we continually update the estimate of the rate_factor needed to meet the target bitrate. In 2pass, we have all the stats, so we pick the right rate_factor to begin with.To make a 1pass encode that is nearly identical to a 2pass, you'd need to specify rate_factor instead of bitrate or QP. (There will still be some differences: 1pass uses SATD for complexity, 2pass uses 1st pass's bitsize; I-frame quants are selected differently.)" For a full discussion, see [http://forum.doom9.org/archive/index.php/t-151938.html xvid: constant quantizer or 2 pass?] on doom9, where xvid and h.264 are both discussed. Recommendation: For H.264 it is recommended that you use 2-pass as described in the encoding process of this guide.{{:FairUse Wizard Troubleshooting}}