KMPlayer'> ]> Koos Vriezen

koos dot vriezen at gmail dot com

2002 2006 2007 Koos Vriezen &FDLNotice; 2007-07-28 0.06.00 &kmplayer; is an application that is a &kde; frontend to MPlayer, Xine and GStreamer. KDE kdemultimedia MPlayer konqueror video &kmplayer; is a simple frontend to MPlayer, Xine, GStreamer and FFMpeg. You can use it for watching all the movie file formats that MPlayer, Xine or GStreamer supports as well as watching from DVD, VCD or TV and camera. The documentation for &kappname; was not finished when &kde; was installed on this computer. If you need more help, please check The KDE Website for updates, or by submitting your question to The &kde; User Mailing list. The &kde; Team The application window is made of so called dockable windows. There is always the central view window. Optional there is the playlist window. And finally there is an info window, that just shows itself when some information is there to been shown.

The playlist window has as of this writing five categories, current item(s), Optical Disks, Television, Persistent Playlists and Most Recent. When clicked on a category's text, it will show the contents below this line. Of course there has to be contents, eg. see TV settings for adding content for the Television category. The Most Recent category will fill itself when playing locale media files or network Urls. This category can hold 60 items of which the last 50 are under the More .. branch.

It's possible to store your favorite links in the Bookmark menu, but those are single items. If you want to create a list of items that play after each other, than you should use the Persistent Playlists category. The easiest way to add an item in this list is to drag it from Most Recent and drop it on Persistent Playlists. As you will see, when dropped, a pop-up menu appears where you can choose to add to this list or create a new group. Top level items behave like a bookmark item, but items in groups will play the whole group wherein they reside. Items in this category can easily be moved, copied, added to a new group or deleted just by dragging this item to another place in this category. Additionally there are Delete item, Move up and Move down items in the context menu (when clicking with the right mouse button on an item). Of course you can add groups to groups to get a deeper hierarchy. When clicked on an item, its group and all its child groups will be copied to the current category and playings starts at the clicked item position.

The data is stored in ~/.trinity/share/apps/kmplayer/playlist.xml, and its format is like this example. See here for manipulating this data directly. <playlist> <group title="feeds"> <item url="http://www.lugradio.org/episodes.rss"/> <item url="http://science.nasa.gov/podcast.xml"/> <item url="http://www.theworld.org/rss/tech.xml"/> </group> <group title="iradio"> <group title="sunny"> <item mplayeropts="-cache 256" url="http://www.swissgroove.ch/listen.m3u"/> <item url="http://www.boombasticradio.com/shoutcast/64.pls"/> </group> <group title="rainy"> <item url="http://www.radioparadise.com/musiclinks/rp_64.m3u"/> <item url="http://www.woxy.com/stream/wma64.asx"/> <item url="http://radionigel.com/winmedia.asx"/> <item url="rtsp://livestreams.omroep.nl/live/vpro/vpro3voor12radioalt.rm"/> </group> </group> </playlist> Also note that for MPlayer custom options can be set using the mplayeropts argument. &kmplayer; searches for this option upwards in the tree, so you can set it for a whole group and override it for a child group or item.

The current, Television and Persistent Playlists categories can also be manipulated by editing their XML storage. Of course one can do that when &kmplayer; is not running and editing the various files in ~/.trinity/share/apps/kmplayer/, but also in the application itself. Simply click on a catergory label, then choose View and next Edit mode. You can also click on a child branch and will then see only the XML contents of the branch. After you have edited some XML, click on the Sync with playlist and either deselect the Edit mode item or click on another catergory. All changes are lost when leaving edit mode or selecting another branch without syncing with playlist. Because of the lazyness of &kmplayer;'s author(s), some features can only be enabled by editing the XML.

Disabling the starting/ending animation can be configured by editing ~/.trinity/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. ~/.trinity/share/apps/kmplayer/intro.xml and ~/.trinity/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.

&kmplayer; uses external programs to do the actual playing.

There is a configuration tab for MPlayer in &kmplayer;'s config dialog. Here you can set MPlayer's path and it cache size for network stream, among other things. This player configuration name is mplayer.

The best way to debug this backend is to start &kmplayer; from a console application like konsole. Then start a movie with kmplayer and see the exact commandline that is used to start mplayer in the console application. Now copy/paste that to another console, remove the '-wid 12344' options, and make it play. Probably it's just choosing the right -ao/-vo params. Also make sure mplayer doesn't start default with a GUI. Another debugging tool is the 'console' button in kmplayer's toolbar. Here you can see the output from mplayer.

When configured &kmplayer; with Xine support, there will be configuration tab for Xine in &kmplayer;'s config dialog. Here you can set various options. These options are dynamic retrieved from the Xine library. Use context help to get information on what these options do (ie. click on the question mark button from the dialog title bar and then click on an option). This player configuration name is xine. The options are saved in .kde/share/apps/kmplayer/xine_config as a text document.

Basically the same way as trouble shooting MPlayer, with the application name of kxineplayer.

There is no configuration tab for GStreamer in &kmplayer;'s config dialog. The common options for eg. DVD device are used when appropriate. This player configuration name is gstreamer.

Basically the same way as trouble shooting MPlayer, with the application name of kgstplayer.

There is no configuration tab for this player in &kmplayer;'s config dialog. Everything must be configured by manually editing the ~/.trinity/share/config/kmplayerrc like with configuring the backend per mimetype. This is an example how to let flash be played with the swfdec-mozilla plugin: [application/x-shockwave-flash] player=npp plugin=/usr/lib/mozilla/plugins/libswfdecmozilla.so You can play flash inside &kmplayer;, actually you can even paste the special embed field for YouTube in the playlist XML. In order to let &kmplayer; play flash in HTML pages, you should make the &kmplayer; plugin the service provider for the application/x-shockwave-flash mimetype in KDE's File Associations configuration dialog. As in the above example, this player configuration name is npp.

Start Konqueror or &kmplayer; in a console application and look for errors about loading the browser plugin library. The process started is called knpplayer. If that doesn't give any errors, check the backend output capturing inside &kmplayer; (View, Console, or Console from the popup menu).

To configure to always use a given backend for a particular mimetype (if detected of course) can be done by manually editing the ~/.trinity/share/config/kmplayerrc. For example, let xine play all ogg files: [audio/ogg] player=xine

&kmplayer; can play from various sources. These sources are listed in the Source menu.

&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 ~/.trinity/share/apps/kmplayer/tv.xml. See here for manipulating this data directly. 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="216"/> <channel name="VCR" frequency="594.90"/> </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 your monitor. Also no annoying flicker when another window overlaps this video window. See the VDR section for more information about using XVideo.

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.

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.

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 ~/.trinity/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, ~/.trinity/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. &kmplayer; copyright 2002,2003 Koos Vriezen &underFDL; &underGPL; &documentation.index;