diff --git a/doc/index.docbook b/doc/index.docbook index c522501..726281e 100644 --- a/doc/index.docbook +++ b/doc/index.docbook @@ -1,240 +1,263 @@ Kmplayer'> ]> The &kmplayer; Handbook Koos Vriezen
koos dot vriezen at xs4all dot nl
 2002 2003 Koos Vriezen &FDLNotice; 2003-12-24 0.05.00 &kmplayer; is an application is a &kde; frontend to MPlayer. KDE kdemultimedia MPlayer konqueror video Introduction &kmplayer; is a simple frontend to MPlayer, Xine and FFMpeg. You can use it for watching all the movie file formats that MPlayer/Xine supports as well as watching DVDs, VCD or TV/camera. The documentation for &kappname; was not finished when &kde; was installed on this computer. If you need help, please check The KDE Website for updates, or by submitting your question to The &kde; User Mailing list. The &kde; Team Settings
Intro/exit animation Disabling the starting/ending animation can be configured by editing ~/.kde/share/config/kmplayerrc and modify [General Options] No Intro=0 the above option to '1'. Just add this option if it's not there yet. It's also possible to set an alternative animation. KMPlayer will look at resp. ~/.kde/share/apps/kmplayer/intro.xml and ~/.kde/share/apps/kmplayer/exit.xml. The format has to be a supported XML file. The intro animation doesn't have to be a short one, because it will automatically end when another source is opened. Of course for the exit animation this would be a bit annoying, however the user can always end the application twice. A simple example of an intro, showing your favorite photo can be <smil> <body> <img dur="indefinite" src="file:///home/koos/mum.gif" fit="meet"/> </body> </smil> In KMPlayer's source package, in the tests/ are some examples of SMIL that KMPlayer supports.
The playable sources &kmplayer; can play from various sources. These sources are listed in the Source menu. -
+
TV &kmplayer; can play from TV cards using MPlayer or XVideo (using kxvplayer). Before you can watch TV, you have to configure which device to use and the TV channels. You can use the scanner from the configure dialog for this or edit the config file manually. The config file for TV settings is a XML file, located ~/.kde/share/apps/kmplayer/tv.xml. The XML format is like this example: <tvdevices> <device path="/dev/video0" width="320" height="240" name="BT878 video (Hauppauge (bt878))" audio="" minwidth="48" minheight="32" maxwidth="924" maxheight="576" playback="0" xvport="240"> <input name="Television" id="0" tuner="1" norm="PAL" xvenc="0"> <channel name="Ned1" frequency="21600"/> <channel name="VCR" frequency="59490"/> </input> <input name="Composite1" id="1" xvenc="7"/> <input name="S-Video" id="2" xvenc="14"/> <input name="Composite3" id="3"/> </device> <device path="/dev/video1" width="640" height="480" name="Philips 740 webcam" audio="" minwidth="160" minheight="120" maxwidth="640" maxheight="480" playback="1"> <input name="Webcam" id="0"/> </device> </tvdevices> Note that input elements having channels, should have the tuner attribute set to 1. XVideo only uses the xvport and xvenc attributes and they can only be set by manually editing this file. The values of these two attributes can be retrieved by running kxvplayer in a terminal application like konsole. For every port, kxvplayer will output lines like below and the numbers can be set for the attributes mentioned. xvport 240 .... encoding: 0 PAL-television encoding: 1 NTSC-television encoding: 2 SECAM-television .... Also width and height attributes are ignored by the XVideo player. This player gets the sizes from the X server. One of the nice things of XVideo is that scaling is done in hardware, by the video card, so fullscreen support without CPU usage and without resolution change of you monitor. Also no annoying flicker when another window overlaps this video window. See the VDR section for more information about using XVideo.
-
+
VDR To configure your VDR settings in kmplayer, see the Configure panel->Source->VDR->XVideo port panel. There should be ports detected, from which you should select one. You have to figure out what encoding you should use (eg. for western europe, that is PAL) and likely the correct one has a name with dvb in it. For instance, I have a TV card, a DVB-S card and a webcam pluged into my system. With these, my settings are that there are three Ports. The first one has a long list of NTSC(-JP)/PAL(-M)/SECAM entries all saying something about television/composite/svideo (my TV card). The second one has NTSC-dvb/PAL-dvb/SECAM-dvb (my DVB-S card). And finally the third has only ntsc/pal (probably my webcam). I should therefore configure (just select it) the second port and second entry (PAL-dvb). Because VDR support from kmplayer can only use XVideo, of course XVideo should work (and I believe for video devices, this way of viewing only works on linux). Also this only works on your first display (:0.0). So make sure videoforlinux extension works with the X server. For the XFree86 server, therefor in its configuration (/etc/X11/XF86Config) it should have Section "Module" .... Load "v4l" EndSection Unfortunately, when ever you update your video driver, you have to reconfigure this setting.
+
+ Commandline + + Internally for the sources, KMPlayer uses distinct names. At the time of + this writing these are "dvdnavsource", "dvdsource", "exitsource", + "hrefsource", "introsource", "pipesource", "tvscanner", "tvsource", + "urlsource", "vcdsource" and "vdrsource". When activated, they mostly + starts playing the list of playable items. + + + You can activate a particular source with a kmplayer:// type URL. Just set the host part as the source name and optional path part as extra arguments, so for a channel for the "vdrsource" this could look like kmplayer://vdrsource/22 MTV 2. Eg. this script starts kmplayer using "dvdnavsource" and using DCOP to play fullscreen. + +/bin/bash +kmplayer kmplayer://dvdnavsource/ & +PID=$! +sleep 2 +dcop kmplayer-$PID KMediaPlayer toggleFullScreen + + For some sources this will not do much because they are not meant to be + for normal playing. For "pipesource" this is disabled because that + would be a bad security hole of course. + +
Questions, Answers, and Tips Frequently asked questions Xine starts up slow, why does it have to benchmark my CPU all the time? Note the answer below is outdated. kxineplayer saves it automatically to last value, so only the first time xine will do the CPU test. The Xine frontend for &kmplayer;, kxineplayer, uses ~/.kde/share/apps/kmplayer/xine_config for its configuration. Settings for Xine are found in the configuration dialog General Options|Xine. (If you change an option here and save it, ~/.kde/share/apps/kmplayer/xine_config will contain some explainations too). The CPU benchmarking is caused by the option misc.memcpy_method set to probe. To see which memcpy version works the fastest for you, enable Show Console Output from the View menu and look at the results from this benchmarking when you play something with Xine. Configure misc.memcpy_method with the method with the lowest time. Any hints to make my CDROM less noisy when playing from it (not VCD://)? Sure, try hdparm -E 8 /dev/cdrom as root after mounting the device. But be sure to double check /dev/cdrom pointing to your CDROM drive. Credits and Licenses &kmplayer; copyright 2002,2003 Koos Vriezen &underFDL; &underGPL; &documentation.index;