mifi / mifi/editly

better handling of "Frame source returned empty result"

Open
#21 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
5.5k
Forks
374
PR merge metrics
No merged PRs in 30d

Description

I wanted to do a quick test to make sure alpha-channel video is composited correctly but I'm encountering some strange behavior. It might just be that the test file I am using is corrupt but it plays fine in mpv.

https://raw.githubusercontent.com/kinetiknz/nestegg/master/test/media/dancer1.webm

I think it is an ffmpeg issue but it's very minor. However, I think there should be better handling of this specific situation:

with

      layers: [{ type: "video", path: "./dancer1.webm" }],
~/amp [2] 🁽 node test.js ; and mpv customFabric.mp4
320x180 15fps
createFrameSource video clip 0 layer 0
createFrameSource fabric clip 1 layer 0
Frame source returned empty result
Frame source returned empty result
Frame source returned empty result
Frame source returned empty result
Frame source returned empty result
(no end to Frame source returned empty result)

I'm not sure what the best option is but it seems like it should exit after some time rather than going on forever

Contributor guide

No contributing guide indexed for this repository

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

Reproduce the issue with the test.js invocation and the dancer1.webm file, then trace the frame-source handling that emits “Frame source returned empty result.” Done means the empty-result condition no longer runs forever and the command exits or otherwise handles the failure after a bounded period.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.