This page describes how to set up and run JMF for Linux, an optimized implementation of JMF that contains class files and native libraries for running JMF players.
/home/someuser/
. A
JMF-2.1.1e
subdirectory will be created.
Set your CLASSPATH path to reference the JMF directory. For example,
setenv JMFHOME /home/someuser/JMF-2.1.1e
setenv CLASSPATH $JMFHOME/lib/jmf.jar:.:${CLASSPATH}
setenv LD_LIBRARY_PATH $JMFHOME/lib:${LD_LIBRARY_PATH}
JMF consists of a collection of media handlers, plugins and capture devices. They are configurable and extensible. To configure JMF, use the JMFRegistry application.
Running the RTP applets and Applications
You can only play unicast and broadcast streams using RTPPlayerApplet. To play a multicast stream or to transmit, you need to use the application JMStudio. See the RTP release notes for more information.
Running JMF with Netscape Communicator
JMF can be used with Netscape Communicator 4.06 or later on Linux. Setting the CLASSPATH and LD_LIBRARY_PATH as described above should enable JMF to run with Communicator.
If a particular type of file doesn't work with Netscape, first check if the MIME type for this type of file is set correctly. By default, Netscape doesn't provide the settings for MIDI (
audio/midi
), RMF (
audio/rmf
), and GSM (
audio/x-gsm
) files. In Communicator, you can add and modify the MIME types from the
Edit->Preferences menu, in
Navigator/Applications category. Alternatively, you can edit the $(HOME)/.mime-types file with the following additions:
audio/rmf rmf
audio/midi midi
audio/gsm gsm
Note: JMF requires access to several resources outside the normal Java sandbox. When Communicator brings up dialogs asking you to grant privileges to JMF applets, you should grant them. To avoid the repeated display of security dialogs, you might want to enable "Remember this decision".