Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

关于音频传输格式的另一种想法和可行性 #291

Open
LFNL-scholar opened this issue Mar 7, 2025 · 1 comment
Open

关于音频传输格式的另一种想法和可行性 #291

LFNL-scholar opened this issue Mar 7, 2025 · 1 comment

Comments

@LFNL-scholar
Copy link

目前的代码

服务端

  • 目前逻辑应该是火山引擎传输pcm的数据到服务端。
  • 服务端流式把pcm转成opus数据进行传输。

客户端

  • 接收到流式的opus数据
  • 流式的将接收到的opus数据转成pcm数据
  • 进行播放

另一种可能的想法

可不可以在服务端和客户端直接传输ogg_opus的数据而不是裸opus的数据。
只需在客户端做一次pcm的编码即可,这样子可以省去服务端的一次pcm编码。

还请各位大佬提供意见。

@LFNL-scholar
Copy link
Author

我了解到火山引擎那边的双向流式API传输ogg_opus数据是200-600ms/帧,这么大的一帧传到客户端再加上提取opus数据和编码的时间,是不是会造成明显的卡顿和延迟。(加之opus这种压缩格式无法准确分割为60ms一帧)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant