Media Playback//媒体播放

翻译 2013年12月03日 18:37:10

Media Playback//媒体播放

The Android multimedia framework includes support for playing variety of common media types, so that you can easily integrate audio, video and 
images into your applications. You can play audio or video from media files stored in your application's resources (raw resources), from 
standalone files in the filesystem, or from a data stream arriving over a network connection, all using MediaPlayer APIs.
//安卓的多媒体框架包括支持播放各种常见的媒体类型,所以你可以很容易地整合音频,视频和图片在你的应用里面。你可以播放音频或者视频从储藏在你的应用的资源(raw resources)里的媒体文件,来自与独立文件系统中的文件,或者来自于通过网络连接获取的数据流,都使用MediaPlayer APIS.
This document shows you how to write a media-playing application that interacts with the user and the system in order to obtain good performance and a pleasant user experience.
Note: You can play back the audio data only to the standard output device. Currently, that is the mobile device speaker or a Bluetooth headset. 
You cannot play sound files in the conversation audio during a call.

The Basics//基础知识

The following classes are used to play sound and video in the Android framework:
This class is the primary API for playing sound and video.
This class manages audio sources and audio output on a device.

Manifest Declarations//清单声明

Before starting development on your application using MediaPlayer, make sure your manifest has the appropriate declarations to allow use of related features.
Internet Permission - If you are using MediaPlayer to stream network-based content, your application must request network access.
<uses-permission android:name="android.permission.INTERNET" />
Wake Lock Permission- If your player application needs to keep the screen from dimming or the processor from sleeping, or uses the MediaPlayer.setScreenOnWhilePlaying() or MediaPlayer.setWakeMode() methods, you must request this permission.
<uses-permission android:name="android.permission.WAKE_LOCK" />

Using MediaPlayer//使用MediaPlayer

One of the most important components of the media framework is the MediaPlayer class. An object of this class can fetch, decode, and play both audio and video with minimal setup. It supports several different media sources such as:
1)Local resources//本地资源
2)Internal URIs, such as one you might obtain from a Content Resolver//网络URIs,例如你可以从Content Resolver里面获得一个
3)External URLs (streaming)//外部的URLs(流)
For a list of media formats that Android supports, see the Android Supported Media Formats document.
//android支持的多媒体格式,参见Android Supported Media Formats文档。
Here is an example of how to play audio that's available as a local raw resource (saved in your application's res/raw/ directory):
//这里是一个例子,这个例子是如何播放本地可用的raw资源(保存在你应用的res/raw/ 目录下)的音频:
MediaPlayer mediaPlayer = MediaPlayer.create(context, R.raw.sound_file_1);
mediaPlayer.start(); // no need to call prepare(); create() does that for you//不需要调用prepare(),create()已经为你调用了
In this case, a "raw" resource is a file that the system does not try to parse in any particular way. However, the content of this resource should not be raw audio. It should be a properly encoded and formatted media file in one of the supported formats.
//在这种情况下,一个"raw" 资源是一个文件,系统不会以任何特别的方式去解析的文件。但是这个资源的内容不能是一个未加工的音频。它应当被恰当地编码并且是一种被支持的媒体格式。
And here is how you might play from a URI available locally in the system (that you obtained through a Content Resolver, for instance):
//这里是如何让播放存在系统的本地可用的URI(例如,你从一个Content Resolver里面得到)
Uri myUri = ....; // initialize Uri here
MediaPlayer mediaPlayer = new MediaPlayer();
mediaPlayer.setDataSource(getApplicationContext(), myUri);
Playing from a remote URL via HTTP streaming looks like this:
//通过一个HTTP 流从一个远程的URL播放像这样:
String url = "http://........"; // your URL here
MediaPlayer mediaPlayer = new MediaPlayer();
mediaPlayer.prepare(); // might take long! (for buffering, etc)
Note: If you're passing a URL to stream an online media file, the file must be capable of progressive download.
Caution: You must either catch or pass IllegalArgumentException and IOException when usingsetDataSource(), because the file you are referencing might not exist.

Asynchronous Preparation//异步准备

Using MediaPlayer can be straightforward in principle.However, it's important to keep in mind that a few more things are necessary to integrate it correctly with a typical Android application. For example, the call to prepare() can take a long time to execute, because it might involve fetching and decoding media data. So, as is the case with any method that may take long to execute, you should never call it from your application's UI thread. Doing that will cause the UI to hang until the method returns, which is a very bad user experience and can cause an ANR (Application Not Responding) error. Even if you expect your resource to load quickly, remember that anything that takes more than a tenth of a second to respond in the UI will cause a noticeable pause and will give the user the impression that your application is slow.


To avoid hanging your UI thread, spawn another thread to prepare the MediaPlayer and notify the main thread when done. However, while you could write the threading logic yourself, this pattern is so common when using MediaPlayer that the framework supplies a convenient way to accomplish this task by using the prepareAsync()method. This method starts preparing the media in the background and returns immediately. When the media is done preparing, the onPrepared() method of the MediaPlayer.OnPreparedListener, configured through setOnPreparedListener() is called.


Managing State//状态管理

Another aspect of a MediaPlayer that you should keep in mind is that it's state-based. That is, the MediaPlayer has an internal state that you must always be aware of when writing your code, because certain operations are only valid when then player is in specific states. If you perform an operation while in the wrong state, the system may throw an exception or cause other undesireable behaviors.

The documentation in the MediaPlayer class shows a complete state diagram, that clarifies which methods move the MediaPlayer from one state to another. For example, when you create a new MediaPlayer, it is in the Idle state. At that point, you should initialize it by calling setDataSource(), bringing it to the Initialized state. After that, you have to prepare it using either the prepare() or prepareAsync() method. When the MediaPlayer is done preparing, it will then enter the Prepared state, which means you can call start() to make it play the media. At that point, as the diagram illustrates, you can move between the StartedPaused and PlaybackCompleted states by calling such methods as start()pause(), and seekTo(), amongst others. When you call stop(), however, notice that you cannot call start() again until you prepare the MediaPlayer again.
Always keep the state diagram in mind when writing code that interacts with a MediaPlayer object, because calling its methods from the wrong state is a common cause of bugs.

Releasing the MediaPlayer//释放MediaPlayer

MediaPlayer can consume valuable system resources. Therefore, you should always take extra precautions to make sure you are not hanging on to a MediaPlayer instance longer than necessary. When you are done with it, you should always call release() to make sure any system resources allocated to it are properly released. For example, if you are using a MediaPlayer and your activity receives a call to onStop(), you must release theMediaPlayer, because it makes little sense to hold on to it while your activity is not interacting with the user (unless you are playing media in the background, which is discussed in the next section). When your activity is resumed or restarted, of course, you need to create a new MediaPlayer and prepare it again before resuming playback.
Here's how you should release and then nullify your MediaPlayer:
mediaPlayer = null;
As an example, consider the problems that could happen if you forgot to release the MediaPlayer when your activity is stopped, but create a new one when the activity starts again. As you may know, when the user changes the screen orientation (or changes the device configuration in another way), the system handles that by restarting the activity (by default), so you might quickly consume all of the system resources as the user rotates the device back and forth between portrait and landscape, because at each orientation change, you create a newMediaPlayer that you never release. (For more information about runtime restarts, see Handling Runtime Changes.)
//作为一个例子,考虑可能发生的这样的问题,当你的activity已经停止了,但你忘记了释放MediaPlayer,当这个Activity再一次开始时会创建一个新的MediaPlayer.正如你可能知道的,当用户改变屏幕的方向(或者以其它方法改变设备的配置),系统的处理是重新开始activity(默认),所以当用户在竖屏和横屏之间向前和向后旋转设备时,你可能会很快地消耗系统所有的资源。因为任何一次方向的改变,你都建立了一个你从没有释放的MediaPlayer.(更多的关于运行时重新启动的信息,参见Handling Runtime Changes.)
You may be wondering what happens if you want to continue playing "background media" even when the user leaves your activity, much in the same way that the built-in Music application behaves. In this case, what you need is a MediaPlayer controlled by a Service, as discussed in Using a Service with MediaPlayer.
//你可能想知道,当用户已经离开了你的activity,而你想继续播放"后台的media"会发生什么,就像系统内置的音乐应用所表现的行为那样。在这种情况下,你需要的是通过一个服务控制MediaPlayer,就像在Using a Service with MediaPlayer讨论的那样。

Using a Service with MediaPlayer//和MediaPlayer在一起使用一个


If you want your media to play in the background even when your application is not onscreen—that is, you want it to continue playing while the user is interacting with other applications—then you must start a Service and control the MediaPlayer instance from there. You should be careful about this setup, because the user and the system have expectations about how an application running a background service should interact with the rest of the system. If your application does not fulfil those expectations, the user may have a bad experience. This section describes the main issues that you should be aware of and offers suggestions about how to approach them.

Running asynchronously//异步的运行

First of all, like an Activity, all work in a Service is done in a single thread by default—in fact, if you're running an activity and a service from the same application, they use the same thread (the "main thread") by default. Therefore, services need to process incoming intents quickly and never perform lengthy computations when responding to them. If any heavy work or blocking calls are expected, you must do those tasks asynchronously: either from another thread you implement yourself, or using the framework's many facilities for asynchronous processing.
For instance, when using a MediaPlayer from your main thread, you should call prepareAsync() rather than prepare(), and implement a MediaPlayer.OnPreparedListener in order to be notified when the preparation is complete and you can start playing. For example:
public class MyService extends Service implements MediaPlayer.OnPreparedListener {
    private static final ACTION_PLAY = "com.example.action.PLAY";
    MediaPlayer mMediaPlayer = null;

    public int onStartCommand(Intent intent, int flags, int startId) {
        if (intent.getAction().equals(ACTION_PLAY)) {
            mMediaPlayer = ... // initialize it here
            mMediaPlayer.prepareAsync(); // prepare async to not block main thread

    /** Called when MediaPlayer is ready */
    public void onPrepared(MediaPlayer player) {

Handling asynchronous errors//处理异步的错误

On synchronous operations, errors would normally be signaled with an exception or an error code, but whenever you use asynchronous resources, you should make sure your application is notified of errors appropriately. In the case of a MediaPlayer, you can accomplish this by implementing a MediaPlayer.OnErrorListener and setting it in your MediaPlayer instance:
public class MyService extends Service implements MediaPlayer.OnErrorListener {
    MediaPlayer mMediaPlayer;

    public void initMediaPlayer() {
        // ...initialize the MediaPlayer here...


    public boolean onError(MediaPlayer mp, int what, int extra) {
        // ... react appropriately ...
        // The MediaPlayer has moved to the Error state, must be reset!
It's important to remember that when an error occurs, the MediaPlayer moves to the Error state (see the documentation for the MediaPlayer class for the full state diagram) and you must reset it before you can use it again.

Using wake locks//使用唤醒锁

When designing applications that play media in the background, the device may go to sleep while your service is running. Because the Android system tries to conserve battery while the device is sleeping, the system tries to shut off any of the phone's features that are not necessary, including the CPU and the WiFi hardware. However, if your service is playing or streaming music, you want to prevent the system from interfering with your playback.
In order to ensure that your service continues to run under those conditions, you have to use "wake locks." A wake lock is a way to signal to the system that your application is using some feature that should stay available even if the phone is idle.
//为了确保你的服务在这些情况下能继续运行,你必须使用"wake locks".一个wake lock是一个方法----发信号告诉系统你的应用正在使用的功能应当保持在可用的状态即使电脑在闲置的状态下。
Notice: You should always use wake locks sparingly and hold them only for as long as truly necessary, because they significantly reduce the battery life of the device.
//注意:你应当少使用wake lock并且只在真正必需的时候保持它们,因为它们会显著地减少设备电池的寿命。
To ensure that the CPU continues running while your MediaPlayer is playing, call the setWakeMode() method when initializing your MediaPlayer. Once you do, the MediaPlayer holds the specified lock while playing and releases the lock when paused or stopped:
mMediaPlayer = new MediaPlayer();
// ... other initialization here ...
mMediaPlayer.setWakeMode(getApplicationContext(), PowerManager.PARTIAL_WAKE_LOCK);
However, the wake lock acquired in this example guarantees only that the CPU remains awake. If you are streaming media over the network and you are using Wi-Fi, you probably want to hold a WifiLock as well, which you must acquire and release manually. So, when you start preparing the MediaPlayer with the remote URL, you should create and acquire the Wi-Fi lock. For example:
WifiLock wifiLock = ((WifiManager) getSystemService(Context.WIFI_SERVICE))
    .createWifiLock(WifiManager.WIFI_MODE_FULL, "mylock");

When you pause or stop your media, or when you no longer need the network, you should release the lock:

Running as a foreground service//作为前台服务运行

Services are often used for performing background tasks, such as fetching emails, synchronizing data, downloading content, amongst other possibilities. In these cases, the user is not actively aware of the service's execution, and probably wouldn't even notice if some of these services were interrupted and later restarted.
But consider the case of a service that is playing music. Clearly this is a service that the user is actively aware of and the experience would be severely affected by any interruptions. Additionally, it's a service that the user will likely wish to interact with during its execution. In this case, the service should run as a "foreground service." A foreground service holds a higher level of importance within the system—the system will almost never kill the service, because it is of immediate importance to the user. When running in the foreground, the service also must provide a status bar notification to ensure that users are aware of the running service and allow them to open an activity that can interact with the service.
In order to turn your service into a foreground service, you must create a Notification for the status bar and call startForeground() from the Service. For example:
String songName;
// assign the song name to songName
PendingIntent pi = PendingIntent.getActivity(getApplicationContext(), 0,
                new Intent(getApplicationContext(), MainActivity.class),
Notification notification = new Notification();
notification.tickerText = text;
notification.icon = R.drawable.play0;
notification.flags |= Notification.FLAG_ONGOING_EVENT;
notification.setLatestEventInfo(getApplicationContext(), "MusicPlayerSample",
                "Playing: " + songName, pi);
startForeground(NOTIFICATION_ID, notification);
While your service is running in the foreground, the notification you configured is visible in the notification area of the device. If the user selects the notification, the system invokes the PendingIntent you supplied. In the example above, it opens an activity (MainActivity).
Figure 1 shows how your notification appears to the user:

Figure 1. 
Screenshots of a foreground service's notification, showing the notification icon in the status bar (left) and the expanded view (right).
You should only hold on to the "foreground service" status while your service is actually performing something the user is actively aware of. Once that is no longer true, you should release it by calling stopForeground():
For more information, see the documentation about Services and Status Bar Notifications.
//有关更多信息,请参见关于Services和Status Bar Notification的文档。

Handling audio focus//处理音频焦点

Even though only one activity can run at any given time, Android is a multi-tasking environment. This poses a particular challenge to applications that use audio, because there is only one audio output and there may be several media services competing for its use. Before Android 2.2, there was no built-in mechanism to address this issue, which could in some cases lead to a bad user experience. For example, when a user is listening to music and another application needs to notify the user of something very important, the user might not hear the notification tone due to the loud music. Starting with Android 2.2, the platform offers a way for applications to negotiate their use of the device's audio output. This mechanism is called Audio Focus.
//虽然仅有的一个activity可以在给定的任何时间内运行,安卓是一个多任务的环境。这对使用音频的应用构成了特别的挑战,因为仅有一个音频输出但是可能有几个互相竞争的使用者。在安卓2.2之前,没有针对这个问题的内置的机制,在某些情况下它导致了很差的用户体验。例如,当一个用户正在听音乐,其它的应用需要通知用户一些非常重要的事,因为大声的音乐用户可能没有听到通知的声音。从安卓2.2开始,平台提供了一种方法越过设备音频输出的使用。这个机制是叫做Audio Focus.
When your application needs to output audio such as music or a notification, you should always request audio focus. Once it has focus, it can use the sound output freely, but it should always listen for focus changes. If it is notified that it has lost the audio focus, it should immediately either kill the audio or lower it to a quiet level (known as "ducking"—there is a flag that indicates which one is appropriate) and only resume loud playback after it receives focus again.
Audio Focus is cooperative in nature. That is, applications are expected (and highly encouraged) to comply with the audio focus guidelines, but the rules are not enforced by the system. If an application wants to play loud music even after losing audio focus, nothing in the system will prevent that. However, the user is more likely to have a bad experience and will be more likely to uninstall the misbehaving application.
To request audio focus, you must call requestAudioFocus() from the AudioManager, as the example below demonstrates:
AudioManager audioManager = (AudioManager) getSystemService(Context.AUDIO_SERVICE);
int result = audioManager.requestAudioFocus(this, AudioManager.STREAM_MUSIC,

if (result != AudioManager.AUDIOFOCUS_REQUEST_GRANTED) {
    // could not get audio focus.
The first parameter to requestAudioFocus() is an AudioManager.OnAudioFocusChangeListener, whose onAudioFocusChange() method is called whenever there is a change in audio focus. Therefore, you should also implement this interface on your service and activities. For example:
class MyService extends Service
                implements AudioManager.OnAudioFocusChangeListener {
    // ....
    public void onAudioFocusChange(int focusChange) {
        // Do something based on focus change...
The focusChange parameter tells you how the audio focus has changed, and can be one of the following values (they are all constants defined in AudioManager):
1)AUDIOFOCUS_GAIN: You have gained the audio focus.//你已经得到了音频的焦点
2)AUDIOFOCUS_LOSS: You have lost the audio focus for a presumably long time. You must stop all audio playback. Because you should expect not to have focus back for a long time, this would be a good place to clean up your resources as much as possible. For example, you should release the MediaPlayer.
3)AUDIOFOCUS_LOSS_TRANSIENT:You have temporarily lost audio focus, but should receive it back shortly. You must stop all audio playback, but you can keep your resources because you will probably get focus back shortly.    transient:短暂的
4)AUDIOFOCUS_LOSS_TRANSIENT_CAN_DUCK:You have temporarily lost audio focus, but you are allowed to continue to play audio quietly (at a low volume) instead of killing audio completely.
Here is an example implementation:
public void onAudioFocusChange(int focusChange) {
    switch (focusChange) {
        case AudioManager.AUDIOFOCUS_GAIN:
            // resume playback
            if (mMediaPlayer == null) initMediaPlayer();
            else if (!mMediaPlayer.isPlaying()) mMediaPlayer.start();
            mMediaPlayer.setVolume(1.0f, 1.0f);

        case AudioManager.AUDIOFOCUS_LOSS:
            // Lost focus for an unbounded amount of time: stop playback and release media player
            if (mMediaPlayer.isPlaying()) mMediaPlayer.stop();
            mMediaPlayer = null;

        case AudioManager.AUDIOFOCUS_LOSS_TRANSIENT:
            // Lost focus for a short time, but we have to stop
            // playback. We don't release the media player because playback
            // is likely to resume
            if (mMediaPlayer.isPlaying()) mMediaPlayer.pause();

            // Lost focus for a short time, but it's ok to keep playing
            // at an attenuated level
            if (mMediaPlayer.isPlaying()) mMediaPlayer.setVolume(0.1f, 0.1f);
Keep in mind that the audio focus APIs are available only with API level 8 (Android 2.2) and above, so if you want to support previous versions of Android, you should adopt a backward compatibility strategy that allows you to use this feature if available, and fall back seamlessly if not.
//记住音频焦点的APIs只在API 8(安卓2.2)以及更高的版本里可用,所以如果你想支持安卓以前的版本,你应该采取向后兼容的策略,如果可用的话就使用这一功能,如果不可以就无缝地后退。
You can achieve backward compatibility either by calling the audio focus methods by reflection or by implementing all the audio focus features in a separate class (say, AudioFocusHelper). Here is an example of such a class:
//你可以通过反射调用audio focus的方法,或者在一个分离的类(叫做,AudioFocusHelper)里面实现所有的音频焦点功能的方法获得向后的兼容性。这里是这样的一个类的例子:
public class AudioFocusHelper implements AudioManager.OnAudioFocusChangeListener {
    AudioManager mAudioManager;

    // other fields here, you'll probably hold a reference to an interface
    // that you can use to communicate the focus changes to your Service

    public AudioFocusHelper(Context ctx, /* other arguments here */) {
        mAudioManager = (AudioManager) mContext.getSystemService(Context.AUDIO_SERVICE);
        // ...

    public boolean requestFocus() {
        return AudioManager.AUDIOFOCUS_REQUEST_GRANTED ==
            mAudioManager.requestAudioFocus(mContext, AudioManager.STREAM_MUSIC,

    public boolean abandonFocus() {
        return AudioManager.AUDIOFOCUS_REQUEST_GRANTED ==

    public void onAudioFocusChange(int focusChange) {
        // let your service know about the focus change
You can create an instance of AudioFocusHelper class only if you detect that the system is running API level 8 or above. For example:
//你可以建立一个AudioFocusHelper类的实例如果你发觉你的系统运行在API 8或者以上时。例如:
if (android.os.Build.VERSION.SDK_INT >= 8) {
    mAudioFocusHelper = new AudioFocusHelper(getApplicationContext(), this);
} else {
    mAudioFocusHelper = null;

Performing cleanup//执行清理

As mentioned earlier, a MediaPlayer object can consume a significant amount of system resources, so you should keep it only for as long as you need and call release() when you are done with it. It's important to call this cleanup method explicitly rather than rely on system garbage collection because it might take some time before the garbage collector reclaims the MediaPlayer, as it's only sensitive to memory needs and not to shortage of other media-related resources. So, in the case when you're using a service, you should always override the onDestroy() method to make sure you are releasing the MediaPlayer:

Media PlayBack 媒体的后台播放

Media PlayBackMedia 的后台播放时Andorid程序的常见功能,主要运用到一下两个类: MediaPlayer This class is the primary API for ...
  • u010865433
  • u010865433
  • 2015年09月03日 10:12
  • 335


什么是媒体    所谓媒体也就是媒介,在CSS中代指各种设备。他们有很多类型(media type),如下: 类型 描述 all 所有设备 braille 盲文 emb...
  • mpdemp
  • mpdemp
  • 2017年04月20日 18:01
  • 1633


一、设置meta标签 在使用媒体查询media之前我们需要先设置meta标签,对设备的缩放等参数进行设定。 参数解释: width=device-width   宽度等于当前设备宽...
  • NineTeen19
  • NineTeen19
  • 2015年10月26日 14:35
  • 6879


准备工作1:设置Meta标签 首先我们在使用Media的时候需要先设置下面这段代码,来兼容移动设备的展示效果: html 代码1 这段代码的几个参数解释: width = device-width:...
  • garvisjack
  • garvisjack
  • 2017年04月27日 14:32
  • 740


Media Queries这功能是非常强大的,他可以让你定制不同的分辨率和设备,并在不改变内容的情况下,让你制作的web页面在不同的分辨率和设备下都能显示正常,并且不会因此而丢失样式。...
  • boyit0
  • boyit0
  • 2016年09月08日 10:22
  • 2079

响应式布局 媒体查询 media query的用法

产生响应布局是因为设备的不同,最终还是分辨率,设备显示器大小不同导致的,所以在做开发时要先了解开发对象的屏幕尺寸信息,可以参考这个网站:响应式开发设备屏幕分辨率查询网址 为了解决移动端屏幕分...
  • MajorMayer
  • MajorMayer
  • 2016年01月28日 16:21
  • 2420


引言一直想对CSS3的媒体查询和Responsive进行一下记录和总结,今天拿出点时间来做一下。媒体查询的历史随着浏览器终端的多样化,无法保证一个网页在不同的设备上呈现出想同的结果,所以Media Q...
  • lecepin
  • lecepin
  • 2016年11月22日 21:04
  • 3043


官网地址: @include-media@include-media的口号是写简单、优雅和可维护的Sass媒介查询。include-media是什么?include-media 是一个Sass库,使用...
  • u014695532
  • u014695532
  • 2017年03月05日 20:24
  • 573


关于bootstrap响应式布局,国内外名气满满的前端样式布局框架。3.0之前版本都采用less动态css预处理语言,实现机制是通过@media媒介查询来达到样式控制。 例如:@media scre...
  • wujimiao
  • wujimiao
  • 2017年04月12日 23:37
  • 739

媒体查询 @Media

媒体查询: 媒体查询可以让我们根据设备显示器的特性(如视口宽度、屏幕比例、设备方向:横向或纵向)为其设定CSS样式,媒体查询由媒体类型和一个或多个检测媒体特性的条件表达式组成。媒体查询中可用于检测的...
  • ltaihyy
  • ltaihyy
  • 2016年09月19日 14:04
  • 1179
您举报文章:Media Playback//媒体播放