|
|
|
Documentation: MP4Player README
May, 2005
This is the beginning of a README for mp4player that will answer
some questions on how to use mp4player.
Command line arguments
Command line argumentsmp4player will take a -loop or --loop option (to loop). Both mp4player and gmp4player will take a file name/url to start playing. As of 1.1, mp4player and gmp4player will take configuration variables in the command line. Use --<variable>=<value>, and make sure that the correct case is used. You can display the configuration variable list by using either -c or --config-vars That's it.
Configuration VariablesConfiguration variables are stored in the windows registry for Windows (see below), and in ~/.gmp4player_rc for every other OS. Configuration variables are read at start, and apply to the entire session. Some can be changed with GUI knobs. The latest list of configuration variables can be found in our_config_file.cpp. LOG_* defines can be found in include/systems.h Boolean values must be 0 or 1. Here is the current list by categories:
Player PluginsStarting with version 0.9.3.2, we've gone to a plugin model for audio and video codecs for the player. This is true for both windows and linux platforms. As of 0.9.7, we also have plugins available for RTP byte streams. Release 1.3 adds text type plugins. On linux (and linux like) platforms, the plugins should be in the mp4player_plugin directory, which is a sub directory of where the other mpeg4ip libraries will be stored. You must do a make install of the plugin when running/debugging with plugins - the player does not currently search for plugins. When installing a new version of the plugins, it is a good idea to purge this directory. On Windows, the .dlls that get created must be in the same directory as the executable for mp4player.exe or wmp4client.exe. The project files should copy the plugin DLLs to the player/src directory, so when running the player, it should work fine. The plugin pattern can be found in player/src/codec_plugin.h and in player/src/rtp_plugin.h. Both plugins contain a version number to enable detection of API changes.
Player URLSWe have 2 special type URLs for the player to play content. The first one is for mpeg2 transport streams. To play an mpeg2 transport stream over UDP, use the following url: mpeg2t://<multicast address>:<multicast port> The 2nd special URL is to play a stream from a Cisco IP/TV server, either broadcast or on demand. To do this, use the following url: iptv://<iptv content manager>/<program id> Where iptv content manager is the address of the IP/TV content manager, and program id is the session id that is created. You can find this out by looking at the program on the content manager, or get the session id by running the iptv_prog utility with the content manager as a parameter.
ISMA Href SupportIn release 1.3, we implemented support for ISMA href. This is a method that allows timed opening of web pages to synchronize with audio and video. There are 2 methods that can be used; automatically dispatching URLs, or click to dispatch. Normally, the cursor will be off in the video window while the video is running. Click to dispatch will enable the cursor in the window while active. While using this feature, the browser should be set to open new urls in the existing window. In Firefox, this setting is in Preferences->Advanced->Tabbed Browsing. Make sure "Open Links From Other Applications" is set to "the most recent tab/window". On Windows, the default browser will be used. On Mac OS X, the "open" command is used (which should use the default browser). On Linux, /usr/bin/firefox/firefox is tried. The browser in question can be set up by using the UrlExec configuration file setting; the full path to the browser should be used. On Linux, Konquerer web browser can not be used, as it will open a different process for each url. On Mac OS X, Safari should be avoided; there is no setting to open URLs in the same window, only in a new window or new tab.
MP4Player key shortcutsIf you are using mp4player (or gmp4player), the following key short cuts can be used, assuming you've got a video window:
Windows GUIFirst - if you're the type of person who wants the player to work with a nice interface, this isn't the place for you. Go see Quicktime or Envivio players. We've created a simple windows GUI. It consists of 2 parts - wmp4player and wmp4client. wmp4player contains the GUI, and wmp4client is basically mp4player that will communicate with wmp4player. wmp4client is launched as a seperate process, due to SDL limitations. The 2 processes communicate using file maps in memory. See the CMp4Process and CMP4If classes in wmp4player and CClientProcess in wmp4client. To create this, look for the player60.dsw in player/src directory. This will make all 3 executables (mp4player, wmp4player.exe and wmp4client.exe, as well as all the plugins). To install wmp4player, put the Release version (ie: versions from the Release folder) of wmp4player.exe, wmp4client.exe and SDL.dll in the same directory. We will not be writing any installers. In addition, make sure all desired plugins are in the same directory. These programs will use the registry for storing information that Linux stores in .gmp4player_rc. Look for the Software\Mpeg4ip\Config registry entry. Our config file library is rigged to save this data there. mp4player will still use a gmp4player_rc file. At this time, if it's broken, you're going to have to fix it. The same goes with GUI "nits" - we're not GUI writers. Currently, there is no playlist support, no loop support, no drag and drop support, no wmp4player command line support, no accelerator from the dialog window (accelerators from the video window still work).
Known Problems
=== END OF README ===
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|
