 | |
|
This page describes how to set up and run JMF for Solaris, an optimized implementation of JMF that contains class files and native libraries for running JMF players. The Java Sound API reference implementation is also bundled with this version of JMF Setting Up JMF
setenv LD_LIBRARY_PATH $JMFHOME/lib:${LD_LIBRARY_PATH} You can use the JMF Diagnostics applet to verify that JMF is set up properly on your system. Configuring JMFJMF consists of a collection of media handlers, plugins and capture devices. They are configurable and extensible. To configure JMF, use the JMFRegistry application. See the JMF Registry User's Guide for details. Running JMFYou can run the samples using Appletviewer, browsers (HotJava, Netscape Communicator) and the JMStudio standalone application.Running the RTP applets and ApplicationsYou 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 CommunicatorJMF can be used with Netscape Communicator 4.06 or later on Solaris. 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: 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".audio/rmf rmf Running JMF on Solaris 7 and AboveOn Solaris 7 and above, the Java Virtual Machine needs to be run in native threads to get the significantly improved graphics performance with XIL. This can be done by executing the following shell command before starting the Java VM:
with sh:
THREADS_FLAG=native; export THREADS_FLAG
Check out the launch scripts of the JMF utilities under the bin directory to get examples of how these commands are integrated into the startup scripts. Note: When running in Netscape on Solaris 7 and above, native threads cannot be used. JMF will automatically switch to using non-native (green) threads. The video performance will be significantly degraded as a result. | |||
|
| ||||||||||||
Print-friendly Version
