Make it a stateless/pure/functional component
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 374
- PR merge metrics
- No merged PRs in 30d
Description
Look into making it completely functional/stateless:
getFrame(frameNum, parameters) -> calculates transitions and everything to return a calculated frame
This allows for making a GUI with seeking to any random frame
Must have workaround for non-seekable streams like ffmpeg pipe
- http://www.ffmpeg.org/ffmpeg-filters.html#movie-1
- http://www.ffmpeg-archive.org/Controlling-an-ffmpeg-stream-td4677436.html
Also cache low resolution/low framerate version of each input video cut so we can render preview faster
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing getFrame(frameNum, parameters) entry point and how non-seekable ffmpeg streams are handled. Read the linked ffmpeg filter and mailing-list references, then determine how random seeking and low-resolution, low-framerate preview caching should work. Done means a stateless frame calculation, a non-seekable-stream workaround, and faster previews for each input video cut.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100