Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

"error processing ffprobe output: no video track found in file" for audio only input

未关闭
#121 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

@red-0ne 已经在做这个了。

开始于 2023年1月5日。

评估

这个 Issue 还没有评估数据。

描述

At the moment, an audio only input will cause a task to fail at the probing step (which currently occurs after Catalyst processing) with:

error processing catalyst callback: error processing ffprobe output: no video track found in file

The following example URLs will trigger the above error for a task:

  • ar://VKiPFdMx9yXdaGY8KJDW9U83G1U_zulErRlacgh5AKE
  • ar://r-2CB1umeVz4ODjlxJLKAw2DOjGP1h10q4uSGEcIMaY
  • ar://QPCRcZRCedI2cM0-j1u1LbWQRdEi2E6fJehZjdQnZa8

All of the above files appear to be ogg files using the opus audio codec for a single audio track.

The error appears to be returned here. The Catalyst MC pipeline seems to be handling the audio only input just fine which is expected since ogg audio only files are in the MC support matrix.

While we could disable the video track check during the probing step, I'm not sure if there are any other things required before we can formally add audio only inputs to our support matrix. So, my suggestion here in the immediate short term is to humanize this error into a invalid video file codec or container... error so that metrics queries/dashboards can filter out errors caused by audio only inputs. Then, separately we can look into formally adding audio only inputs to our support matrix (I suspect we'll want to do this in the near future!) which would allow us to remove the video track check during probing.

主要语言
Go
星标
3
派生
1
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

livepeer/task-runner 的其他 Issue

查看 livepeer/task-runner 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。