Currently the JMF/RTSP stack can only be accessed through the Manager.createPlayer() interface which supports the playback case only. There is no public interface that would be necessary for a server to communicate with the RTSP stack.

Note the JMF 2.0 API was updated slightly to include improved RTP interfaces, but remains backward compatible with the old API. It is still known as the JMF 2.0 API, but is dated 10-March-2001. The JMF 2.1.1 reference implementation is based on this new API.

Yes. There are two versions of H.263 payload header defined: RFC 2190 (payload type 34) and the new RFC 2429 (dynamic payload type 96-127). The QuickTime server uses the newer one and JMF used to support the older one. JMF 2.1.1 now supports both H.263 payload types.

For a complete set of formats, check out: http://java.sun.com/products/java-media/jmf/2.1.1/formats.html

There is an unsupported way to play audio CDs using the Windows Performance Pack version of JMF 2.1.1! Assuming your CD-ROM drive is mapped to E:, you can use the URL "file:/E:/Track01.cda", etc., to play the CD track.

Yes. You can use the SimplePlayerApplet that is included in the jmf.jar file or write your own. See SimplePlayerApplet.

Yes. JMF 2.1.1 has a new plugin architecture which allows you to add new codecs and effects to the framework. You can also create your own custom datasources and players to parse and render new media types which are not bundled with JMF 2.1.1 More information about this can be found in the JMF Programmer's Guide, available on the JMF web site at http://java.sun.com/products/java-media/jmf

Yes. JMF 2.1.1 provides capture functionality so you can capture from a recorded or live media source. On Solaris, SunVideo and SunVideo Plus cards are supported. On Windows, most video capture devices that have a VFW driver are supported. For a list of tested video capture devices, check out: http://java.sun.com/products/java-media/jmf/2.1.1/formats.html Video capture is not supported in the pure Java versions of JMF 2.1.

JMF 2.1.1 will run on Windows 95/98/NT 4.0/2000, Solaris/SPARC, and any Java Compatible platforms. The pure Java version of JMF 2.1.1 will now run on Apple's MRJ 2.1.4; however there are a/v syncronization problems since Apple added a 6 second audio buffer to that MRJ.

JMF 2.1.1 runs on Java Compatible platforms running JDK 1.1 or greater. For complete Y2K compliance, you should use JDK 1.1.6 or greater.

By default (for security reasons), JMF 2.1.1 does not allow capture from an applet. The user can turn this on by using JMFRegistry. Run "java JMFRegistry", select the UserSettings tab and check "Allow Capture From Applets". If the browser's security permits loading native libraries, then you will now be able to capture audio/video from an applet.

By default (for security reasons), JMF 2.1.1 does not allow files to be saved from an applet. The user can turn this on by using JMFRegistry. Run "java JMFRegistry", select the UserSettings tab and check "Allow File Writing for Applets". If the browser's security permits loading native libraries, then you will now be able to save fies from an applet.

JMF supports both transmission and reception of media over RTP for a variety of media formats. For a list of the default formats supported, check: http://java.sun.com/products/java-media/jmf/2.1.1/support-rtp.html It also fully supports RTCP. Besides, JMF implements the "RTP Profile for Audio and Video Conferences with Minamal Control", RTP/AVP. The front end GUI application, JMStudio can be used as a standalone application to transmit and receive RTP streams.

JMF is an open architecture with pluggable components such as renderers, codecs etc. In order to add RTP-Text capabilities you would need to add a new format (payload) and provide the appropriate data packetizer and depacketizer, codec and renderer. Yes.

You can start looking at the solutions on our website at: http://java.sun.com/products/java-media/jmf/2.1.1/solutions/index.html There you'll find various sample programs that highlight different aspects of JMF. For example for RTP transmission check out AVTransmit.

RTP is the Real-time Transport Protocol. Here is an excerpt from the RTP specification: "RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulated data, over multicast or unicast network services. RTP does not address resource reservation and does not guarantee quality-of-service for real-time services.

JMF is not properly installed on your machine or is not available on the website that contains the applet in question. Run the JMF diagnostics applet to see if JMF is installed properly: http://java.sun.com/products/java-media/jmf/2.1.1/jmfdiagnostics.html Your browser does not have a JDK 1.1.x compatible Java VM. Upgrade to a more recent version of the browser. The applet might have thrown a security exception - check the Java Console pertaining to your browser.

Your eSignal connection takes place via several different servers and they are required for some of the features within the application such as charts, Market Trader, Zone Trader, Conditional Systems, Streaming Quotes etc. to work properly.

A stream is a way of thinking about digital information for which there may be no ending point. The most conventional form of digital information is the file. Files always have a beginning and an end, but streams may or may not, and therefore software which uses streams must not require finding the end of the file in order to process it. Streams are usually delivered in packets which are self-contained, and usually allow seeking (i.e. fast forward) for further points in the streams.

Check the ATN webcasting start page. It will walk you through detailed instructions for adjusting your system settings (and for downloading a viewer, if need be) to view the lectures on your computer. I do mean detailed -- it will take anywhere from 10 to 30 minutes, and you may want a pad to jot down some of the settings, since you may have to quit programs and restart your computer a few times to get everything just so. The crucial slides will be available on a lecture handout (in .

If you know of a book that is not on this list, please let us know so we can add it. Fill out the JMF Feedback form

JMF 2.1.1 maintains a registry of available plugins, package prefixes and other settings in a file called jmf.properties. This is a binary file and should only be modified using the provided JMFRegistry application. This application is a part of the JMF 2.1.1 jmf.jar file and can be run as "java JMFRegistry". It requires that you have Swing-1.1 in your CLASSPATH (or you can use JDK 1.2 or later).

On the JMF web site, there is a diagnostics page with an embedded JMF applet which will check to see if you have JMF installed correctly on your system. Check out: http://java.sun.com/products/java-media/jmf/2.1.1/jmfdiagnostics.html

The CS email servers support both POP and IMAP. All CS email servers require the SSL protocol for incoming email (usaully found in the advanced tab). Users should use their incoming email server as their outgoing SMTP server for machines located here in the department. For machines located outside the department (yes, your home is outside the department) users MUST use their ISP's SMTP server. If you are using Bruin Online your SMTP setting is 'mail.ucla.edu' - authentication is required.