Java Media Framework

From Wikipedia, the free encyclopedia

Java Media Framework
JMStudio application
JMF's simple JMStudio application playing a QuickTime movie
Developed by Sun Microsystems
Latest release 2.1.1e / May 23, 2003 (2003-05-23); 1847 days ago
Written in Java
OS Cross-platform
Genre Library for multimedia
Website http://java.sun.com/products/java-media/jmf/

The Java Media Framework (JMF) is a Java Library that enables audio, video and other time-based media to be added to Java applications and applets. This optional package, which can capture, playback, stream, and transcode multiple media formats, extends the Java Platform, Standard Edition (Java SE) and allows development of cross-platform multimedia applications.

Contents

[edit] Versions and Licensing

An initial, playback-only version of JMF was developed by Sun Microsystems, Silicon Graphics, and Intel, and released as JMF 1.0 in 1997. JMF 2.0, developed by Sun and IBM, came out in 1999 and added capture, streaming, pluggable codecs, and transcoding. [1].

JMF 2.0 originally shipped with an MP3 decoder and encoder. This was removed in 2002, and a new MP3 playback-only plug-in was posted in 2004.

JMF binaries are available under a custom license, and the source is available under the SCSL.

The current version ships with four JAR (file format) files, and shell scripts to launch four JMF-based applications:

  • JMStudio - A simple player GUI
  • JMFRegistry - A GUI for managing the JMF "registry," which manages preferences, plug-ins, etc.
  • JMFCustomizer - Used for creating a JAR file that contains only the classes needed by a specific JMF application, which allows developers to ship a smaller application.
  • JMFInit

JMF is available in an all-Java version and as platform-specific "performance packs", which can contain native-code players for the platform, and/or hooks into a multimedia engine specific to that platform. JMF 2.0 offers performance packs for Linux, Solaris and Windows (on SPARC). [2]

[edit] Design Concepts

JMF abstracts the media it works with into DataSources (for media being read into JMF) and DataSinks (for data being exported out). It does not afford the developer significant access to the particulars of any given format; rather, media is represented as sources (themselves obtained from URL's) that can be read in and played, processed, and exported (though not all codecs support processing and transcoding).

A Manager class offers static methods that are the primary point-of-contact with JMF for applications.

[edit] Code Example

The following example shows an AWT file-selection dialog, and attempts to load and play the media file selected by the user.

import javax.media.*;
import java.io.File;
import java.awt.*;
 
public class TrivialJMFPlayer extends Frame {
 
    public static void main (String[] args) {
        try {
            Frame f = new TrivialJMFPlayer();
            f.pack();
            f.setVisible (true);
        } catch (Exception e) {
            e.printStackTrace();
        }
    }
    public TrivialJMFPlayer() 
        throws java.io.IOException,
               java.net.MalformedURLException,
               javax.media.MediaException {
        FileDialog fd = new FileDialog
            (this, "TrivialJMFPlayer", FileDialog.LOAD);
        fd.setVisible(true);
        File f = new File (fd.getDirectory(), fd.getFile());
        Player p = Manager.createRealizedPlayer
            (f.toURL());
        Component c = p.getVisualComponent();
        add (c);
        p.start();
    }
}

Much of the example is involved with the building of the AWT GUI. Only two lines touch JMF. Manager.createRealizedPlayer() implicitly creates a DataSource from a URL representation of the file, creates a Player, and realizes it, meaning that all resources necessary for playback are allocated and initialized. The getVisualComponent() asks the Player for an AWT Component suitable for use in a GUI. If a control component were desired, it would be obtained with getControlPanelComponent() and added to the GUI separately. Note that the developer is not concerned with the format of the media - this code works equally well for any media format that JMF can import and read.

[edit] Criticism and Alternatives

Many JMF developers have complained that it supports few codecs and formats in modern use. Its all-Java version, for example, cannot play MPEG-2, MPEG-4, Windows Media, RealMedia, most QuickTime movies, Flash content newer than Flash 2, and needs a plug-in to play the ubiquitous MP3 format. [3] While the performance packs offer the ability to use the native platform's media library, they're only offered for Linux, Solaris and Windows. Furthermore, Windows-based JMF developers can unwittingly think JMF provides support for more formats than it does, and be surprised when their application is unable to play those formats on other platforms.

Another knock against JMF is Sun's seeming abandonment of it. The API has not been touched since 1999, and the last news item on JMF's home page was posted in November 2004.

While JMF is built for extensibility, there are few such third-party extensions.

Furthermore, editing functionality in JMF is effectively non-existent, which makes a wide range of potential applications impractical.

[edit] Alternatives

Depending on a developer's needs, several other libraries may be more suitable than JMF. These include:

[edit] Using JMF in Webstart

Many users have reported difficulty in using JMF in applications through webstart to write media to the local disk. This is not necessarily a difficult task, just a very specific process.

First, make certain that the Java Media Framework has been installed properly according to the directions listed by sun for your operating system. This part is critical, if the JMFHOME, and CLASSPATH system variables are not set properly, the remaining steps will not work.

Second, run the JMFRegistry application, make certain "Allow File Writing For Applets" is checked, then click Commit. If an error was displayed in the console window, please revisit the first step and make sure that JMF is installed properly.

Third, run JMFCustomizer with the following command "java JMFCustomizer -p <path to javac>". Select all the desired options, and create your own custom jmf.jar.

This jar contains the same registry settings that your development platform was configured with. Now all that remains is to sign it with the same key that the other jars in your application are signed with, and include it in your jnlp file.

[edit] See also

[edit] External links

[edit] References

  1. ^ JMF FAQ
  2. ^ JMF FAQ
  3. ^ JMF 2.1.1 - Supported Formats
Languages