1. Android4.0.1中默認定義了4個(gè)真正的Player,具體情況如下：
[cpp]
view plaincopystatic sp<MediaPlayerBase> createPlayer(player_type playerType, void* cookie,
notify_callback_f notifyFunc)
{
sp<MediaPlayerBase> p;
switch (playerType) {
case SONIVOX_PLAYER:
LOGV(" create MidiFile");
p = new MidiFile();
break;
case STAGEFRIGHT_PLAYER:
LOGV(" create StagefrightPlayer");
p = new StagefrightPlayer;
break;
case NU_PLAYER:
LOGV(" create NuPlayer");
p = new NuPlayerDriver;
break;
case TEST_PLAYER:
LOGV("Create Test Player stub");
p = new TestPlayerStub();
break;
default:
LOGE("Unknown player type: %d", playerType);
return NULL;
}
if (p != NULL) {
if (p->initCheck() == NO_ERROR) {
p->setNotifyCallback(cookie, notifyFunc);
} else {
p.clear();
}
}
if (p == NULL) {
LOGE("Failed to create player object");
}
return p;
}
2. 每個(gè)Player的專(zhuān)長(cháng)是什么呢？
Player TypeFeature Description
TEST_PLAYERurl以test:開(kāi)始的。如test:xxx
NU_PLAYERurl以http://或https://開(kāi)始的，且url以.m3u8結束或url中包含有m3u8字符串
SONIVOX_PLAYER處理url中擴展名為：.mid,.midi,.smf,.xmf,.imy,.rtttl,.rtx,.ota的媒體文件
STAGEFRIGHT_PLAYER它是一個(gè)大好人，前面三位不能處理的都交給它來(lái)處理，不知能力是否有如此強大
以上言論以代碼為證，獲取player type的代碼如下：
[cpp]
view plaincopyplayer_type getPlayerType(const char* url)
{
if (TestPlayerStub::canBeUsed(url)) {
return TEST_PLAYER;
}
if (!strncasecmp("http://", url, 7)
|| !strncasecmp("https://", url, 8)) {
size_t len = strlen(url);
if (len >= 5 && !strcasecmp(".m3u8", &url[len - 5])) {
return NU_PLAYER;
}
if (strstr(url,"m3u8")) {
return NU_PLAYER;
}
}
// use MidiFile for MIDI extensions
int lenURL = strlen(url);
for (int i = 0; i < NELEM(FILE_EXTS); ++i) {
int len = strlen(FILE_EXTS[i].extension);
int start = lenURL - len;
if (start > 0) {
if (!strncasecmp(url + start, FILE_EXTS[i].extension, len)) {
return FILE_EXTS[i].playertype;
}
}
}
return getDefaultPlayerType();
}
如果你想增加自己的player,以上兩個(gè)函數都需要修改。
現在對整個(gè)媒體系統基本上有一個(gè)清晰的框架了，就突發(fā)奇想，到底在StagefrightPlayer如何增加自己的硬件解碼呢? 很好奇，想一探究竟...
