livepeer / livepeer/studio

Asset fails to upload when < 3 seconds in length

Open
#1,328 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
88
Forks
37
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug (required)** A clear and concise description of what the bug
is.

- When an asset is less than 3 seconds in length, it will fail. This is the case with DoinGud
https://eu-metrics-monitoring.livepeer.live/grafana/explore?orgId=1&left=%5B%22now-2d%22,%22now%22,%22Loki%22,%7B%22refId%22:%22A%22,%22expr%22:%22%7Bapp%3D%5C%22prod-task-runner%5C%22%7D%20%7C%3D%20%5C%22c8c152a6-1ea5-423b-ae6f-d4d60656993a%5C%22%22%7D%5D

After @gioelecerati concat the same clip 3 times, it was able to upload.
```
ffmpeg -i input.mp4 -i input.mp4 -i input.mp4 -filter_complex "[0:v] [0:a] [1:v] [1:a] [2:v] [2:a] \
concat=n=3:v=1:a=1 [v] [a]" -map "[v]" -map "[a]" concat.mp4
```
This process was repeated again with another clip and confirms it

Failed
https://eu-metrics-monitoring.livepeer.live/grafana/explore?orgId=1&left=%5B%22now-7d%22,%22now%22,%22Loki%22,%7B%22refId%22:%22A%22,%22expr%22:%22%7Bapp%3D%5C%22prod-task-runner%5C%22%7D%20%7C%3D%20%5C%220b6ea965-1181-400c-b28c-9085aca3bb51%5C%22%22%7D%5D

Success
https://eu-metrics-monitoring.livepeer.live/grafana/explore?orgId=1&left=%5B%22now-7d%22,%22now%22,%22Loki%22,%7B%22refId%22:%22A%22,%22expr%22:%22%7Bapp%3D%5C%22prod-task-runner%5C%22%7D%20%7C%3D%20%5C%2289b4e676-ed4e-4caa-b8dc-c73050740961%5C%22%22%7D%5D

**Expected behavior (required)** A clear and concise description of what you
expected to happen.

**To Reproduce (required)** Steps to reproduce the behavior:

1. Upload a clip of less than 3 seconds
2. See it fail
3. Upload a clip longer than 3 seconds
4. See it successfully upload

**Device (required):**

Device: MacBook Pro
OS: Monterey 12.6
Browser: Brave
Version: Version 1.43.93 Chromium: 105.0.5195.127 (Official Build) (arm64)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the upload with a clip under three seconds, then compare it with a longer clip that succeeds. Use the linked Grafana logs for the failed and successful asset IDs to identify where processing diverges; done means short assets upload successfully without concatenating the clip.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.