AVInfo tiny ChaVo (FAQ)

Q: Why AVInfo 0.7 (and higher) is so slow (when using in scripts for processing a lot of files)?
A: Because starting from version 0.7 AVInfo reads bitrate data from index.
   Index is very large (~1-8Mb per file), so it's slow for reading.
   If you are not intrested in the bitrates, use a -fx option to disable the index reading.

Q: I wish more speed.
A: Try -fix option (no bitrate data, no LIST-INFO data)

Q: I wish more speed!
A: Try -fisx option (and get only header data -_-).

Q: Something strange at my screen! (garbage)
A: try -f7 option to disable an 8-bit's output

Q: Avinfo traped at my favorite avi file.
A: Fist, check avinfo with a -eem key. If it doesn't trap, exit and print error message
   possibly, your avi is broken. (If you are sure in "no" - contact me, please)
   If it traps with -eem option - mail me, please.

Q: How about asf/mpeg files?
A: I'm thinking about this. (see DOC/todo)

Q: Why sound bitrate so strage (127kbps, 54 kbps)? It's bug?
A: No. Real situation. AVInfo just calculates a bitrate (e.g. for audio) as a 
   (audio data size)/(movie length).

Q: My AVI file contain a 2 audio streams, and AVInfo shows a wrong audio bitrate!
A: This is a feature. In header teplate &ab shows summary audio bitrate of all
   audio streams. (And &vb - for video). Use an a --struct-report key for  detail 
   report for each stream.

Q: When AVInfo prints a INFO data (in my language), they prints in wrong codepage.
A: M... I'm know about this. Think about this as a feature. //Really it's a bug :(
   It's too heavy to fix. Try -f7 to skip them.

Q: I'm found the avi file with a fourcc signature, and AVInfo doesn't now about it.
A: Please, contact the owner of http://www.fourcc.org/ . I'm just using their database.

Q: How about 16-bits version (i.e. DOS-16)?
A: Never. Try by yourself.

Q: AVInfo slides a template, when some data absents.
A: Bug-and-feature. Will be fixed in future version (may be...)

Q: Whats this - bpp?
A: bpp - bits-per-pixel. (for more detail try to search bits per pixel at Google)

Q: OGM support is buggly and uggly!
A: Yes. No docs - no normal support.

Q: How about Sun Solaris?
A: Sorry, only "good-endinan" CPU, like x86. ^_~
