QUICK NAVIGATOR
PRODUCTS
TECHNOLOGIES
DEVELOPMENT TOOLS
* News
* Java Media Framework
* Intel Animation for Java
* Intel Spatial Audio for Java
* Runtime Software License
* SDK Software License
* System Requirements
* Download Area
* Documentation Online
* Gallery
* General FAQ
* Support Information

[INTEL NAVIGATION HEADER]

Java* Media Framework Package Beta Release Notes

Beta 1.3.0

Contents

I Introduction
II Support
III Installation
IV Uninstall
V Differences Between Java* Media Framework Beta 1.3.0 and Java Media Player Specification Version 0.95
VI Known Problems

Part I. Introduction

The Java Media Framework (JMF) enables Microsoft, Netscape and Sun Java execution environments to run Java applets containing audio and video media.

The JMF is available in two configurations: Software Development Kit (SDK) and Runtime. Install the SDK if you are a developer and you want to integrate video and audio into your Java applets or applications. Install one of the Runtimes if you want to run JMF-enabled Java applets under either Microsoft Internet Explorer* or Netscape Navigator*.

Java Media Framework Beta 1.3.0 is based upon JavaSoft's Java Media Player Specification Version 0.95, which was released on February 4th, 1997. To download this specification, please refer to http://www.javasoft.com/products/java-media/mediaplayer.

This Beta software expires on April 30th, 1997.

Part II. Support

Web Site

The Intel Media for Java home page is the best resource for finding answers to your technical and non-technical questions: http://developer.intel.com/ial/jmedia.
All the following support options are referenced on the Technical Support page.

FAQ

We encourage you to reference the Technical FAQ.
The Technical FAQ is a compilation of questions asked by developers in the Intel Media for Java Newsgroup or Emails to us.

For general questions such as availability and high-level overviews, please check the online General FAQ.

Intel Media for Java Newsgroup

Collaborate and find answers with other developers using Intel Media for Java:

Bug Submission and Email Support

If you have a bug, recurring problem or a suggestion to report, please send a detailed description with corresponding code and/or error message/text to jmedia@mailbox.intel.com.

If you could not find an answer utilizing the preceding support methods send us an Email using the above address. Thank you for your feedback!

Part III. Installation

Please refer to Java Media Framework package page for information on system requirements, and downloading and installing Java Media Framework.

If JMF has already been installed, you must uninstall the old version before installing a newer version. Refer to the Uninstall section for instructions.

The JMF SDK and Runtimes do not contain a Java compiler. If you are going to create Java applets and do not have Java development tools, you can obtain the Sun Java Developer's Kit from: http://www.javasoft.com/java.sun.com/products/JDK/index.html.

Part IV. Uninstall

Uninstall Java Media Framework by using the Windows* 95 or Windows NT* Uninstall utility. From the Control Panel, choose the Add/Remove Program. To uninstall any component, highlight it and push the Add/Remove button.

To uninstall the Java Media Framework SDK, uninstall the following components:

  • Intel Java Media Framework SDK
  • Intel Java Media Framework IE Runtime
  • Intel Java Media Framework Netscape Runtime

If you have installed only the Internet Explorer Runtime, uninstall the Intel Java Media Framework IE Runtime component.

If you have installed only the Netscape Navigator Runtime, uninstall the Intel Java Media Framework Netscape Runtime component.

Note to Windows 95 users: The uninstall program will not edit the CLASSPATH variable in your autoexec.bat file. To uninstall, edit autoexec.bat and remove the C:\Program Files\intel\java\classes and C:\Program Files\intel\java\classes\media.zip arguments in the CLASSPATH variable.

Part V. Differences Between Java Media Framework Beta 1.3.0 and Java Media Player Specification Version 0.95

The following list describes areas of the Java Media Player Specification that are not supported in Java Media Framework Beta 1.3.0, but will be in subsequent releases:

  1. The addController() and removeController() methods of the Player class are not implemented. These methods allow multiple Controllers to be placed under the control of a single Player.
  2. The java.media.protocol and java.media.content packages are not yet implemented. These support packages are not intended for the use of programmers at the application level.

The following section describes behavior which is not explicitly defined by the Java Media Player Specification, or which may be unexpected:

  1. The gainControl object controls the Wave device in the Windows 95 and Windows NT volume mixer.
  2. Only one Player can access the audio device at a time. Inability to access the audio device is not considered an error, and ResourceUnavailableEvent is not sent when the audio device is unavailable. If the audio device is unavailable, the Player behaves as if the media clip being presented contains no audio.
  3. The ability to set a Player to another's reference time base is supported, provided that the new reference time base is obtained from another Player by this implementation. Any attempt to call setTimeBase() with a reference time base obtained from a user-supplied TimeBase implementation will result in an IncompatibleTimeBaseException being thrown.

The following section describes behavior which is incompatible with the Java Media Player Specification, but that will be fixed in subsequent releases:

  1. TransitionEvents are sent only for those state transitions which are represented by subclasses of TransitionEvent; the Java Media Player Specification requires that events be sent to mark all state changes.
    For example, the Java Media Player Specification specifies that two state transition events should be sent as the player moves from the Unrealized state through the Realizing state and finally into the Realized state.
    This implementation sends one RealizeCompleteEvent to denote the transition to the Realized state; it does not send a TransitionEvent to mark the transition to the Realizing state.
  2. getControls() does not return a CachingControl object, even though this implementation otherwise fully supports the CachingControl interface. The CachingControl object must be obtained directly from the CachingControlEvent as described in the Java Media Player Specification.

Part VI. Known Problems

A list of known problems for the Java Media Framework package are available here.

 

This page was last updated on Feb 12th, 1997.

Legal Stuff

Free Web Hosting