OpenHarmony 3.2 Beta多媒体系列——音视频播放框架-六虎

一、简介

媒体子体系为开发者供给一套接口，方便开发者使用体系的媒体资源，首要包括音视频开发、相机开发、流媒体开发等模块。每个模块都供给给上层使用对应的接口，本文会对音视频开发中的音视频播映结构做一个具体的介绍。

二、目录

foundation/multimedia/media_standard

├── frameworks                        #结构代码
│   ├── js
│   │   ├── player
│   ├── native
│   │   ├── player                    #native完成
│   └── videodisplaymanager         #显现管理
│       ├── include
│       └── src
├── interfaces
│   ├── inner_api                     #内部接口
│   │   └── native
│   └── kits                          #外部JS接口
├── sa_profile                        #服务配置文件
└── services
    ├── engine                        #engine代码
    │   └── gstreamer
    ├── etc                           #服务配置文件
    ├── include                       #头文件
    └── services
        ├── sa_media                  #media服务
        │   ├── client                #media客户端
        │   ├── ipc                   #media ipc调用
        │   └── server                #media服务端
        ├── factory                   #engine工厂
        └── player                    #player服务
           ├── client                 #player客户端
           ├── ipc                    #player ipc调用
           └── server                 #player服务端

三、播映的整体流程

四、Native接口使用

OpenHarmony体系中，音视频播映经过N-API接口供给给上层JS调用，N-API相当所以JS和Native之间的桥梁，在OpenHarmony源码中，供给了C++直接调用的音视频播映比如，在foundation/multimedia/player_framework/test/nativedemo/player目录中。

void PlayerDemo::RunCase(const string &path)
{
    player_ = OHOS::Media::PlayerFactory::CreatePlayer();
    if (player_ == nullptr) {
        cout << "player_ is null" << endl;
        return;
    }
    RegisterTable();
    std::shared_ptr<PlayerCallbackDemo> cb = std::make_shared<PlayerCallbackDemo>();
    cb->SetBufferingOut(SelectBufferingOut());
    int32_t ret = player_->SetPlayerCallback(cb);
    if (ret != 0) {
        cout << "SetPlayerCallback fail" << endl;
    }
    if (SelectSource(path) != 0) {
        cout << "SetSource fail" << endl;
        return;
    }
    sptr<Surface> producerSurface = nullptr;
    producerSurface = GetVideoSurface();
    if (producerSurface != nullptr) {
        ret = player_->SetVideoSurface(producerSurface);
        if (ret != 0) {
            cout << "SetVideoSurface fail" << endl;
        }
    }
    SetVideoScaleType();
    if (SelectRendererMode() != 0) {
        cout << "set renderer info fail" << endl;
    }
    ret = player_->PrepareAsync();
    if (ret !=  0) {
        cout << "PrepareAsync fail" << endl;
        return;
    }
    cout << "Enter your step:" << endl;
    DoNext();
}

首要依据RunCase可以大致了解一下播映音视频的首要流程，创立播映器，设置播映源，设置回调办法（包括播映过程中的多种状况的回调），设置播映显现的Surface，这些准备工作做好之后，需求调用播映器的PrepareASync办法，这个办法完成后，播映状况会变成Prepared状况，这时就可以调用播映器的play接口，进行音视频的播映了。

RegisterTable()办法中，将字符串和对应的办法映射到Map中，这样后续的DoNext会依据输入的指令，来决议播映器具体的操作。

void PlayerDemo::DoNext()
{
    std::string cmd;
    while (std::getline(std::cin, cmd)) {
        auto iter = playerTable_.find(cmd);
        if (iter != playerTable_.end()) {
            auto func = iter->second;
            if (func() != 0) {
                cout << "Operation error" << endl;
            }
            if (cmd.find("stop") != std::string::npos && dataSrc_ != nullptr) {
                dataSrc_->Reset();
            }
            continue;
        } else if (cmd.find("quit") != std::string::npos || cmd == "q") {
            break;
        } else {
            DoCmd(cmd);
            continue;
        }
    }
}
void PlayerDemo::RegisterTable()
{
    (void)playerTable_.emplace("prepare", std::bind(&Player::Prepare, player_));
    (void)playerTable_.emplace("prepareasync", std::bind(&Player::PrepareAsync, player_));
    (void)playerTable_.emplace("", std::bind(&Player::Play, player_)); // ENTER -> play
    (void)playerTable_.emplace("play", std::bind(&Player::Play, player_));
    (void)playerTable_.emplace("pause", std::bind(&Player::Pause, player_));
    (void)playerTable_.emplace("stop", std::bind(&Player::Stop, player_));
    (void)playerTable_.emplace("reset", std::bind(&Player::Reset, player_));
    (void)playerTable_.emplace("release", std::bind(&Player::Release, player_));
    (void)playerTable_.emplace("isplaying", std::bind(&PlayerDemo::GetPlaying, this));
    (void)playerTable_.emplace("isloop", std::bind(&PlayerDemo::GetLooping, this));
    (void)playerTable_.emplace("speed", std::bind(&PlayerDemo::GetPlaybackSpeed, this));
}

以上的DoNext办法中中心的代码是func()的调用，这个func便是之前注册进Map中字符串对应的办法，在RegisterTable办法中将空字符串””和”play”对绑定为Player::Play办法，默许不输入指令参数时，是播映操作。

五、调用流程

本阶段首要针对媒体播映的结构层代码进行剖析，所以在流程中涉及到了IPC调用相关的客户端和服务端，代码暂且剖析到调用gstreamer引擎。首要Sample经过PlayerFactory创立了一个播映器实例（PlayerImpl目标），创立过程中调用Init函数。

int32_t PlayerImpl::Init()
{
    playerService_ = MediaServiceFactory::GetInstance().CreatePlayerService();
    CHECK_AND_RETURN_RET_LOG(playerService_ != nullptr, MSERR_UNKNOWN, "failed to create player service");
    return MSERR_OK;
}

MediaServiceFactory::GetInstance()回来的是MediaClient目标，所以CreateplayerService函数实际上是调用了MediaClient对应的办法。

std::shared_ptr<IPlayerService> MediaClient::CreatePlayerService()
{
    std::lock_guard<std::mutex> lock(mutex_);
    if (!IsAlived()) {
        MEDIA_LOGE("media service does not exist.");
        return nullptr;
    }
    sptr<IRemoteObject> object = mediaProxy_->GetSubSystemAbility(
        IStandardMediaService::MediaSystemAbility::MEDIA_PLAYER, listenerStub_->AsObject());
    CHECK_AND_RETURN_RET_LOG(object != nullptr, nullptr, "player proxy object is nullptr.");
    sptr<IStandardPlayerService> playerProxy = iface_cast<IStandardPlayerService>(object);
    CHECK_AND_RETURN_RET_LOG(playerProxy != nullptr, nullptr, "player proxy is nullptr.");
    std::shared_ptr<PlayerClient> player = PlayerClient::Create(playerProxy);
    CHECK_AND_RETURN_RET_LOG(player != nullptr, nullptr, "failed to create player client.");
    playerClientList_.push_back(player);
    return player;
}

这个办法中首要经过PlayerClient::Create(playerProxy)办法创立了PlayerClient实例，并且将该实例一层层向上传，终究传给了PlayerImpl的playerService_变量，后续关于播映器的操作，PlayerImpl都是经过调用PlayerClient实例完成的。

int32_t PlayerImpl::Play()
{
    CHECK_AND_RETURN_RET_LOG(playerService_ != nullptr, MSERR_INVALID_OPERATION, "player service does not exist..");
    MEDIA_LOGW("KPI-TRACE: PlayerImpl Play in");
    return playerService_->Play();
}
int32_t PlayerImpl::Prepare()
{
    CHECK_AND_RETURN_RET_LOG(playerService_ != nullptr, MSERR_INVALID_OPERATION, "player service does not exist..");
    MEDIA_LOGW("KPI-TRACE: PlayerImpl Prepare in");
    return playerService_->Prepare();
}
int32_t PlayerImpl::PrepareAsync()
{
    CHECK_AND_RETURN_RET_LOG(playerService_ != nullptr, MSERR_INVALID_OPERATION, "player service does not exist..");
    MEDIA_LOGW("KPI-TRACE: PlayerImpl PrepareAsync in");
    return playerService_->PrepareAsync();
}

关于PlayerImpl来说，playerService_指向的PlayerClient便是具体的完成，PlayerClient的完成是经过IPC的长途调用来完成的，具体地是经过IPC中的proxy端向远端服务建议长途调用恳求。

咱们以播映Play为例：

int32_t PlayerClient::Play()
{
    std::lock_guard<std::mutex> lock(mutex_);
    CHECK_AND_RETURN_RET_LOG(playerProxy_ != nullptr, MSERR_NO_MEMORY, "player service does not exist..");
    return playerProxy_->Play();
}

int32_t PlayerServiceProxy::Play()
{
    MessageParcel data;
    MessageParcel reply;
    MessageOption option;
    if (!data.WriteInterfaceToken(PlayerServiceProxy::GetDescriptor())) {
        MEDIA_LOGE("Failed to write descriptor");
        return MSERR_UNKNOWN;
    }
    int error = Remote()->SendRequest(PLAY, data, reply, option);
    if (error != MSERR_OK) {
        MEDIA_LOGE("Play failed, error: %{public}d", error);
        return error;
    }
    return reply.ReadInt32();
}

proxy端发送调用恳求后，对应的Stub端会在PlayerServiceStub::OnRemoteRequest接收到恳求，依据恳求的参数进行对应的函数调用。播映操作对应的调用Stub的Play办法。

int32_t PlayerServiceStub::Play()
{
    MediaTrace Trace("binder::Play");
    CHECK_AND_RETURN_RET_LOG(playerServer_ != nullptr, MSERR_NO_MEMORY, "player server is nullptr");
    return playerServer_->Play();
}

这里终究是经过playerServer_调用Play函数。playerServer_在Stub初始化的时分经过PlayerServer::Create()方式来获取得到。也便是PlayerServer。

std::shared_ptr<IPlayerService> PlayerServer::Create()
{
    std::shared_ptr<PlayerServer> server = std::make_shared<PlayerServer>();
    CHECK_AND_RETURN_RET_LOG(server != nullptr, nullptr, "failed to new PlayerServer");
    (void)server->Init();
    return server;
}

终究咱们的Play调用到了PlayerServer的Play()。在媒体播映的整个过程中会涉及到很多的状况，所以在Play中进行一些状况的判读后调用OnPlay办法。这个办法中建议了一个播映的使命。

int32_t PlayerServer::Play()
{
    std::lock_guard<std::mutex> lock(mutex_);
    if (lastOpStatus_ == PLAYER_PREPARED || lastOpStatus_ == PLAYER_PLAYBACK_COMPLETE ||
        lastOpStatus_ == PLAYER_PAUSED) {
        return OnPlay();
    } else {
        MEDIA_LOGE("Can not Play, currentState is %{public}s", GetStatusDescription(lastOpStatus_).c_str());
        return MSERR_INVALID_OPERATION;
    }
}
int32_t PlayerServer::OnPlay()
{
    auto playingTask = std::make_shared<TaskHandler<void>>([this]() {
        MediaTrace::TraceBegin("PlayerServer::Play", FAKE_POINTER(this));
        auto currState = std::static_pointer_cast<BaseState>(GetCurrState());
        (void)currState->Play();
    });
    int ret = taskMgr_.LaunchTask(playingTask, PlayerServerTaskType::STATE_CHANGE);
    CHECK_AND_RETURN_RET_LOG(ret == MSERR_OK, ret, "Play failed");
    lastOpStatus_ = PLAYER_STARTED;
    return MSERR_OK;
}

在播映使命中调用了PlayerServer::PreparedState::Play()

int32_t PlayerServer::PreparedState::Play()
{
    return server_.HandlePlay();
}

在Play里边直接调用PlayerServer的HandlePlay办法，HandlePlay办法经过playerEngine_调用到了gstreamer引擎，gstreamer是终究播映的完成。

int32_t PlayerServer::HandlePlay()
{
    int32_t ret = playerEngine_->Play();
    CHECK_AND_RETURN_RET_LOG(ret == MSERR_OK, MSERR_INVALID_OPERATION, "Engine Play Failed!");
    return MSERR_OK;
}

六、总结

本文首要对OpenHarmony 3.2 Beta多媒体子体系的媒体播映进行介绍，首要梳理了整体的播映流程，然后对播映的首要步骤进行了具体地剖析。

媒体播映首要分为以下几个层次：

（1）供给给使用调用的Native接口，这个实际上经过

OHOS::Media::PlayerFactory::CreatePlayer()调用回来PlayerImpl实例。

（2） PlayerClient，这部分经过IPC的proxy调用，向长途服务建议调用恳求。

（3） PlayerServer，这部分是播映服务的完成端，供给给Client端调用。

（4） Gstreamer，这部分是供给给PlayerServer调用，真正完成媒体播映的功能。

OpenHarmony 3.2 Beta多媒体系列——音视频播放框架

一、简介

二、目录

三、播映的整体流程

四、Native接口使用

五、调用流程

六、总结

作者信息

推广

OpenHarmony 3.2 Beta多媒体系列——音视频播放框架

一、简介

二、目录

三、播映的整体流程

四、Native接口使用

五、调用流程

六、总结

相关文章

React-Native热更新之微软CodePush

混合云案例：利用 Databend Cloud 高效加速私有 Databend 的策略与实施

GPT-3微调分步指南

DolphinDB节点启动时的流计算自动订阅教程

作者信息

推广