The Mobile Media API (MMAPI) is an API specification for the Java ME platform CDC and CLDC devices such as mobile phones. Depending on how it is implemented, the APIs allow applications to play and record sounds and video, and to capture still images. MMAPI was developed under the Java Community Process as JSR 135.

Programming concepts

The Multimedia Java API is based around four main types of classes in the package—the , the , the and various types of. Java ME programmers wishing to use JSR 135 would first make use of the static methods of the class. Although there are other methods such as, the main method used is. This takes either a URI or an, and a MIME type. In most cases, URIs are used. Common URI protocols used include: The MIME type is optional, and is inferred from the data passed in if not supplied. The method returns an implementation of the interface (even if you use a capture: protocol URI). This has core methods that are applicable to all players, such as starting and stopping the media, and requesting that it loop. You can also to an object implementing the interface, which will receive various events related to the clip (starting, stopping, media finishing, etc.) classes also have a method that returns an implementation of a particular. A handles any optional APIs which are not applicable to all media types. Any given may or may not be able to supply an implementation of any given. (Typically, the returned is actually the itself, but this is not guaranteed to be the case.) The set of controls implemented by a is not limited; however, some standard ones are defined in the package by the JSR: (Others may be defined in JSR 234 (Advanced Multimedia Supplements). A subset of JSR 135 is defined in JSR 118 (MIDP 2.0).

Player lifecycle

Regardless of the protocol or media type involved, the moves through the same discrete states during its lifecycle. These states are listed in table below

Implementations

As with most Java ME specifications, implementations differ despite the best efforts of the specification authors to ensure consistency. Two obvious areas for differences are in the controls supported, and in the acceptable URI types in the first place. More obscure areas are whether mixing is supported; many games would like to play a MIDI music track and layer PCM sound effects on top. Another source of extreme variance is in performance. For example, if an HTTP clip is requested, at what point does the clip get downloaded? The specification recognises this by providing two methods that can be called in advance of actually playing: and. Depending on the implementation, these may do some of the work of getting the clip into a playable state, thus making it quicker to actually play the clip when it is needed. Some implementations are sophisticated enough to actually stream a clip on request whilst it is being played. Symbian OS contains a very complete implementation of JSR 135, but even this is highly dependent on the underlying multimedia capabilities of the device, and some device manufacturers may choose not to expose the more obscure parts of Java ME such as recording. Implementation consistency is ensured by forcing all implementations to pass the Java Technology Compatibility Kit (TCK). This ensures that each supported URI schema, MIME type and Control is tested, but does not test every permutation of these optional parts.

Code example