FairUse Frequently Asked Questions with Answers

This is the list of Frequently Asked Questions for the FairUse Wizard - The
quality solution for converting your DVD-Video material into DivX AVI form.

-----------------------------------------------------------------------------

Table of Contents

1. Introduction and General Information
    1.1. What Is FairUse?
    1.2. What Version Of FairUse Is This FAQ For?
    1.3. What Are FairUse's Main Features?
    1.4. What Features Are Still To Be Implemented?
    1.5. Why Was FairUse Written?
    1.6. So What's Up With That Name?
    1.7. Isn't This Illegal?
   
2. Answers to Common Problems and Questions
    2.1.  How Do I Install FairUse?
    2.2.  What Version Of DivX Should I Install To Use FairUse?
    2.3.  Can I Use VOBs On My HDD I Made With Program X?
    2.4.  Can I Use Those ".RAW" Files As VOBs With Program X?
    2.5.  "Building Program Chain Index" Takes A Long Time.
    2.6.  How Much Drive Space Do I Need?
    2.7.  How Long Does The Encoding Take?
    2.8.  What Does This Button Do?
    2.9.  How Do I Determine The Best Data Rates For Encodings?
    2.10. Why Isn't My Favourite Resolution Listed? 
    2.11. But Really, My Video Should Be Exactly 1.85:1 (or 2.35:1).
    2.12. What Does It Mean "Preferred" Resolutions?
    2.13. How Do I Select The Best Resolution/Compression Ratio?
    2.14. What Does This "Diff Threshold" Mean?
    2.15. My Final AVI Looks Like Crap!
    2.16. My Final AVI Still Looks Like Crap!
    2.17. Can I Make A Cross-Cut Manually?
    2.18. Multi-Angle Scenes Are Repeatedly Inserted.
    2.19. What's This Indexing Process?

3. Technical Information
    3.1. How Does The Descrambling Work?
    3.2. Can FairUse Handle DVDs With Authoring Errors?
    3.3. How Does The Decoder Work?
    3.4. How Does The IVTC Functionality Work?
    3.5. How Does The VKI Functionality Work?
    3.6. How Is The Quality Of Images Calculated?
    3.7. How Does The Cross-Cutter Work?
    3.8. What Kind Of Audio Encoding Will Be Included?
    3.9. What Changes Were Made To The DivX Codecs Included With FairUse?

4. How to Get Further Assistance
    4.1. You Still Haven't Answered My Question!
    4.2. What to Put in a Request for Help.

5. Release History

6. Acknowledgments and Administrivia
    6.1. Feedback Is Invited.

-----------------------------------------------------------------------------

1. Introduction and General Information

1.1. What Is FairUse?

The FairUse Wizard is a tool for converting your DVD-Video material into a
DivX AVI form.

-----------------------------------------------------------------------------

1.2. What Version Of FairUse Is This FAQ For?

This FAQ is current up to version 0.30 beta. If you are experiencing problems
try updating to this version. Note: The project and chain file formats
changed between 0.26 beta and 0.30 beta. Any sessions from 0.26 beta or
earlier should be finished before upgrading.

-----------------------------------------------------------------------------

1.3. What Are FairUse's Main Features?

All-In-One solution - Converts straight from DVD, the only other software
you need is a working ASPI layer (but see yet to be implemented features
below).

Fully integrated MM4 support - Video is encoded at up to 30 different
bitrates/codec types simultaneously, for later "cross cutting" into the
final output file.

Best quality for a fixed size - You specify the size (disk space) of the
output file, and the best quality file that will fit that space is produced.

Maximally flat quality level - The new (in version 0.30 beta) encoding mode:
"diff tracking" adjusts the DivX quantisation levels on a frame by frame
basis to make the quality level as even as possible.

Variable keyframe interval - You can configure the minimum and maximum
keyframe intervals. This avoids the "sharpening effect" by not inserting
keyframes on static scenes.

Codec errors fixed - The DivX codec will no longer produce freeze frames/
grey blocks/mirrored blocks, etc.

SMP support - During the encoding phase, multiple processors will be used.
(The actual utilisation depends on the number of encodings being created.)

Field combination modes - Fields can be realigned (PAL), IVTCed (NTSC) or
simply decoded natively as directed by the DVD.

Support - FairUse supports seamless branching and multiangle titles.

Audio demuxing - AC3 audio tracks can be demuxed and are synchronised to
the video range selected.

-----------------------------------------------------------------------------

1.4. What Features Are Still To Be Implemented?

Full audio processing - Currently, AC3 audio tracks are listed, demuxed
and written to disk, but they are not decoded, nor interleaved in the
final AVI file. You specify the audio bitrate and space is left so that
there is enough room to mux in the audio later. For now you will have to
decode/interleave the audio using other tools.

Multi-part output - There is currently no support for splitting the
output file into (say) 650MB pieces, so you will have to do that yourself
(for now).

Optimisations - The program has not been optimised for speed. Optimisation
will be looked at once it is all working.

The priority order for current work is:
1. Fixing bugs
2. Further audio support
3. Other new features
4. Speed optimisations

-----------------------------------------------------------------------------

1.5. Why Was FairUse Written?

FairUse was written because the author feels strongly that the actions
taken by the motion picture industry in relation to DVDs have been unfairly
restrictive. "Innovations" such as region coding and macrovision, in
addition to practices such as unskippable studio advertisements at the start
of most DVDs only serve to discourage and frustrate legitimate DVD users.
This program returns some measure of control to us, the end users.

-----------------------------------------------------------------------------

1.6. So What's Up With That Name?

The name FairUse is a reference to the "fair use" provisions which exist
under most copyright laws. The fact that the motion picture industry's
stance on region protection, CSS and content control makes me want to scream
"FU" is a complete coincidence.

-----------------------------------------------------------------------------

1.7. Isn't This Illegal?

Not in my country, and in a number of others. Despite what the "content
industry" would like you to believe, under these laws, it is legal
to make a copy or convert a copyrighted material into another format
for the owner's own personal use. If this is not legal where you are, then
you are contravening the FairUse "Conditions Of Use" and should not
use this software.

-----------------------------------------------------------------------------

2. Answers to Common Problems and Questions

2.1.  How Do I Install FairUse?

No "installation" process is necessary to use FairUse. Simply extract all
files from the distribution zip file into a directory and run the executable.

-----------------------------------------------------------------------------

2.2.  What Version Of DivX Should I Install To Use FairUse?

None is required for FairUse to operate. The program does not require DivX
to be installed because it contains its own specific version of the codecs.
This alleviates any problems with incorrect codec versions and fixes some
codec problems (See section 3.9).

As of 0.30 beta, these codecs are contained within the FairUse executable
itself, so the files fu-fm.dll and fu-lm.dll (from earlier versions) are no
longer needed and can be deleted.

Of course if you actually want to play the AVI files generated, you will need
at least the DirectShow decoder installed. I would recommend installing
DivX version 3.11 alpha.

-----------------------------------------------------------------------------

2.3.  Can I Use VOBs On My HDD I Made With Program X?

Not at present, although this feature may be included at a later time.

This is for two main reasons:

1. FairUse accesses the DVD data at the lowest possible layer, just like a
software DVD player would. It does not open the VOB and IFO files as
presented by Windows, but parses the underlying filesystem that all
DVD-Video disks must be formatted with. This helps ensure maximum
compatibility with DVD-Video disks, and helps to ensure that if a standalone
player can play the disk, FairUse will be able to read it too.

2. FairUse requires the DVD data to be available exactly as it is stored on
the disk (both VOB and IFO files). Most of the current "rippers" have
numerous options that modify the VOB files as they are being ripped, and
this is very bad for FairUse. To protect against this causing crashes,
FairUse would have to do extensive checking of the files before allowing
them to be used.

-----------------------------------------------------------------------------

2.4.  Can I Use Those ".raw" Files As VOBs With Program X?

No. These are more than simple "rips" of the DVD VOB files. The .raw files
contain cached raw DVD data, including UDF filesystem and directory
information. In addition, the order in which the data is stored in depends
on the order in which it was first accessed.

-----------------------------------------------------------------------------

2.5.  "Building Program Chain Index" Takes A Long Time.

This stage should take on the order of between 15 to 45 minutes, and
will normally be limited by the speed of your DVD drive. If you find that
the time estimate is far in excess of these figures, check that DMA
transfer mode is enabled for your DVD-Rom drive.

-----------------------------------------------------------------------------

2.6. How Much Drive Space Do I Need?

The files that will use a large amount of hard disk drive space are the
cached DVD data files (.raw) and the various bit-rate DivX encodings.

The amount of drive space will obviously depend on the length of the
sequence/feature that you are encoding and the resolution you are using,
however as a rough guide an average length feature film, 4 encodings and
a final product AVI may take up to 7 Gigabytes.

-----------------------------------------------------------------------------

2.7.  How Long Does The Encoding Take?

How long is a piece of string? There are so many variables here as to make
reasonable estimation difficult. Number of processors, system memory,
length of the feature footage, number of encodings and whether or not the
PC is used at all during the process are just some of the major factors
that can affect the time taken.

However as a reference a 2 hour feature was encoded using 4 data rates
at 528 x 288 with a target size of 650 Megabytes on the system below.
The entire process took approximately 22 hours.

Celeron 500MHz PC
Windows 2000
256 Mb RAM
Quantum ATA-66 HDD

-----------------------------------------------------------------------------

2.8.  I'm Not Sure How To Use A Certain Feature/Section Of FairUse.

Anywhere that it is possible, FairUse has sensible default values or has
a method for FairUse to use its own judgement (auto-detect) to set values
within the FairUse wizard. If you are unsure of what a feature of the wizard
is for, you should use these automatic judgements where they are available.

-----------------------------------------------------------------------------

2.9.  How Do I Determine The Best Data Rates For Encodings?

For best results, the data rates for each of the low motion encodings should
be evenly spaced and roughly centred on the average data rate. A single
fast motion encoding at approximately three times the average data rate
serves as a upper bound. This fast motion encoding also means that it is best
to lower the point the low motion encodings are centred around.

When in doubt, try the "Auto Add" function. While this is not perfect, it
provides reasonable defaults for a first attempt.

-----------------------------------------------------------------------------

2.10. Why Isn't My Favourite Resolution Listed? 

The output resolutions you can use with FairUse are constrained in the
following ways:

  (a) The width and height must be exact multiples of 16. This is because the
      DivX codecs internally pad to a multiple of 16 anyway, and so using a
      multiple of 16 in the first place is a good idea.

  (b) The video cannot be stretched in either dimension, only left the same
      size or shrunk. You cannot "extract" more detail by stretching the
      image, doing this only creates more data that needs compressing. It's
      best to leave enlarging the image to the player to do during playback.

  (c) The output pixels must be resized to have a 1:1 aspect ratio. This is
      due to the fact that the output will be an AVI file. So you can
      arbitarily select the width or the height, but not both.

If your favourite resolution is not listed, even after you have unchecked
"Show only preferred resolutions", then it violates one of the above
constraints, and is probably not a good idea anyway.

-----------------------------------------------------------------------------

2.11. But Really, My Video Should Be Exactly 1.85:1 (or 2.35:1).

The aspect ratio listed on the DVD case or on IMDB is very rarely an exact
match for what is actually on the DVD itself. Differences in the transfer and
authoring processes often lead to different sized "black borders" on each
title. As far as FairUse is concerned, the three parameters that really
control the output image aspect ratio are:

  (a) Whether the DVD is NTSC or PAL.

  (b) Whether the DVD is anamorphic (16:9 enhanced) or not.

  (c) The cropping region you have selected.

Parameters (a) and (b) are read from the DVD. Parameter (c) is under your
control, and you can adjust it as you wish. FairUse will then give you a
choice of output resolutions, as outlined in section 2.10.

-----------------------------------------------------------------------------

2.12. What Does It Mean "Preferred" Resolutions?

Because the width and height are both constrained to a multiple of 16 pixels,
it is not normally possible to exactly match a selected cropping region to
an output size and still maintain the correct pixel aspect ratio.

So FairUse must apply a small amount of extra cropping (usually about 2-6
pixels worth) before resizing the video. This extra cropping can either be
done on the top/bottom or on the sides. For fullscreen video (aspect ratio
< 1.4:1), FairUse prefers to keep the full width and crop the top/bottom.
For widescreen video (aspect ratio > 1.4:1), FairUse prefers to keep the
full height and crop the sides. The "preferred resolutions" checkbox controls
whether all resolutions are shown, or only the preferred ones.

Also, any resolutions with either a too high or too low compression ratio
are considered to be "not preferred".

-----------------------------------------------------------------------------

2.13. How Do I Select The Best Resolution/Compression Ratio?

Once you have chosen your target output DivX AVI file size and selected the
audio data rate, FairUse can calculate the maximum amount of "bits" that will
be available for video data in the output AVI file. This allows it to list
the compression ratios that the DivX codec will have to achieve for a variety
of different resolutions.

As a guide to selection of a resolution that will give a high quality result,
you should aim for a compression ratio of approximately 120 for movies that
contain a lot of action sequences, and a compression ratio of approximately
150 for movies that do not. This assumes the DVD is a good clean transfer.
If the transfer is poor and contains a lot of noise, then you should aim for
a lower compression ratio.

You can ignore the compression ratio if you like, but don't be surprised if
the final AVI file has a high "diff threshold" and looks like crap.

-----------------------------------------------------------------------------

2.14. What Does This "Diff Threshold" Mean?

So you've chosen your resolution and let the encodings finish and FairUse
has spat out some number called the "diff threshold". This is FairUse's
evaluation of the quality of the final AVI file produced. If FairUse gives
you a value of less than 11000 then it believes that it has produced a good
result. A value of between 11000 and 12000 mean that FairUse has produced an
acceptable result. Values over 12000 mean that the resulting AVI will probably
display artifacts.

Note: A diff threshold of zero does not mean that a "perfect" AVI has been
produced, just that FairUse has produced the best file possible with the
available encodings.

-----------------------------------------------------------------------------

2.15. My Final AVI Looks Like Crap!

So, you followed through all this and your final DivX AVI looked bad in some
way. The first thing to do is to look at what your "Diff Threshold" (See
Section 2.14) was. It was pretty high right? This means that the parameters
you entered for your target AVI were beyond the ability of the codec, i.e.
you were trying to fit too much data into too little space. There are a
number of ways you can look at fixing this:

1. Increase the target file size.
By increasing the size of the DivX AVI file that you are trying to make, you
don't force the codec to do so much compression. By compressing the data less
the cross-cutter can use more footage from the lower data rate (i.e. less
compressed) data streams. Less compression equals better quality.
This is the easiest and quickest option, because you don't need to do any
more encodings, provided you won't want to modify the final size too much. If
you wanted to (say) double the available size, then you should probably go back
and generate a couple of encodings near the new average bitrate.

2. Decrease the target resolution.
By decreasing the resolution of the DivX AVI file that you are trying to make,
you are trying to encode less information, which means that the codec does
not have to perform as much compression. As with point 1, less compression
equals better quality. For this you must create a new session, and regenerate
all the encodings.

3. Add more encodings.
By adding more encodings (as described in Section 2.9) the cross-cutter has
more options for selecting appropriate frames in order to get good quality
while keeping the AVI size to the target file size. However, as the data
rates of the encodings get closer together, the benefit from added encodings
diminishes.

-----------------------------------------------------------------------------

2.16. My Final AVI Still Looks Like Crap!

So, you read Section 2.15, made some changes and you *still* get a low
quality result. Sure you could drop the resolution more, but why does this
feature need to be so small compared to that last one you just did? The
answer is normally in either the DVD transfer or maybe the type of footage.
As you probably realise, DivX works by compressing the video. This compression
is in-part done by removing redundant information from the video stream, for
example if you have a big blue sky in a scene, then that is all duplicated
information and can be easily reduced. However if you have a DVD that has
been produced from some old film stock or the transfer process has introduced
lots of noise, instead of a big blue sky, you get a big blue sky with lots
of sparkles, flickers etc in it. Of course the codec isn't to know that it
can discard all those sparkles, and so it tries to encode them. This means
that you get substantially less compression. The effect of all of this, you
will never be able to compress these poor transfers as well, this means
having to increase the file size or reduce the resolution more than you
might have liked to.

-----------------------------------------------------------------------------

2.17. Can I Manually Select Which Frames To Use In The Cross-Cut?

No. The cross-cut is completely handled internally by FairUse. However the
cross-cutter is pretty smart, and in my experiences does a very good job
with the encodings that you provide. For more information on the cross-cutter
see Section 3.7.

-----------------------------------------------------------------------------

2.18. Multi-Angle Scenes Are Repeatedly Inserted.

This was a problem with program versions earlier than 0.22 beta. Upgrade to
the latest version, but see Section 1.2 for an important note.

-----------------------------------------------------------------------------

2.19. What's This Indexing Process?

During the indexing phase, FairUse is pre-processing the selected program
chain, examining the embedded timing information, and building an index into
the streams. This index is used later to allow frame accurate random access
to the streams, as well as ensuring synchronisation between the video, audio
and subpicture streams.

During this process, if the DVD data needed is not cached, it will be read
from the DVD.

Once this index is built, it is stored in a ".chain" file, so that the next
time it is needed, it can be just read back from the file (which is much
faster than reindexing the chain from scratch).

-----------------------------------------------------------------------------

3. Technical Information

3.1. How Does The Descrambling Work?

The descrambling code was written from scratch. It uses ASPI and a UDF
parser, and so works in a similar manner to DeCSS/DOD SpeedRipper. However,
unlike these tools, it knows a "few" player keys so it won't be blacklisted
any time soon.

-----------------------------------------------------------------------------

3.2. Can FairUse Handle DVDs With Authoring Errors?

When a DVD changes keys in the middle of a title, even a standalone player
will not play it. However, FairUse gets a new key at the start of each "cell"
so it may be able to work with DVDs like this, but this has not been
confirmed.

FairUse is also able to read DVDs with VOBs over 1GB, due to it's low level
DVD access.

Confirmation of how FairUse behaves with problem DVDs would be appreciated.

-----------------------------------------------------------------------------

3.3. How Does The Decoder Work?

The lowest layer of the video decoder began as early version of MPEG2AVI.
Over time, much of it has been replaced.

-----------------------------------------------------------------------------

3.4. How Does The Inverse Telecine (IVTC) Functionality Work?

The IVTC functionality is integrated deeply into FairUse, and was written
from scratch. It looks for interlaced frames and repeated fields, and should
work properly even when the IVTC offset changes, or the video switches 
between hard and soft 3:2 pull down. 

The same interlace metric is used on PAL titles to realign fields that have
been either orphaned after editing or incorrectly interleaved due to
mastering errors.

Note: The preview window uses "native" mode, so it will show interlaced
frames if they are present.

-----------------------------------------------------------------------------

3.5. How Does The Variable Key Interval (VKI) Functionality Work?

The VKI functionality is integrated deeply into FairUse and was written
from scratch. Each frame is compared with the previous and assigned a value
that indicates how "stationary" or "still" it is, (i.e. how much of it has
not changed). The encoder will then try to avoid inserting keyframes when
the stationary value is high (i.e. a still frame).

There is also a sliding scale of stationary values as the maximum key frame
interval approaches. This means that the philosophy is not so much "keyframe
on scene change" but rather more "avoid keyframes during still scenes". This
increases the quality by avoiding the "sharpening" effect that is visible
when a keyframe is inserted in the middle of a still scene.

A keyframe is also inserted when a gross codec error is detected (grey
blocks, mirrored blocks, dropped frames, etc).

-----------------------------------------------------------------------------

3.6. How Is The Quality Of Images Calculated?

The quality metric was designed specifically for FairUse, and uses a custom
algorithm that aims to model how the human eye perceives image distortion.

It looks at the original image and uses its model to create a mask of areas
in which the human eye can see a lot of detail and those in which it can't.
It then also creates a "temporal" mask to account for the fact that the human
eye can see less detail when an object is in motion. These masks are then
used to weight different areas of the image and compare the compressed image
to the original. From this the "diff" metric is calculated which measures the
"visible" differences.

The algorithm is not perfect, and tends to over-estimate the "difference"
value about 1% of the time. This is not really a problem, as it just causes
a small number of scenes to have slightly more bits allocated to them than
they really need.

-----------------------------------------------------------------------------

3.7. How Does The Cross-Cutter Work?

The cross-cutter was designed specifically for FairUse. It first chooses
a diff cutoff value, discarding any frames with a diff value above that
cutoff. It then produces the smallest possible AVI file from the remaining
frames. This process is repeated (using a binary search) until the lowest
cutoff (highest quality) file is found that does not exceed the target file
size.

The result is a file of the highest constant quality that is still smaller
than the size you specified.

The cross-cutter is limited by the encodings you provide it. These encodings
set a minimum and maximum file size that the cross-cutter can produce. If
your output file is too small, then it is very likely that the "diff
threshold" reported was zero, and the cross-cutter produced the highest
quality file it could from the encodings that were available.

-----------------------------------------------------------------------------

3.8. What Kind Of Audio Encoding Will Be Included?

Audio encoding is in the pipeline, but the exact options are yet to be
determined.

-----------------------------------------------------------------------------

3.9. What Changes Were Made To The DivX Codecs Included With FairUse?

The original DivX 3.11 codecs can (under some circumstances) automatically
add keyframes when they feel it is appropriate. In some circumstances, this
was found to have a negative effect upon the quality of the resulting AVI and
this "feature" has been disabled in the included codecs.

-----------------------------------------------------------------------------

4. How to Get Further Assistance

4.1. You Still Haven't Answered My Question!

If you think an answer is incomplete or inaccurate, please post a message in
Doom9's FairUse forum, on www.doom9.org.

Try experimenting. That's the best way to get to know FairUse.

Read the latest Readme documentation.

Make sure you don't have an out-of-date copy of the program. The version of
FairUse this FAQ has been written for is specified above in section 1.2.

Read the FairUse forum on www.doom9.org. If you still require help then
submit a post to the FairUse forum.

-----------------------------------------------------------------------------

4.2. What to Put in a Request for Help.

Please include as much detail as possible. Especially for quality problems,
you need to know: the compression ratio you selected (on the resize page),
and the "diff threshold" of the final AVI file.

-----------------------------------------------------------------------------

5. Release History

0.1 beta    First public release

0.2 beta    Video resizer now uses low pass and cubic reconstruction filters
            Squashed an NTSC IVTC subpicture synchronisation bug

0.21 beta   Fixed a bug with NTSC IVTC sometimes not counting fields properly,
              which would cause a slight loss of sync
            Tweaked the NTSC IVTC to work a bit better on movies with a lot
              of "noise" present in the transfer (older movies)
            Fixed a DivX codec problem where it would insert many keyframes
              by itself if the number of pixels per frame was less than
              184320; this could cause significant quality problems
            Increased timeouts so they are less likely to happen if the system
              is loaded up with some other task; added some diagnostics to
              show status of decoder timeouts

0.22 beta   *** IMPORTANT NOTE: With this version, the project and chain file
              formats have been changed. You should finish any current
            sessions before trying to use this version. ***

            Added better error messages when the encoders have problems (like
              running out of disk space, etc)
            Fixed an IFO parsing bug which would cause a crash if a title-set
              had no menu VOBs
            Fixed the IFO parsing to (hopefully) handle angles properly; each
              angle should now appear as a separate program chain
            Fixed a small bug with the subpicture next/previous buttons
            Changed the way subpictures with no end time are handled
            Added a timeout at the lowest DVD access layer to try to resolve
              a problem with scratched disks

0.23 beta   Added a key fallback mechanism and more diagnostic output to try
              to resolve the problem with a few DVDs where the key can't be
              found

0.24 beta   Added an extra check for anamorphic titles that seem to have
              inconsistant aspect ratio flags
            Removed the key fallback mechanism that was added in 0.23 beta
              because it didn't fix the key problem

0.25 beta   Added an automatic key retry mechanism to fix a problem getting
              keys from some DVDs using some DVD drives; you need to create a
              new project if you want to take advantage of this fix

0.26 beta   Changed the AVI writer so it is more compatible with streams
              generated by other programs
            Changed the way anamorphic/non-anamorphic titles are detected,
              hopefully all titles will be correctly detected now
            Modified the "gross" error detector to be a bit more sensitive,
              hopefully it will pick up all visible codec errors now
            Fixed a problem with the demuxer that occurred when there was
              skipped data in the streams
            Increased the timeouts, especially when the decoder is waiting
              for all the encoders to finish up

0.30 beta   *** IMPORTANT NOTE: With this version, the project and chain file
              formats have been changed. You should finish any current
            sessions before trying to use this version. ***

            Audio _demuxing_ has been added; currently only AC3 streams are
              supported; audio decoding and combining are still unsupported,
              so it's not idiot-proof yet
            A new "diff tracking" encoding mode has been added; see the
              notes section lower down for details
            All encodings are now done in the one process, and all timeouts
              have been removed, so it doesn't matter how much the CPU is
              loaded by other tasks
            Added a confirmation dialog so that it's more difficult to abort
              long processes accidently; this is only on the main GUI
              window; if you close the diagnostic window the program will
              terminate immediately
            Changed output FourCC from "div3" to "DIV3" for increased
              compatibility with other programs/operating systems
            Changed the IFO parser to correctly handle DVDs with missing
              titles; also some DVDs with IFO errors (like The Day of the
              Jackal R2) will no longer cause a crash
            Changed the video decoder to ignore the MPEG2 temporal reference
              field; this field can sometimes be wrong, and it would cause
              "cloning frame ..." messages and sync problems
            Changed the resizer to follow ITU-R BT.601 standard; images will
              be about 2% "shorter and fatter" than they were before
            Fixed a bug that caused the quality setting of the decoder to be
              indeterminate; this could cause the quality of different
              encodings to be "weighted" differently and would cause the
              cross-cutter to be biased; image quality is now measured
              with the frame always decoded at quality level 0
            Fixed a bug with the subtitle colors (the chroma channels were
              swapped)
            Codec DLLs are now stored in the EXE file, and not as separate
              files; the old FU-FM.DLL and FU-LM.DLL can be deleted
            Adjusted the keyframe min/max interval code to ignore keyframes
              that were inserted to fix gross errors; this keeps keyframes
              more consistent across encodings
            The encodings/session limit has been increased from 10 to 30
            The maximum audio bitrate has been increased from 512 kbit/s to
              1024 kbits/s

-----------------------------------------------------------------------------

6. Acknowledgments and Administrivia

6.1. Feedback Is Invited.

Please provide comments on the FairUse Wizard and this FAQ. Please make use
of the FairUse forum on www.doom9.org.
