Modeling the conceptual structure of FFmpeg in JavaScript
summary
Claims a concrete JS library called pizzonia that models FFmpeg’s CLI as five objects (command, input, output, filter chain, filter node) and uses the same FFmpeg option names so documentation maps directly. Demonstrates building real pipelines with explicit IO mappings and command/filter graph construction, shows two execution modes (execute/spawn), evented progress and error reporting, and reports it is in active use in encoding automation (v1, open source) with working examples and produced runnable ffmpeg invocations.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:58Why? We do lots of things with ffmpeg
- 1:31Existing ffmpeg libraries?
- 2:57Libraries for ffmpeg exist - do they help?
- 4:21What do we want out of our code?
- 6:25What might our code look like for this?
- 6:56What makes an ffmpeg command? (the general case)
- 9:03We built a library for this!
- 9:23Fessonia has classes for each component of the command.
- 10:38Let's construct this ffmpeg command bit by bit...
- 12:10Next, we create inputs.
- 14:09Finally, we'll create the command.
- 15:12We can take a look at what we've created.
- 17:17Here's that example using fluent-ffmpeg
related talks
16mJavaScript can be the missing spork in ffmpeg's swiss army knife
13mCreating videos... with React!
21mVideo Creation in a JavaScript World
20mFunctional JavaScript
30mWhen Porgs Scream at Webpack and Other Stories
46mFRP with Bacon.js
05mreal world fp js • Lightning talk
27mGetting Functional with (fab)