############################################ assoc .mpg SMPEG # plugins_dir /usr/local/lib/lamp/plugins load shm_renderer load dga_renderer load avifile_player begin fourcc CVID iccvid.dll path /win/c/winnt/system32/ end load mpeg3_player load smpeg_player load xanim_player begin path /usr/lib/xanim end ###############################################Comments start with a '#' and finish at the end of the line.
The 'assoc' keyword is used to associate an extension with a plugin. By default, filenames are read by the first plugin able to play the file, in the order of loading specified in the config file. The 'assoc' keyword allows to bypass this behavior by specifying a plugin for a particular extension. Currently, available plugins names are AVIFILE (for .avi files), SMPEG (for mpegs 1/3), MPEG3 (for mpegs 1/2) and XANIM (for most formats).
The 'load' keyword is used to specify a plugin to load. Plugins are found in the plugins directory (normally, a subdirectory called plugins/ of the directory containing the config file). Another directory can be specified in the config file, using the 'plugins_dir' keyword.
Options can be passed to the plugins in the config file. For this, add a 'begin' keyword after the name of the plugin. The options end with a keyword 'end' on a line.
Each plugin has its own options. For instance, XANIM uses a 'path' option to specify the directories to be searched for xanim codecs. AVIFILE uses also a 'path' option with the path where to find Windows codecs dlls. Particular dlls can be added using the 'fourcc' keyword, the FOURCC code identifying the AVI codec, and the name of the dll.
If the value for your system is higher than 50 Mb/s, then there's nothing for you to worry about, because your X server has some kind of output acceleration. ( Actually, I suspect that most current X servers have it ).
In case of this performance being worse than 30 Mb/s, you'll probably need to turn on write-combining for video card. This should generally be done by X server, but some servers ( for example, X server for XFree86 3.3.6 with s3_savage driver ) don't do it ( shame on them ). Here I'll describe how it could be done by hands in case of Linux.
startx >./startx.log 2>&1Look into the log and find a line similar to this:
(--) SVGA: PCI: S3 Savage4 rev 2, Memory @ 0xe5000000, 0xd8000000Here 0xe5000000 and 0xd8000000 are virtual addresses of your video memory. You'll need one of them.
echo "base= size=0x800000 type=write-combining" >>/proc/mtrr
replacing cat /proc/mtrrFind the line that was added by you. Suppose it starts with "reg02", then type:
echo "disable=2" >>/proc/mtrrand repeat case 3 with another address. You can find details about using /proc/mtrr in Linux kernel sources, file Documentation/mtrr.txt.
a) Add new resolutions to your XF86Config file. For this, you can call LAMP with the -sml option. It will then print a list of ModeLine lines, that you can directly add to your XF86Config file. Then, you will have to restart X to take these modes into account. Note that adding modes to your computer may damage your computer if these modes are not correct, so do it at your own risks ! LAMP accepts two options to modify the computation of modelines:
b) If you run XFree 4.0, and like to compile everything on your computer, you can download its source, and replace the file xc/programs/Xserver/Xext/xf86vmode.c by the one you will find in the patches/ subdirectory of LAMP. This patch will allow applications to dynamically add new resolutions to a running X server (it has been submitted to XFree86.org, but not yet integrated). Then, you can start LAMP with the -xf86bugfix option, to force LAMP to add new resolutions at runtime. The modes will be computed using the same algorithm as in a), and might be modified by the same options (-m_bw and -m_rr).
X Error of failed request: BadName (named color or font does not exist) Major opcode of failed request: 45 (X_OpenFont) Serial number of failed request: 26Well, your system doesn't contain the font used for drawing strings (for subtitles, position and volume). You should modify the shm_renderer.c and dga_renderer.c files and change the font used. The next version of Lamp will solve this problem soon.