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

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.

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 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.

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.

Most players use DirectShow for playback. DirectShow is a system that uses multiple DirectShow filters as building blocks to construct what is called a DirectShow graph. A file is a root of this graph and the audio and video renderers are the leaves of the graph. During playback data flows from the root to the leaves. Each filter in the graph performs a subtask of the whole process. Typical elements in the graph are a source filter, also called a splitter, and decoders for the audio and video.

Ok, so I forcefully turned it on but when it activates, my ‘plugin’-page in the admin section does not display any plugins anymore unless I manually delete the disclose secret folder with my FTP. Mmmmh, maybe this is not a problem of your plugin but maybe are other plugins or a script causing this. Fatal error: Maximum execution time of 30 seconds exceeded in /home/smithism/public_html/blog/wp-content/plugins/disclose-secret/pcre.

The MPEG-4 and H.264 codec options on the Video tab should only be used if you are planning to create a QuickTime movie containing video compressed in this format. In this case, you would choose either of these codecs on the Video tab and use QuickTime as the Output Format on the Output tab. The resulting file will have the extension MOV, as it will be a QuickTime movie, and the frame size will be the full frame size of the DVD.

Codecs are filters that need to be installed on your system in order to view specific video file types. They are necessary for video (and sometimes audio) playback. The following are a list of video codecs that you can download directly on our website:

No. The developer chemistry oxidizes fairly rapidly whether in an automatic processor or in hand tanks. Again monthly cleaning along with a chemistry change is in order.

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

AVIedit lets you enumerate and view both the video and audio codecs installed. Select Options|ICM menu item to list video codecs, or use Options|ACM menu item to list audio codecs.

We stay away from recommending specific settings as it is pretty subjective, and all of the elements in the Save Movie dialog come from QuickTime, not Snapz Pro X 2, and therefore are a bit beyond the scope of these FAQs. That said, the H.264 codec is Apple's standard. It is the codec used for trailers on the Apple site and does a great job of maintaining video quality and keeping file sizes to a minimum.

WinImages uses Windows 32-bit CODEC interface. WinImages can not use 16-bit CODECs from the Windows 3.1 era. Using Windows 32-bit CODEC mechanism means that Windows actually handles the CODECs themselves; they are not handled by WinImages. WinImages just hands basic images back and forth between it and Windows one after another, until the entire animated image stream is complete.

RAW codecs are available direct from camera manufacturers' websites, and may also be included in software provided with future cameras. Nikon has released version 1.0 of its codec, which can be found on the Nikon Imaging website. For information about the availability of codecs for other RAW file types, please see the following links: Important note to users of the Nikon RAW Codec for Windows: Microsoft has received reports of compatibility issues with Nikon NEF files after installing version 1.

JMF source is made available under the Sun Community Source Licensing (SCSL) program; the following summarizes how it can be used. SCSL allows for the release of source code for non-commercial, evaluation and/or research use.